3 ms·
This might be a hard pill to swallow...but it's going to be highly dependent on your app server. Java EE is just a set of annotations with several different ve
by agibsonccc 9y ago
This might be a hard pill to swallow...but it's going to be highly dependent on your app server.
Java EE is just a set of annotations with several different vendors implementing the standard in an app container.
I would look at the docs for whatever your employer is using.
A lot of it comes down to knowing some basic fundamentals about web development. For example: Load balancing/HA can be done in several different ways not tied to Java EE, the same is true of any of the things you're mentioning.
Largely, HA can be done with your app server. An API is just REST which means the jaxrs implementation.
Multi threading dynamics are typically app server specific. Generally "let your container do it" is the right answer though.
Source: Been doing java since spring 2.0 as well as dealing with app servers ranging from glassfish to jboss (now wildfly).
- alicorn 9y agoNot hard at all, I already suspected that this might be the case. Can you recommend any generally good resources about these topics? I am looking first and foremost to acquire enough knowledge to think about them the right way. Technical implementation is important as well, but perhaps secondary in the context. We are using Wildfly as app server.
- agibsonccc 9y agoThen use their docs. In general, I would follow a few tutorials specific to red hat. For now, decompose it focusing on using jaxrs for now. The only other thing might be JNDI for accessing data sources. The rest will come from that.