computer-scienceangular-roadmapbackend-roadmapblockchain-roadmapdba-roadmapdeveloper-roadmapdevops-roadmapfrontend-roadmapgo-roadmaphactoberfestjava-roadmapjavascript-roadmapnodejs-roadmappython-roadmapqa-roadmapreact-roadmaproadmapstudy-planvue-roadmapweb3-roadmap
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
15 lines
739 B
15 lines
739 B
# No Caching |
|
|
|
Monolithic persistence in system design refers to the use of a single, monolithic database to store all of the data for an application or system. This approach can be used for simple, small-scale systems, but as the system grows and evolves, it can become a bottleneck, resulting in poor scalability, limited flexibility, and increased complexity. |
|
|
|
A monolithic persistence can have several disadvantages: |
|
|
|
- Scalability |
|
- Limited Flexibility |
|
- Increased Complexity |
|
- Single Point of Failure |
|
|
|
Learn from the following links: |
|
|
|
- [What is Caching in system design?](enjoyalgorithms.com/blog/caching-system-design-concept) |
|
- [No Caching antipattern](https://learn.microsoft.com/en-us/azure/architecture/antipatterns/no-caching/) |