The need for OSGi

                                                         and the SpringSource dm Server




Copyright 2...
Who is this guy anyway?


      •Alef Arendsen (Dutch)
                  – Co-founder of SpringSource
                  – ...
Complexity is your Enemy!

  “Complexity leads to disaster. Your application should be built
    around simple constructs ...
Toward Lean Software

             “Lean software is an approach to building software that
          promotes simplicity a...
Towards modular middleware

            “...thus a container is no longer a fixed monolithic concept,
              but a ...
Copyright 2007   SpringSource.   Copying, publishing or distributi   ng without   express written permission is prohibited.
Java API 1.0.2 (9 in total)




Copyright 2007   SpringSource.   Copying, publishing or distributi   ng without   express ...
Java API 1.1.3 (25 in total)




Copyright 2007   SpringSource.   Copying, publishing or distributi   ng without   express...
Java API 1.2                                                               (59 in total)




Copyright 2007   SpringSource...
Java API 1.3 (76 in total)




Copyright 2007   SpringSource.   Copying, publishing or distributi   ng without   express w...
Further evolution of Java


      •Java                      1.4         had               135 packages
      •Java       ...
Spring Framework


      •Spring                         1.0 – 95 packages
      •Spring                         1.1 – 110...
Spring Framework


      •It looks like we continue to keep on
      dumping stuff in there!




Copyright 2007   SpringSo...
Before we move on...


      •We do seem to get more stuff done
      •Spring 3.0 for example
                  – Introduc...
The types problem


      •All these types do form a problem though
                  – Larger footprint of our applicatio...
The services problem


      •Even if we fix the types problem
                  – We still can't seem to share services i...
It's all about modularity and sharing




Copyright 2007   SpringSource.   Copying, publishing or distributi   ng without ...
Using OSGi to solve


      •The types problem
                  – Export-Package: I offer types in package XYZ
          ...
On to the IDE




Copyright 2007   SpringSource.   Copying, publishing or distributi   ng without   express written permis...
So what if I don't want OSGi


      •Spring + Tomcat: a widely used combo
      •Tomcat however does not have everything ...
Questions?
                        We offer training session in Milano & Roma.
                 Visit http://www.springsou...
Upcoming SlideShare
Loading in …5
×

Server Day 2009: Spring dm Server by Alef Arendsen

1,365 views
1,312 views

Published on

Alef Arendsen presentation at the Application Server Day 2009, discussing the latest innovations in Spring dm Server 1.0

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

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

No notes for slide

