2 ms·
> You take your monolithic app and you split it into like 12 services. The non-web world has been doing this with message queueing for about 15 years. Maybe mo
by nailer 10y ago
> You take your monolithic app and you split it into like 12 services.
The non-web world has been doing this with message queueing for about 15 years. Maybe more.
- sangnoir 10y agoYou do know the author is a taking the piss out of the practice, right?
- nailer 10y agoYou know nothing in the comment you're replying to indicates I wouldn't, right?
- drdaeman 10y agoProbably more. I'd say, like, at least 30-40 years. I mean, the infamous "UNIX way" of "do one thing, do it well" (something we nearly lost with popularity of "do everything in a manner incompatible with how others do it" approach in too many modern systems), when complex behavior was frequently achieved through the modularity of smaller programs communicating through well-defined interfaces. Heck, microkernels are all about this, and their ideas haven't grew out of nowhere. And HURD (even though it was never finished) is quarter a century old already.
- flukus 10y agoDon't be so quick to assume micros services involve message queuing. For most it seems to just be an elaborate RPC mechanism (unfortunately).
- nailer 10y agoOh yeah, there's certainly other ways of doing it. My own experience is just that message queuing seems to be the default loosely-coupled RPC mechanism for larger orgs (from before the term 'micro services' was popular).