Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Make microservices look like monoliths

github.com

Post reply on HN
Print view View original

1–10 of 106 posts

Re: Make microservices look like monoliths

#6

Post by Zetice »

I’d rather compose my systems with widely understood and commonly used components that make hiring and maintaining over time more of a puzzle problem than a, “learn a new framework” problem.

This feels like we make our jobs harder than they have to be, sometimes…

Re: Make microservices look like monoliths

#7

Post by switch007 »

voidfunc wrote: post #5
mati365 wrote: post #2

It makes no sense. Why not just create modular monolith?

Because all these idiots who pitched microservices super hard need to undo the mess they've created while self promoting themselves into new thought leadership roles.

Uffff

Spot on.

And how do you know you’re not a thought leader? You call yourself one

Re: Make microservices look like monoliths

#8

Post by jawns »

mati365 wrote: post #2

It makes no sense. Why not just create modular monolith?

I can think of a few cases. For instance, say you want to make parts of your codebase open-source and self-contained, but others closed-source. It can be easier to carve off the OSS and treat it as if it were a third-party application.

That's not the case here, where the code lives in a monorepo but the services are many.

Re: Make microservices look like monoliths

#9

Post by dec0dedab0de »

jawns wrote: post #8
mati365 wrote: post #2

It makes no sense. Why not just create modular monolith?

I can think of a few cases. For instance, say you want to make parts of your codebase open-source and self-contained, but others closed-source. It can be easier to carve off the OSS and treat it as if it were a third-party application. That's not the case here, where the code lives in a monorepo but the services are many.

In that case it would be just as easy to have the OSS app be used directly by the closed source app instead of spinning up another service. It could be a library, a plugin, or even just a separate app that your internal app shells out to. Basically, a separate OSS release really shouldn't be a consideration for deciding to run it as a separate service or not. Though it is an excellent reason for a separate repo.
Post reply on HN