News for hackers. Stuff that matters.
Re:Monolith First (2015) by thatswrong0 on Friday February 19, 2021 @05:23AM (#26191485)
That's what my company has done. We have a microservice-like architecture, but discourage dependencies on other services. If we need to use one service in another, we use dependency injection (which allows us to switch out the communication protocol later if need be) or talk over a message bus instead. The idea was that we would figure out later which sub-services actually need to be split out based on usage.

AFAIK, we haven't actually split out anything yet after all these years. All of our scale issues have been related to rather lackadaisical DB design within services (such as too much data and using a single table for far too many different purposes), something an arbitrary HTTP barrier erected between services would not have helped with at all.

Re:Monolith First (2015) by rizpanjwani on Friday February 19, 2021 @05:25AM (#26191500)
Does each microservice/module have its own db?
Re:Monolith First (2015) by thatswrong0 on Friday February 19, 2021 @05:40AM (#26191613)
Nope. Everything lives in one big DB, but services are not allowed to touch each others tables directly - communication must be done through service API endpoints.
Re:Monolith First (2015) by collyw on Friday February 19, 2021 @09:19AM (#26193384)
I have seen micro-service architectures like that. It seems pretty pointless. You should be letting the database do as much of the heavy lifting as you can.