1. Tip the scales using EJB 3
Carlo de Wolf
EJB 3 Lead Developer
JBoss by Red Hat
JBUG BE
th
July 9 2009
1

2. Agenda
● Job Trends
● Clustering
● Standards
● Performance
● Q&A
2

3. Job Trends #1
● Spring is rising
3

4. Job Trends #2
● Not at the cost of JavaEE
4

5. Clustering
● Two flavors
– High performance
– High availability
● Simply: @Clustered
5

6. Standards
tm
●
JSR 318: Enterprise JavaBeans 3.1
● Not proprietary
● Choose your support organization
6

7. Performance
● EJB has detached instances
● Pooling of Stateless Enterprise Beans
● Passivation of Stateful Enterprise Beans
● => better QoS
7

8. Performance #2
● Took 37.5 seconds ● BLACKBOX MEASURED
STATS:
● Average wait queue 0.15
– Took 37.8 seconds
● Average execution 31.6 – Average wait queue 0.024
● Max wait queue 1.251 – Average execution 19.5
● Max execution 34.485 – Max wait queue 0.113
– Max execution 36.206
● WHITEBOX MEASURED
STATS:
– Average wait queue 12.7
– Average execution 1.86
8

9. Future
● JavaEE 6: embrace all techs
● JSR 299: Contexts & Dependency
Injection (WebBeans)
● JSR 330: Dependency Injection for Java
● EJB 3.1 Embeddable
● EJB 3.1 Light in Web Profile
9

10. (tm)
Why Enterprise JavaBeans ?
● Allow rapid development of reusable
business components
● Using an easy infrastructure which does:
– Memory management
– Remote invocation
– Thread management
● Thus having a predictable QoS
● Without any low-level system code
10

11. Q&A
● JBoss EJB3 makes your bean evolve.
● http://www.jboss.org/ejb3
11