Architecture Thought #995
lawweiliang
started this conversation in
General
Replies: 1 comment 1 reply
-
Hi @lawweiliang , thanks for sharing your new project with us. Can you please provide us with more context on the business side? This will help us better understand the needs behind your technical design. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hihi Friends,
This is the high-level architecture that I am thinking of for a new project. Just want to share it with you yeah.
The whole architecture will use
Tauri + React/Vue (Frontend)
Rocket(API)
Reasons I am using React/Vue as UI framework
Reasons I am using Tauri
Reasons I am using Rocket
My expectation
From an architectural design perspective, Liang usually focuses on 3 key components. Update + Scale + Standard.
Update
Question: The system needs to update from time to time. How do I update the code?
I pass this responsibility to the framework. If the framework upgrades, I upgrade as well.
Scale
Question: What if traffic increase dramatically? Can I scale the system?
That is the reason why I usually split the system into two parts. Frontend and backend. (lots of work, yeah I got you, look at my hair over the profile picture, then you will figure out why. 😃 )
Using Nginx + Reddis + Database Partition to reduce loading pressure + etc.
Standard
Question: How to maintain the standard of a system that every programmer will follow?
The framework comes in handy, everyone follows framework standards. Buddy, trust me. this is going to save you a ton of time.
Notes, This is just my thought yeah. It might have some bias or angle that I do not think of. Feel free to point it out. 😃
Beta Was this translation helpful? Give feedback.
All reactions