Re:Introducing “Database Performance at Scale”: A Free, Open...
by CBLT on Thursday October 05, 2023 @12:33PM
(#37780728)
It looks like what they're describing is implementing database joins in the application: 2 network round trips, first one for ids from a table and the second to get values from another table with foreign keys corresponding to the ids.
[ Parent
| on HN ]
Re:Introducing “Database Performance at Scale”: A Free, Open...
by WanderPanda on Thursday October 05, 2023 @12:59PM
(#37781064)
Isn‘t implementing joins in the application what microservices are all about?
Re:Introducing “Database Performance at Scale”: A Free, Open...
by _jal on Thursday October 05, 2023 @02:39PM
(#37782345)
No, microservices are all about senior management ability to map applications to people to yell at.
Re:Introducing “Database Performance at Scale”: A Free, Open...
by nicoburns on Thursday October 05, 2023 @04:22PM
(#37783820)
You're getting confused with NoSQL ;)
Re:Introducing “Database Performance at Scale”: A Free, Open...
by macintux on Thursday October 05, 2023 @06:54PM
(#37785264)
I have supported a microservices environment where each service had its own database, and indeed "foreign keys" were mostly application-level concerns. A real pain, and I don't think any of us would have chosen that approach in hindsight.
I hope there are better ways to design microservices.