Microservices Database vs Polyglot Persistence

Pick database-per-service when services have genuinely independent lifecycles and your team can stomach eventual consistency — greenfield microservices, polyglot persistence needs, teams that own their schema end-to-end meets developers should adopt polyglot persistence when building complex applications with diverse data models, such as e-commerce platforms needing relational data for transactions, document stores for product catalogs, and graph databases for recommendations. Here's our take.

Microservices Database

Nice Pick

Pick database-per-service when services have genuinely independent lifecycles and your team can stomach eventual consistency — greenfield microservices, polyglot persistence needs, teams that own their schema end-to-end

Pros

• Skip it for a small team shipping a first product with tangled read patterns; a modular monolith with one shared database gets you 90 percent of the boundary discipline without the operational tax
• Related to: apache-kafka, postgresql

Cons

• Specific tradeoffs depend on your use case

Polyglot Persistence

Developers should adopt polyglot persistence when building complex applications with diverse data models, such as e-commerce platforms needing relational data for transactions, document stores for product catalogs, and graph databases for recommendations

Pros

• It's particularly useful in microservices architectures, where each service can use its own database type, and for big data scenarios requiring real-time analytics alongside transactional consistency
• Related to: microservices, database-design

Cons

• Specific tradeoffs depend on your use case

The Verdict

Use Microservices Database if: You want skip it for a small team shipping a first product with tangled read patterns; a modular monolith with one shared database gets you 90 percent of the boundary discipline without the operational tax and can live with specific tradeoffs depend on your use case.

Use Polyglot Persistence if: You prioritize it's particularly useful in microservices architectures, where each service can use its own database type, and for big data scenarios requiring real-time analytics alongside transactional consistency over what Microservices Database offers.

The Bottom Line

Microservices Database wins

Pick database-per-service when services have genuinely independent lifecycles and your team can stomach eventual consistency — greenfield microservices, polyglot persistence needs, teams that own their schema end-to-end