News for hackers. Stuff that matters.
Re:“It's The Future” by nailer on Wednesday August 17, 2016 @07:51AM (#12303945)
> 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.

Re:“It's The Future” by drdaeman on Wednesday August 17, 2016 @09:12AM (#12304378)
Probably 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.

Re:“It's The Future” by sangnoir on Wednesday August 17, 2016 @07:59AM (#12303985)
You do know the author is a taking the piss out of the practice, right?
Re:“It's The Future” by nailer on Wednesday August 17, 2016 @09:10AM (#12304370)
You know nothing in the comment you're replying to indicates I wouldn't, right?
Re:“It's The Future” by flukus on Wednesday August 17, 2016 @11:29PM (#12310242)
Don't be so quick to assume micros services involve message queuing. For most it seems to just be an elaborate RPC mechanism (unfortunately).
Re:“It's The Future” by nailer on Thursday August 18, 2016 @04:06AM (#12311017)
Oh 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).