Is a shared database in microservices actually an anti-pattern?

Re:Is a shared database in microservices actually an anti-pa... by gcufhg on Sunday February 24, 2019 @03:48PM (#19240536)

You could build a separate ReportService which replicates only the data that's needed for a report in RDBMS.

[ Parent | on HN ]

Re:Is a shared database in microservices actually an anti-pa... by HelloNurse on Monday February 25, 2019 @04:43AM (#19244338)

With a sane database design, the Report service can read user details of all users of interest from the user service and ask the Orders service for the orders of each user (a presumably efficient query), without replicating data.

[ Parent | on HN ]

Re:Is a shared database in microservices actually an anti-pa... by tatersolid on Thursday February 28, 2019 @10:11PM (#19277635)

So you’re guaranteeing O(n^2) runtime?

Relational DBs are really just fantastic at high-performance sorts, merges, and joins. Why do you want to pay the continual ongoing cost of replicating that poorly and inefficiently in your application logic? For each microservice that refers to another in some way?

[ Parent | on HN ]