Server Day 2009: Spring dm Server by Alef Arendsen

  1. 1. The need for OSGi and the SpringSource dm Server Copyright 2007 SpringSource. Copying, publishing or distributi ng without express written permission is prohibited.
  2. 2. Who is this guy anyway? •Alef Arendsen (Dutch) – Co-founder of SpringSource – Currently strategic advisor at JTeam – Key contributor to Spring Framework •SpringSource – The company creating and sustaining many open source technologies • Spring, Integration, Web Flow, Batch, et cetera • AspectJ, Groovy, Grails, ActiveMQ, ServiceMix • Apache Tomcat, Apache HTTPd – Consulting, training and support subscriptions for these many open source technologies and other value-adds Copyright 2007 SpringSource. Copying, publishing or distributi ng without express written permission is prohibited. 2
  3. 3. Complexity is your Enemy! “Complexity leads to disaster. Your application should be built around simple constructs and understandable layers, which combine to perform complex tasks. The code itself, however, should avoid complexity at every stage. This is much easier to say than to do, though, since many programmers are afraid of missing important pieces, or of oversimplifying.” -- Justin Gehtland Copyright 2007 SpringSource. Copying, publishing or distributi ng without express written permission is prohibited.
  4. 4. Toward Lean Software “Lean software is an approach to building software that promotes simplicity and minimizes resource usage. Forrester analyst John Rymer says he believes the application development industry must move to lean software as the next development paradigm to move ahead. Lean software could be the antidotes to bloated vendors and could be helpful in a down economy.” -- Daryl K. Taft – eWeek ( December 2008) Copyright 2007 SpringSource. Copying, publishing or distributi ng without express written permission is prohibited.
  5. 5. Towards modular middleware “...thus a container is no longer a fixed monolithic concept, but a runtime infrastructure that can be assembled from existing building blocks. There's no longer a set menu of declarative middleware services; you can create your own selection à la carte...” -- Rod Johnson – J2EE without EJB (2004) Copyright 2007 SpringSource. Copying, publishing or distributi ng without express written permission is prohibited.
  6. 6. Copyright 2007 SpringSource. Copying, publishing or distributi ng without express written permission is prohibited.
  7. 7. Java API 1.0.2 (9 in total) Copyright 2007 SpringSource. Copying, publishing or distributi ng without express written permission is prohibited. 7
  8. 8. Java API 1.1.3 (25 in total) Copyright 2007 SpringSource. Copying, publishing or distributi ng without express written permission is prohibited. 8
  9. 9. Java API 1.2 (59 in total) Copyright 2007 SpringSource. Copying, publishing or distributi ng without express written permission is prohibited. 9
  10. 10. Java API 1.3 (76 in total) Copyright 2007 SpringSource. Copying, publishing or distributi ng without express written permission is prohibited. 10
  11. 11. Further evolution of Java •Java 1.4 had 135 packages •Java 5– 166 packages •Java 6– 203 packages •Java 7– 204 packages (in the current beta) Copyright 2007 SpringSource. Copying, publishing or distributi ng without express written permission is prohibited. 11
  12. 12. Spring Framework •Spring 1.0 – 95 packages •Spring 1.1 – 110 packages •Spring 1.2 – 137 packages •Spring 2.0 – 197 packages •Spring 2.5.6 – 231 packages •Spring 3.0 milestone 1 – 232 packages Copyright 2007 SpringSource. Copying, publishing or distributi ng without express written permission is prohibited. 12
  13. 13. Spring Framework •It looks like we continue to keep on dumping stuff in there! Copyright 2007 SpringSource. Copying, publishing or distributi ng without express written permission is prohibited. 13
  14. 14. Before we move on... •We do seem to get more stuff done •Spring 3.0 for example – Introduces REST support – Incorporates XML marshalling support • With JiBX, JAXB, XStream • With XMLBeans and Castor – Introduces an expression language •We write applications – That are more feature-rich – Are better to interface with – Et cetera Copyright 2007 SpringSource. Copying, publishing or distributi ng without express written permission is prohibited. 14
  15. 15. The types problem •All these types do form a problem though – Larger footprint of our applications • Ever heard of 10 to 50 MB WAR or EAR files? – Larger footprint of infrastructure software • If you've ever installed <insert-favorite-vendor>'s application server, you know what I mean – With changing infrastructure landscape this is going to form a real problem very soon (think cloud, et cetera)! Copyright 2007 SpringSource. Copying, publishing or distributi ng without express written permission is prohibited. 15
  16. 16. The services problem •Even if we fix the types problem – We still can't seem to share services in an elegant way! – To be able to share services • You have to write web services • You have to write RMI interfaces – Redeployment of services seems to be quite hard Copyright 2007 SpringSource. Copying, publishing or distributi ng without express written permission is prohibited. 16
  17. 17. It's all about modularity and sharing Copyright 2007 SpringSource. Copying, publishing or distributi ng without express written permission is prohibited.
  18. 18. Using OSGi to solve •The types problem – Export-Package: I offer types in package XYZ – Import-Package: I need types from package XYZ •The services problem – <osgi:service/>: I offer a instance of a service – <osgi:reference/> I need an instance of a service Copyright 2007 SpringSource. Copying, publishing or distributi ng without express written permission is prohibited. 18
  19. 19. On to the IDE Copyright 2007 SpringSource. Copying, publishing or distributi ng without express written permission is prohibited.
  20. 20. So what if I don't want OSGi •Spring + Tomcat: a widely used combo •Tomcat however does not have everything you might need such as cluster management, diagnostics and other monitoring and management features •SpringSource tc Server – The Tomcat you know – The enterprise capabilities you need – Nothing new to learn, just plain Tomcat + some extras – Commercial offering, easy way to get started (€2500,= for 4 CPUs/sockets & a training seat) Copyright 2007 SpringSource. Copying, publishing or distributi ng without express written permission is prohibited. 20
  21. 21. Questions? We offer training session in Milano & Roma. Visit http://www.springsource.com/training for more info. There are also possibilities to do a training in-house. Further information about dm Server, tc Server and SpringSource Tool Suite, visit http://www.springsource.com Copyright 2007 SpringSource. Copying, publishing or distributi ng without express written permission is prohibited.

×