2011-11-01 | 10:40 AM - 11:40 AM Although you can build Java EE 6 applications with only a fraction of the code that’s necessary with J2EE, many projects are still based on the bloated and exaggerated J2EE patterns and best practices. This session discusses how to build lean applications in a productive and maintainable way. The following pragmatic tools, patterns, and best practices will be covered with working source code, which are especially interesting to Java EE developers and architects: - Mixing CDI, JPA, EJB, JSF, and JAX-RS to save code - Mocking, unit testing, stress testing, and integration testing - Continuous integration and build (Maven 3, Git) - Efficient data access without DAOs - CAP and BASE - Asynchronous CDI events for decoupling and pub/sub - Pro-active JMX monitoring instead of logging

1. Java EE Clean Code
[kill the bloat]
blog.adam-bien.com / twitter:@AdamBien

2. • Expert Group Member (jcp.org) of Java EE 6, Java EE 7,
JPA 2.1, EJB 3.2, CDI 1.1, JMS 2.0 (...)
• Java Champion, (JavaONE) speaker + rockstar, freelancer,
consultant and author: >100 articles, 7 German books,
• Author: “Real World Java EE Patterns– Rethinking Best
Practices” and “Real World Java EE Night Hacks” http://
press.adam-bien.com
• NEW: workshops.adam-bien.com
• http://kenai.com/projects/javaee-patterns/
http://java.net/projects/x-ray
blog.adam-bien.com / twitter:@AdamBien

3. Adam Bien,
press.adam-bien.com
blog.adam-bien.com / twitter:@AdamBien

4. Adam Bien,
press.adam-bien.com
blog.adam-bien.com / twitter:@AdamBien

5. “Perfection (in enterprise development) is
achieved not when there is nothing more to
add, but rather when there is nothing more
to take away.”
--Antoine de Saint-Exupéry
blog.adam-bien.com / twitter:@AdamBien

6. General Advice: Don't
Distribute (CAP)

7. J2EE Patterns in Java EE
adam-bien.com

8. It’s Not
Overengineering...
adam-bien.com

9. ...It’s Cargo Cult
Programming:
[http://en.wikipedia.org/wiki/Cargo_cult_programming]
adam-bien.com

10. “...Cargo cult programming is a style of
computer programming that is characterized
by the ritual inclusion of code or program
structures that serve no real purpose...”
blog.adam-bien.com / twitter:@AdamBien

11. “...Cargo cult programming can also refer to
the results of (over-)applying a design pattern
or coding style blindly without understanding
the reasons behind that design principle in the
first place. Examples are adding unnecessary
comments to self-explanatory code, adding
deletion code for objects that garbage
collection would have collected automatically
with no problem, creating factory objects to
build simple objects, etc. It often happens when
programmers are inexperienced with the
programming language, or simply overzealous...”
blog.adam-bien.com / twitter:@AdamBien

12. Verify Your Design With
…Aliens

13. adam-bien.com

14. ...or ask a Ruby / Python
developer...

15. Continuous Everything
(Integration,
Deployment, QA)

16. Mocks, Unit-, Integration-
and Stress Testing

17. Strict Separation Between
Unit-, Integration-, and
System Tests

18. Java EE 6, Maven 3,
Continuous Integration
And Git

19. Convention Over
Configuration with DI

20. No, I don't want your
XML!

21. Homegrown
Frameworks?

22. JavaDoc Is Suspicious

23. DRY And DIE

24. package private fields or
public setters?

25. Back To Java SE Thinking

26. Rich Domain Objects

27. No Interfaces

28. No Extensive Layering

29. Rethink J2EE Patterns

31. Rethink GoF Patterns

32. Factory

33. Observer

34. Builder

35. Facade

36. Bridge

37. Strategy

38. Decorator

39. Entity Control Boundary

40. Thank You!
blog.adam-bien.com
twitter.com/AdamBien
adam-bien.com