Reza, good points. Comments below.
Thanks for bringing this up in the “Opening Up Java EE” panel as well. Everyone agreed with this during the session.
I do like “standalone on Java SE" as a "guiding principle”. It will facilitate broad adoption of EE4J technologies, not to mention other pragmatic reasons (easier testing, etc).
I prefer we simply replace “microservices” with “cloud native”, which is a broader, more abstract conceptual description that encompasses both FaaS and microservices. Oddly, “server side” is more broad that “cloud native”, and encompasses both traditional on-premise and cloud native architectures :-) However, I agree that referring to the cloud is a good balance.
The definition of “Modern" changes on a monthly basis - by definition. Adding this future-proofs EE4J! :-) I actually think that using “cloud native” as discussed above covers this point.
_______________________________________________ ee4j-community mailing list ee4j-community@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/ee4j-community
|