Hacker News Reader

There is a new paper out from Google which seems like an interesting approach to get out of microservice hell

https://sigops.org/s/conferences/hotos/2023/papers/ghemawat....

I've only read the abstract, but hasn't this been achievable for at-least the last twenty years with dependency injection? I've seen time and time again developers conflate microservices with the general concept of service abstraction and separation-of-concerns. These things have existed before microservices, and will continue to exist.

A good DI implementation allows for one to define these business services as interfaces and implementations within an initial monolith, and then trivially reimplement those interfaces against an API or RPC when it comes time to scale. Interfaces can be separated out into a common library which can be referenced in all parts of the system. I am simply curious as to why this has been so staunchly avoided over the past decade of microservices hype.

This isn't really DI. From skimming, it is sort of.. cross-machine DI.

This is an interesting paper and one I would never have found on my own. How did you come across it?

Twitter, I think it is pretty new. The lead author is a very well known engineer.

Reply on news.ycombinator.com