News for hackers. Stuff that matters.
Re:In Defence of the Monolith, Part 2 by qaq on Sunday March 26, 2017 @10:59PM (#13964805)
calling something over http vs calling functions or class methods does not make much difference. So in your example how does it make it easier to add vs monolith? Monolith can have well defined modules and interfaces and microservices could be an entangled mess.
Re:In Defence of the Monolith, Part 2 by nine_k on Sunday March 26, 2017 @11:07PM (#13964837)
No one owns the whole stack. You pick your "main" software, and customize it with third-party services. None of it runs on your premises. No party is willing to expose much more than an API.
Re:In Defence of the Monolith, Part 2 by qaq on Sunday March 26, 2017 @11:38PM (#13964982)
"No one owns the whole stack" - depending on the nature of what you are integrating this can either speed things up or slow things down

"You pick your "main" software, and customize it with third-party services" - not much difference monolith vs microservices

"None of it runs on your premises" - totaly unrelated to monolith vs microservices

"No party is willing to expose much more than an API" - again consuming an API can actually be easier in monolith vs microservices