| Pros | Cons |
|---|---|
| Easy to develop, test and deploy: only needs to deal with one codebase, one build process and one deployment process | Lack of modularity and flexibility: You cannot easily change or update a part of the application without affecting the whole system. You also cannot reuse or replace components with different technologies or architectures |
| High performance and scalability: can leverage the full power of the server or the cluster by using shared memory, caching and load balancing | Long development and deployment cycles: You need to rebuild and redeploy the entire application every time you make a change, which can take a lot of time and resources |
| Low complexity and maintenance: don't need to worry about inter-service communication, coordination, synchronization or consistency | High risk of failure and downtime: If any part of the application fails or has a bug, it can bring down the whole system. You also need to take the system offline or use complex techniques to perform zero-downtime deployments |
Created
July 19, 2023 05:24
-
-
Save EliFuzz/1881ce9f7125ac18ec1cecdf6f61e71a to your computer and use it in GitHub Desktop.
Pros & Cons: Monolithic deployment
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment