So basically what I’ve meant is that we’ve got a bunch of services - they can be cascaded and can be dependent of each other.
For instance, 80% of all webapp backend stuff is a generic CRUD with AAA (Authentication, Authorization, Accounting), and any of existing endpoints can be «wrapped» with an additional AAA layer of logic, so there would be:
Authentication Check or HTTP 40* status -> Authorization Check or HTTP 40* status -> Accounting check or HTTP 402 status -> and then the actual action call.
Node.js frameworks leverage this cascaded request handling via chaining of middlewares, some other MVC frameworks call it with some other names, but the purpose remains the same.
And ktor has something called «features» yet another name for the subject.
So basically services exports methods and methods can be called via protocols, services has their own dependencies, they can be stacked together as mentioned before, and there might be some hot/cold service reloading semantics involved. What I’ve meant by a «proper lifecycle» is to provide people with an ability of implementing hot and cold update logic with proper dependency management, consistency tests and fallbacks.
I’m just thinking «out of the box» of another generic MVC framework, it’s all about SOA automation and microservices nowadays, and there is a very huge lack of proper instrumentation.