Jee Overview Ppt

2,071 views
1,956 views

Published on

Published in: Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,071
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Jee Overview Ppt

  1. 1. JEE Architectural Benefits Feb – 2008
  2. 2. Why JEE when we have Java
  3. 3. History of Enterprise Software <ul><li>Enterprise Requirements:-> </li></ul><ul><ul><li>Scalable </li></ul></ul><ul><ul><li>Secure </li></ul></ul><ul><ul><li>Transactional </li></ul></ul><ul><ul><li>Distributed </li></ul></ul><ul><ul><li>Portable </li></ul></ul><ul><ul><li>Robust (Performance, Availability, Integrity) </li></ul></ul><ul><ul><li>Availability </li></ul></ul><ul><li>Basically these are non-functional/operational requirements . </li></ul><ul><li>Enterprise solutions existed before J2EE, but catering specific requirement </li></ul><ul><ul><li>Bea Tuxedo for messaging </li></ul></ul><ul><ul><li>Java RMI, DCOM, CORBA etc… for distribution </li></ul></ul><ul><ul><li>Distributed Transaction monitors from Microsoft in 1998 triggered the need for having standard specification to save the investment of various other organization groundwork. </li></ul></ul><ul><ul><li>Sun/Java looked upon as savior for these Vendors (IBM, ECM, BEA, SAP, Oracle…) </li></ul></ul>
  4. 4. Java EE – Set of Specifications JavaEE is simplified* programming model to accomplish enterprise requirements.
  5. 5. Specification defining process <ul><ul><li>www.jcp.org -> Specifying the programming interfaces </li></ul></ul><ul><ul><li>Major vendors (IBM, BEA, Adobe, Google, SAP etc…) provide their resources (people) to define these specifications </li></ul></ul><ul><ul><li>All specifications are managed under the leadership of Sun </li></ul></ul><ul><ul><li>Usually specifications are developed in consent with the best in the industry. (but not always the best) </li></ul></ul><ul><ul><li>All the specifications are not part of J2EE or JEE </li></ul></ul><ul><ul><li>The specifications are required to be implemented completely in order to be certified J2EE vendor. </li></ul></ul><ul><ul><li>Tomcat implements only the portions of (We part) J2EE spec </li></ul></ul><ul><ul><li>Most of the commercial vendors are completely compliant with the spec & also develop their propriety extensions over them </li></ul></ul><ul><ul><li>Java EE as a big umbrella </li></ul></ul>
  6. 6. Container Model
  7. 7. Typical enterprise architecture
  8. 8. .NET Vs J2EE <ul><ul><li>.NET is a set of products where as J2EE is a collection of APIs </li></ul></ul><ul><ul><li>J2EE has 30+ Vendors .Net is powered by Microsoft </li></ul></ul>
  9. 9. C# Vs Java Absolute Relative
  10. 10. SOA Angle <ul><ul><li>The beauty of SOA is that it does not favor one particular platform or approach — it doesn’t matter if services come out of Java EE, .NET, Ruby on Rails, CORBA, or even COBOL </li></ul></ul><ul><ul><li>So faster/quick solutions like RoR rule the world as there will be very less up-front investment on big projects </li></ul></ul>
  11. 11. 2012 <ul><ul><li>In five years, Java EE will be the CORBA of the 21st Century </li></ul></ul>
  12. 12. Source <ul><ul><li>http://java.sun.com </li></ul></ul>

×