Performance Implications and Special Considerations

The Database per Service Pattern gives each service independence, and that independence has costs. The earlier lessons showed the rule and a working example. This lesson lists what the pattern costs at run time and in operations. It then shows the standard ways to keep those costs small.

Queries Cross the Network Now

In a shared database, one SQL query could join many tables. That join was one round trip to one server. With a database per service, the same read becomes several HTTP calls.

Each call adds latency (the time a request spends traveling and waiting)