News for hackers. Stuff that matters.
Re:The End of Microservices by pjmlp on Thursday July 21, 2016 @05:18AM (#12135689)
I have been doing it since the early 90's.

It is called unit, module, package, library.

No need to put some network layer, with its own set of problems, between method/function calls.

Re:The End of Microservices by lobster_johnson on Thursday July 21, 2016 @11:43AM (#12137587)
Libraries typically don't have databases or daemons. It's operationally very different.

Can I envision a language-specific framework wherein "microservices" are just plugins that implement interfaces (Java interfaces, for example) for exposing RPC endpoints, which you then "mount" in your framework, allowing developer-enforced separation of concerns, but still allowing a single codebase to share things like config structures, database accessibility, etc.?

Sure. I can't imagine why anyone would want to do it that way, though. For example, you couldn't realistically open-source one of your services, or write it in a different language. Service-specific database stuff would get hairy, quickly. And so on.

Re:The End of Microservices by pjmlp on Thursday July 21, 2016 @01:36PM (#12138536)
Daemons are called threads and coroutines.

As for the rest, that is what a proper design of module interfaces is supposed to be.

Apparently too many people nowadays don't read books about ADTs (Abstract Data Types).