Cloud Managed Services, Migration Strategy, and Polyglot Persistence
Learn how NoSQL is used in modern cloud systems and why many architectures combine multiple database types instead of choosing only one.
Inside this chapter
- Managed NoSQL in the Cloud
- Migration Requires More Than Data Copy
- Polyglot Persistence
- Choosing Multiple Databases Wisely
Series navigation
Study the chapters in order for the clearest path from NoSQL basics to advanced distributed design and production decision-making. Use the navigation at the bottom of each page to move through the full series.
Managed NoSQL in the Cloud
Many teams use managed NoSQL services to reduce operational burden. Cloud providers offer managed document stores, key-value platforms, graph options, and globally distributed data services. This can simplify operations, but engineers still need to understand the underlying data model and tradeoffs.
Migration Requires More Than Data Copy
Moving from relational to NoSQL, or from one NoSQL model to another, is not just a data export exercise. It usually requires redesigning schemas, access patterns, consistency assumptions, caching behavior, and sometimes application logic itself.
Polyglot Persistence
Many strong architectures use multiple storage systems together. For example, a company may keep financial truth in PostgreSQL, sessions in Redis, product content in MongoDB, and event streams in Cassandra. This is called polyglot persistence.
Choosing Multiple Databases Wisely
Using many databases can solve real problems, but it also increases complexity. Teams should only add multiple data platforms when there is a clear architectural benefit, not because every new tool sounds exciting.