[remmelt]

This stops short at all the really interesting stuff of microservices. Where's the service discovery? Failover? Secret storage? Communication?

Besides that, I don't agree with putting dependency injection in a microservice. Why bother? In a sense, microservices are a breath of fresh air, because they're supposed to "fit in one developer's head." If you're already adding layers of indirection, you're making the code harder to reason about for no good reason.

[anon987]

Yep - yet another half-baked project that someone is using for internet points. I'm really getting sick of people re-inventing the wheel poorly.

The number of available tools is really getting out of hand and I wish projects like this wouldn't suck away resources from established, functional projects.

[artpepper]

Even in a microservice I'd expect DI to be useful for injecting stuff like logging, caching, data backend. For mocking, if nothing else.

DI + properly defined interfaces shouldn't make code harder to reason about.

[giulianob]

I would even expect some out of the box management APIs to help upgrade the microservice with low to zero downtime, feature toggles, etc... A lot of these get built into each app typically but when you're creating many different microservices, the overhead of creating a service needs to be as close to zero as possible.