F
Frank Meulblok
Guest
From what I've read so far in those NGINX articles (Which isn't all of it, have to leave that as a new year's resolution...), it looks like the architectural changes in the Pacific AppServer for OpenEdge (11.6) take a few big steps towards enabling the micro-services pattern. Every individual service can now be it's own self-contained ABL Web App, which can be distributed as needed/desired (see also: documentation.progress.com/.../index.html for the technical details on that). And there's nothing that stops the code from one Web App to make requests to another. How big or how small each service becomes is then left up to the developer. I'd say that if you want to transition from a monolithic classic appserver towards microservices, you'll want to start by grouping together your different entry points by what functionality they provide, and then start splitting off those groups into their own service. (In theory, you can do something similar with the classic appserver as well by using the often-overlooked AppserviceList functionality. But then you end up with a lot of extra work to avoid collisions between the different services running under the same brokers.)
Continue reading...
Continue reading...