Also--we do indeed use the embedded Jetty model for serving web apps. It's entirely up to a user of the framework to decide how many apps they'd like to run in each embedded Jetty instance.
One minor point of clarification: this framework is not intended to prescribe that we (Puppet Labs) or anyone else should move all of their services into a giant monolothic process, a la JavaEE. In fact, that's one of…
To be clear: these changes should be totally invisible to most or all of our end users. We'll still be packaging our server-side applications as rpms/debs/etc., and none of the client-side tools are changing at all as a…
Also--we do indeed use the embedded Jetty model for serving web apps. It's entirely up to a user of the framework to decide how many apps they'd like to run in each embedded Jetty instance.
One minor point of clarification: this framework is not intended to prescribe that we (Puppet Labs) or anyone else should move all of their services into a giant monolothic process, a la JavaEE. In fact, that's one of…
To be clear: these changes should be totally invisible to most or all of our end users. We'll still be packaging our server-side applications as rpms/debs/etc., and none of the client-side tools are changing at all as a…