Taming a Dinosaur - History and Evolution of Jakarta EE
•Download as PPTX, PDF•
1 like•158 views
Jakarta EE / Java EE is still important framework. This talk is meant for developers that does not have much experience on subject. It introduces Java EE and it's meaningfulness to software industry.
Recommended
Recommended
More Related Content
Recently uploaded
Recently uploaded (20)
Featured
Featured (20)
Taming a Dinosaur - History and Evolution of Jakarta EE
- 1. Jari Timonen Taming a dinosaur History and Evolution of Jakarta EE
- 2. Jari Timonen Who is talking? • Jari Timonen, Pirkkala • Twitter: @jtimonen, Github: zenix, ircnet: zenix • Working since 2001 • Basic Industry to Finance to Telco • Cloud • Relevant certifications • Oracle Certified Master, Java EE 5 Enterprise Architect • Sun Certified Developer for the Java 2 Platform (SCJD) • Sun Certified Programmer for the Java 2 Platform, Standard Edition 5 (SCJP)
- 3. Jari Timonen What is Jakarta EE?
- 4. Jari Timonen Where does Jakarta EE come from?
- 5. Jari Timonen J2EE, Java EE and Jakarta EE. WTF? • J2EE 1.2 (December 12, 1999) • J2EE 1.3 (September 24, 2001) • J2EE 1.4 (November 11, 2003) • Java EE 5 (May 11, 2006) • Java EE 6 (December 10, 2009) • Java EE 7 (June 12, 2013 ) • Java EE 8 (August 31, 2017) • Jakarta EE (September 12, 2017)
- 6. Jari Timonen The Golden Times J2EE 1.2 – 1.4 1999 - 2006
- 8. Jari Timonen The Goose That Laid the Golden Eggs Enterprise Java Beans 1999 ->
- 9. Jari Timonen The Dark Ages J2EE 1.2 – 1.4 1999 - 2006
- 12. Jari Timonen J2EE Challenges • Technology • Reference implementation / application • Challenges
- 13. Jari Timonen The Horrow Show PT1 (ejb-jar.xml)
- 14. Jari Timonen The Horrow Show PT2 (ejb-jar.xml)
- 15. Jari Timonen The Horrow Show PT3 (ant)
- 16. Jari Timonen XDoclet to The Rescue
- 17. Jari Timonen Hurray for Maven
- 19. Jari Timonen The Modern Age Begins Java EE 5 2006 ->
- 20. Jari Timonen Age of improvement Java EE 6 2009 ->
- 22. Jari Timonen Why anyone used or would use Jakarta EE?
- 23. Jari Timonen Why I would not use Jakarta EE?
- 24. Jari Timonen Why Jakarta EE seems so big, ugly and hairy?
- 25. Jari Timonen Thank you for listening Questions?
Editor's Notes
- Jakarta used to Difference between Java and Javaee is ava EE. Jakarta EE is Collection definitions and reference implementations which solve software, integration and architectural problems It Includes implementations from traditional small web development to wide range of Enterprise applications
- Until September 12, 2017 Java Community Process which coordinated development and definitons. It included individuals and big companies that had intrest in Java EE. Individual specification was called Java Specification Request Vendor driven, slow Oracle handed over Java EE to Eclipse Foundations September 12, 2017. Now driving of the direction is done by Jakarta EE Working Group. Anyone can join, just join the mailin list: Jakarta.EE-wg@eclipse.org There is also Separate Eclipse Committer membership (you need to be voted to be member) Top level organization is Project Management Comitee which oversees projects. Technical direction is managed by group itself Vendor neutral, agile
- J2EE yook web development giant leaps forward. Popularisation and offered new job possibilities for lot’s of people. Huge amounts of people got re-educated or transfered from c/++ Mandatory to know at the time if you wanted good salary Salaries excellent Hipsters before it was invented EJB was steaming hot! PHP was/is not a real option serious web development. It lacked lot’s of features needed in enterprise world
- After Smalltalk JSP etc Ejb up, Left jsp Controller servlet right
- Server side component which enabled distributed, transactional (remote transactions) and secure applications. It encapsulates business logic and persistent layer It scales automatically Only one call needed from frontend Many types: Statefull / Stateless / Singleton (later) Session Bean Message Driven Bean for JMS This was all before Rest was even invented
- Lot’s of manual work had to be done. Applications were getting bigger and more complex. Labour intensive Really steep learning curve
- J2EE Design Patterns When I started
- First glance of Java/Jakarta EE
- Challenges of J2EE Incorrectly used and misunderstood technologies Reference implementation/application directed people to misuse in their applications. You do not need to use all of them Some misuses and annoyances - Business logic in frontend JSP - XML configurations - EJB 1-2 too complicated
- Totally horrible. Session bean definition
- Entity bean definition
- Too much manual work. Reminds of current and old packaging mechanism of node.js (grunt, gulp, webpack)
- Automatic generation of ejb stuff
- Maven replaced ANT
- And then community started to revolt Struts, Spring and Hibernate were extremely popular
- Java EE 5 Brought Open Source community standards to Java EE This was partly possible because introduction of Java 5 which brough annotations Spring, Hibernate and Toplink Java EE did not migrate, merely copied best of them They started to use Convention over configuration, Annotation for configuration. This means that there are sensible defaults… Radical change in development Too late?
- Profiles: Web - All that’s needed for web development full monty - All Enterprise technologies https://en.wikipedia.org/wiki/Java_EE_version_history#Java_EE_6_(December_10,_2009)
- Built in: - Security - Proven and tested - Transactions (local/remote/joining) - Scales in software level without gimics - Easier to sell in big or secure organisations
- Application Server price is too much I do not need transactions I do not need strict security I do not know how and my friends does not know Making simple web pages Not a real competition for Nodej.js. Different use cases cases.
- There is lot’s of different technologies and understanding takes time Efficient Jakarta EE architecture requires broad understanding of techologies and servers Attitude