Skip to content

Instantly share code, notes, and snippets.

@AdamBien

AdamBien/28thAirhacksQ&A.md

Last active July 13, 2016 15:57
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save AdamBien/37aa198634f5b7227e64e2c7b16fd8d7 to your computer and use it in GitHub Desktop.
Save AdamBien/37aa198634f5b7227e64e2c7b16fd8d7 to your computer and use it in GitHub Desktop.
Download ZIP
28thAirhacksQ&A.md
Raw
28thAirhacksQ&A.md

Ask questions and see you at July, 13th (exceptionally, this time at wednesday) at 6.PM. CET: http://www.ustream.tv/channel/adambien Also see archives: airhacks.tv

  1. Java EE 8 News
  2. Discussion around http://microprofile.io (http://www.adam-bien.com/roller/abien/entry/the_enterprise_java_future_is)

Questions from anonymous:

  1. Java EE status – during my studies, I utilized Java EE 6 for creating distributed system to monitor IT infrastructure. Now is 2016 and situation of Java EE is not in bright colors – Oracle reluctant to invest in Java EE standard, concern expressed in formation of “Java EE Guardians” that you are part of. I learned much from it and gave me ability to think “at scale”, distributed manner. But recent developments around standard, started my evaluation - if Java EE is worth pursuing in long term.
  2. Java EE Backend Development – I find great joy in creating backend software – RESTful web services in JAX-RS or Restlet, business logic or database integration using ORM (JPA or Hibernate). Not mentioning Big Data “movement” with Apache Hadoop and Spark frameworks. But Java EE offers I was looking up, almost always require Angular or other JS libraries. More and more employers require “Full-stack” engineers. Is simply market for specialized backend engineers is shrinking and should I adapt to it or is it simply reality of software development – backend can be reused and GUI trends (Desktop or Web) change all the time ? 

  3. Java and JavaScript – In my projects, I always used statically typed languages – benefit for compile time checks (C/C++ or Java/C#) is undisputed. What would be your advice for Java engineer in regard to JavaScript ? Unavoidable future or majority of development but not all ?
  4. Thoughts on Golang ?
  5. ForkJoin and Java EE 8
@julio-rocha-coderoad-com
Copy link

@dwamara yes it is, and I see that solution for the first part, but since 2014 to now, do I have to still using that solution?

@karschdn
Copy link

karschdn commented Jul 13, 2016 •
edited

Hi Adam,

Question regarding BCE

BCE is fine to organize "modules" and providing a common package structure. As far as i understood, the boundary is used as a kind of entry point (transaction startpoint, ...) to use the modules. Correct? CDI seems to be the "tool" to put everything together and building the application structure e.g. adding cross funcitonalities with interceptors.

But adding @stateless to the boundaries prevents them to be processed by CDI Extensions (because they are EJBs and not CDI Objects). This, for example, makes it impossible to add interceptors programmaticaly by a CDI Extension to @Stateless-Objects. I think this is a big disadvantage of the BCE pattern because the boundary plays a central role in this pattern and in application design and i want to have full CDI feature support here. What is your opinion about that? Do you have a solution for that? Or, should it work and do i make some kind of mistakes or conceptual faults (i am using JEE6 at the moment)?

regards
Karsten

(Currently, i am using a CDI Extension to add interceptors to arbitrary CDI classes but does not work with EJBs. Yes, adding interceptor annotation in code works well but this is not what i want to do. Its like adding some functionallity (temporary) to CDIs without byte-code-manipulation)

@haal
Copy link

haal commented Jul 13, 2016 •
edited

Hi Adam,

could you comment on this presentation?

Nine Neins - where Java EE will never take you (slides |video)

Points from presentation:

  1. Java EE helps building distributed moniliths
  2. Java EE has a threading-model that isn't ideal for microservices
  3. Java EE doesn't support the notion of data in motion (streams)
  4. Java EE doesn't support resilency
  5. Java EE is implemented as containers - no service elasticity
  6. No notion of immutability
  7. Choice of data stores, use of transactions and evental consistency
  8. No outer architecture - while still calling it a platform
  9. Java EE doesn't know services

Thanks

@jlmc
Copy link

jlmc commented Jul 13, 2016

hello Adam, About Monitoring Java EE, it is possible do use wildfly in the same way as you used on glassfish (like in your project lightfish). if it is not, can you talk about the diferences.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment