Re: [ee4j-community] Just for application servers?

[Adam Bien <abien@xxxxxxxxxxxxx>]

> On 16. Oct 2017, at 12:49, arjan tijms <arjan.tijms@xxxxxxxxx> wrote:
> 
> Hi,
> 
> On Sun, Oct 15, 2017 at 6:49 PM, Adam Bien <abien@xxxxxxxxxxxxx> wrote:
> 
> > How about "Runtime for enterprise JVM workloads"?
> 
> +1 but: what is the technical difference between a "Runtime for enterprise JVM workloads" and an "Application Server"?
> 
> I think there isn't much difference. Adding to the confusion is that the entire term "Application Server" is not really well defined at all.

Exactly. This is what I always asked myself.
> 
> For some people "Application Server" seems to mean e.g. a 2Gb WebSphere 6 installation that costed a million dollar, was installed years ago by an operations team, which nobody may ever touch, and for which developers may only provide wars. In such systems e.g. JSF can never be updated, since operations supposedly don't know what JSF is, and engineering who does is not allowed to touch the application server.

This was true in 1945 :-)
> 
> While a runtime is, I think, associated by many with e.g. Spring Boot, which is under full control of the engineering team, is free of cost, and may include JSF, which can be upgraded by the engineering team since they deliver/provide the full runtime.
IMO there is no difference between a booted Spring Boot and an Application Server. Even the stack trace should be similar.
> 
> So technically there's little to no difference at all. Both are an executable that contains both library code (JSF, CDI, etc..), server code (Tomcat- Undertow, etc internals) and application code. 
> 
> Even if there was any technical difference, i.e. application servers typically being provided as 2 pieces; the AS and the .war/ear, things like docker, Payara Micro, WildFly Swarm, etc further blur the differences.

There is one difference I care about: app servers are pre-packaged. I don't have to build a assemble an appserver from various parts by myself.
This seems to be appealing to many "getting things done" devs as well. We should be careful with our message.
> 
> But correct or not, it seems "application server" just like "EJB" will forever be associated with that mythical 2GB WebSphere 6 installation, so although perhaps undeserved that may be the reason people like to avoid the term.

+1 -> everything is just marketing :-)

cheers,

adam


> 
> Just my 2 cents
> 
> Kind regards,
> Arjan Tijm
> 
> 
> 
>  
> >
> >
> > Ed
> >
> > --
> > | 29 business days until CodeEurope Poland 2017
> > | 75 business days until JavaLand 2018
> > | edward.burns@xxxxxxxxxx | office: +1 407 458 0017
> > _______________________________________________
> > ee4j-community mailing list
> > ee4j-community@xxxxxxxxxxx
> > To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> > https://dev.eclipse.org/mailman/listinfo/ee4j-community
> 
> _______________________________________________
> ee4j-community mailing list
> ee4j-community@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/ee4j-community
> 
> _______________________________________________
> ee4j-community mailing list
> ee4j-community@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/ee4j-community



 workshops.adam-bien.com
 webstandards.training
 javaeemicro.services
 adambien.blog

 Author of: 
 "Real World Java EE Night Hacks”,  
 "Real World Java EE Patterns—  Rethinking Best Practices"