A. Architectural Patterns
In a service-oriented architecture, services are expected to be as self-sufficient as possible, and the way you decide to compose and structure your services is one of the greatest challenges in SOA.
Fortunately, with OnixJS... You get to build SOA Services with an extra clean structure, elegant and highly semantic set of artifacts that will allow you to focus on your Business Logic.
SOA Applications / Services are executed in separated processes, but all registered under the same OnixJS SOA Context Host and living within the same container/server.
When implementing microservices architecture, you want to create a much smaller piece of code than SOA, it will mainly be independently deployed and won't be registered and loaded by the OnixJS SOA Context Host, instead, it will run in stand-alone mode.
MSA Services naturally lives in separated processes/containers/servers.
Everybody loves MVC, OnixJS provides the artifacts for you to create a Monolithic MVC Application that will be deployed all at once, naturally running the entire app in a single process, unless you horizontally scale using a process manager like PM2 or a LB on top.