Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Systems design
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
===Architecture design=== Designing the overall structure of a system focuses on creating a scalable, reliable, and efficient system. For example, services like Google, Twitter, Facebook, Amazon, and Netflix exemplify large-scale distributed systems. Here are key considerations: # [[Functional requirement|Functional]] and [[Non-functional requirement|non-functional]] requirements # Capacity estimation # Usage of [[Relational database|relational]] and/or [[NoSQL]] databases # Vertical scaling, horizontal scaling, [[Shard (database architecture)|sharding]] # [[Load balancing (computing)|Load balancing]] # Primary-secondary [[Replication (computing)|replication]] # Cache and CDN # Stateless and Stateful servers # Datacenter [[Geographic routing|georouting]] # Message Queue, Publish-Subscribe Architecture # Performance Metrics Monitoring and Logging # Build, test, configure deploy automation # Finding single point of failure # [[API]] Rate Limiting # Service Level Agreement
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)