This article signals to me that we may have reached ‘peak microservice’ and should now expect a flood of blog posts extolling the virtues of monoliths and lots of industry effort to combine microservices into self-contained monoliths.
I'm not so convinced. I'll assert that a service boundary can absolutely exist between two modules running within the same binary image. The distinction comes down to grading your application along a few axes: Ratio of deployable units to bounded contexts, ball of mud versus domain-driven design, release engineering maturity, and a few others that I may be missing. I'll further assert that "a monolith" is not the ant…
+1 to this comment. My team is heading down a similar path. Theres a single, defined and versioned, external API. Internally there are a handful of “microservices.” All have their own APIs, models, versions, etc. Some are invoked over remote HTTP, some are a function call, some have their own endpoint and several microservices behind it, some are bundled in to the same binary. In each case the caller and the receiver doesnt know (or care) about the implementation. The important parts are the service boundaries and definitions. Not the packaging.