Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • Use a single database. Commented Jul 6, 2022 at 18:59
  • @ReinstateMonica imagine a more complex system with a lot more independent services that require this type of relationship. Sure, you can argue that if you need this type of relationship, especially for this example, then you should not separate them in different services/databases. But, let's imagine for the sake of discussion a more complex system. Commented Jul 6, 2022 at 19:09
  • 1
    Then tune the database so that it performs well enough and run it on fast hardware. There are very few situations where a relational database can't handle the load. If you're in one of those rare situations, you can hire a dozen engineers to manage a distributed data store. Commented Jul 6, 2022 at 20:04
  • Seems like a poor selection of microservices, similar to the CRUDy API problem. Rethink your services. Commented Jul 8, 2022 at 18:51
  • This question is a list question, which is off-topic. It's okay to ask for a solution to a problem, but asking for us to list other solutions is going to draw opinionated answers and render the question unresolvable (because there's always one more way to do it). Commented Apr 3, 2023 at 23:56