Reza Rahman is a long time consultant now working at CapTech. He has been an official Java technologist at Oracle. He is the author of the popular book EJB 3 in Action. Reza has long been a frequent speaker at Java User Groups and conferences worldwide including JavaOne and DevNexus. He has been the lead for the Java EE track at JavaOne as well as a JavaOne Rock Star Speaker award recipient. Reza is an avid contributor to industry journals like JavaLobby/DZone and TheServerSide. He has been a member of the Java EE, EJB and JMS expert groups over the years. Reza implemented the EJB container for the Resin open source Java EE application server. He helps lead the Philadelphia Java User Group.
Reza has over a decade of experience with technology leadership, enterprise architecture, application development and consulting. He has been working with Java EE technology since its inception, developing on almost every major application platform ranging from Tomcat to JBoss, GlassFish, WebSphere and WebLogic. Reza has developed enterprise systems for well-known companies like eBay, Motorola, Comcast, Nokia, Prudential, Guardian Life, USAA, Independence Blue Cross and AAA using EJB 2, EJB 3, Spring and Seam.
Domain-Driven Design (DDD) promises to simplify enterprise application development and is gradually gaining traction as an alternative to traditional four-tier architectures originally popularized by J2EE. As the name implies, DDD is an architectural approach that strongly focuses on materializing the business domain in software.
This session demonstrates first-hand how DDD can be implemented using Java EE via a project named Cargo Tracker. Part of the Java EE Blue Prints, Cargo Tracker seamlessly maps concepts like bounded contexts, layered architectures, entities, value objects, aggregates, services, repositories and factories to realistic code examples. The Cargo Tracker project also embraces popular practices adopted by the DDD community such as Object Oriented Analysis, Domain Models, Test Driven Development, Agile Refactoring, Continuous Integration, Object Relational Mapping, Dependency Injection and Cross-Cutting Concerns, incorporating these concepts into a realistic Java EE application.
The process of defining the scope for Java EE 8 was the most community opinion driven in the history of the platform. Java EE 8 is supposed to solidly enable HTTP/2, Server-Sent Events (SSE), JSON and aligning all parts of the platform with Java SE 8. It includes a much awaited security API overhaul, a brand new MVC API as well as a slew of critical updates to APIs like JSF, JMS, JPA, JAX-RS and CDI. Unfortunately the road to Java EE 8 has not been very smooth. After a long and silent delay Oracle has now announced updated plans for Java EE 8 and Java EE 9. The plans include adding support for dynamic configuration, health-checks, NoSQL, fat-jars, eventual consistency, multi-tenancy, dynamic discovery and circuit breakers.
This session will explain the situation including the details of what is proposed for Java EE 8 and Java EE 9. The talk will end with what all us need to do about it now. We will also discuss the critical role Java EE and it’s APIs play in maintaining the health of the entire Java ecosystem.