Dynamic Deployment Oredev 2009

Software Engineer at Luminis
Nov. 9, 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
Dynamic Deployment   Oredev 2009
1 of 43

More Related Content

Recently uploaded

CamundaCon NYC 2023 Keynote - Shifting into overdrive with process orchestrationCamundaCon NYC 2023 Keynote - Shifting into overdrive with process orchestration
CamundaCon NYC 2023 Keynote - Shifting into overdrive with process orchestrationBernd Ruecker
Product Listing Presentation-Maidy Veloso.pptxProduct Listing Presentation-Maidy Veloso.pptx
Product Listing Presentation-Maidy Veloso.pptxMaidyVeloso
How resolve Gem dependencies in your code?How resolve Gem dependencies in your code?
How resolve Gem dependencies in your code?Hiroshi SHIBATA
Dev Dives: Mastering AI-powered Document UnderstandingDev Dives: Mastering AI-powered Document Understanding
Dev Dives: Mastering AI-powered Document UnderstandingUiPathCommunity
Webhook Testing StrategyWebhook Testing Strategy
Webhook Testing StrategyDimpy Adhikary
"From Orchestration to Choreography and Back", Yevhen Bobrov "From Orchestration to Choreography and Back", Yevhen Bobrov
"From Orchestration to Choreography and Back", Yevhen Bobrov Fwdays

Featured

Introduction to Data ScienceIntroduction to Data Science
Introduction to Data ScienceChristy Abraham Joy
Time Management & Productivity -  Best PracticesTime Management & Productivity -  Best Practices
Time Management & Productivity - Best PracticesVit Horky
The six step guide to practical project managementThe six step guide to practical project management
The six step guide to practical project managementMindGenius
Beginners Guide to TikTok for Search - Rachel Pearson - We are Tilt __ Bright...Beginners Guide to TikTok for Search - Rachel Pearson - We are Tilt __ Bright...
Beginners Guide to TikTok for Search - Rachel Pearson - We are Tilt __ Bright...RachelPearson36
Unlocking the Power of ChatGPT and AI in Testing - A Real-World Look, present...Unlocking the Power of ChatGPT and AI in Testing - A Real-World Look, present...
Unlocking the Power of ChatGPT and AI in Testing - A Real-World Look, present...Applitools
12 Ways to Increase Your Influence at Work12 Ways to Increase Your Influence at Work
12 Ways to Increase Your Influence at WorkGetSmarter

Featured(20)

Dynamic Deployment Oredev 2009

Editor's Notes

  1. - Who am I? Angelo, Luminis, Apache ACE committer - We will show a case that feels familiar to most of us, and use that as a showcase for using component technology and deployment. - Will go into OSGi a little, - I will show what dynamic deployment is all about - And wrap up with a demo
  2. You start out with the idea of a great drawing application
  3. You start out with a monolithic application http://www.flickr.com/photos/minegro/3097817447/
  4. Growing software always has its peril. Customers will start demanding ‘specials’ you don’t want everyone to have, since you might want to charge for them. The specials start cluttering up your code, making it very hard to maintain
  5. Growing software always has its peril. Customers will start demanding ‘specials’ you don’t want everyone to have, since you might want to charge for them. The specials start cluttering up your code, making it very hard to maintain
  6. Build times start ramping up: engineers fire up a build shortly before lunch so they can see the results before going home that evening. http://xkcd.com/303/
  7. It soon becomes hard to enforce your architecture, due to all of the specials that need to ‘hook in’ somewhere http://www.flickr.com/photos/lance_mountain/142158155/sizes/o/ http://www.answersingenesis.org/assets/images/articles/utp/chap8/userkafs-pyramid.jpg
  8. It soon becomes hard to enforce your architecture, due to all of the specials that need to ‘hook in’ somewhere http://www.flickr.com/photos/lance_mountain/142158155/sizes/o/ http://www.answersingenesis.org/assets/images/articles/utp/chap8/userkafs-pyramid.jpg
  9. You have a load of code, nicely communicating through interfaces. Note that in many applications some sort of layering shows up.
  10. We overlay the Java packages here. These are quite fixed: how long would ik take you to restructure your packages? This really is the basis for subsequently designing both: - your package view / development view - your deployment view Reference the 4+1 view here: - to remain agile, you have to constantly manage your dependencies: -> test, how quickly could you completely redesign your packages??? (hours, days, weeks?)
  11. So, we group these packages into components; this could be the basis of your package/deployment view. Note that while packages are rather fixed, carving up this package space isn’t necessarily: we can rather easily change the packaging, or even have various forms together.
  12. (from osgi.org) OSGi is based on the “home gateway” market, but later on profiled itself as ‘universal middleware’. Now, it just uses the term ‘dynamic module system’. OSGi is often seen as an application server, but it actually spans the range from embedded devices to enterprise servers.
  13. The specification consists of two parts: a core specification and a service compendium. The core describes the framework itself and some core services. The compendium describes a lot of service interfaces, standardized so different implementations can be substituted easily. Of most of these services, multiple open source implementations exist already. Recently, version 4.2 of the specification has been has been released, focussing mostly on enterprise-related elements.
  14. The framework itself is build out of a couple of layers, starting at the bottom with the execution environment, which describes the exact set of Java API’s that are considered part of the environment. By having different environments, bundles can specify for example if they can run on Java 1.4, 5 or 6. You can even make your own environments. On top of that, the module, life cycle and service layers are built.
  15. At the module layer, the software is grouped into bundles (also known as plugins in Eclipse), where each bundle contains zero or more Java packages and optionally some other resources or even native libraries. Some of these packages are exported, meaning they can be used by other bundles, others are private and only visible within a specific bundle. Packages that are exported by one bundle, can be imported by another. The exporter specifies a version number for a package. The importer can specify a range of versions it is compatible with. At run-time the framework will resolve such dependencies. All this allows you to keep implementations private, only exposing API’s.
  16. On top of that, the life-cycle layer determines the life-cycle of individual bundles. Basically, bundles can be installed, started, stopped and uninstalled. Furthermore, an installed bundle can be updated anytime. Finally, you can uninstall a bundle if you don’t need it anymore. The “starting” and “stopping” states have hooks for you as the bundle developer to actually make your bundle do something. By implementing the BundleActivator interface, the framework will invoke your start() and stop() methods. You will also get a BundleContext which is basically a reference to the API to talk to the container.
  17. Finally, the service layer contains a registry where services are published. Each bundle can register any number of services in the service registry. A service is registered using the fully qualified name of its interface. Furthermore, you can add any number of properties to this service. Both the name and properties can then be used again by others that query the registry. A fast and powerful LDAP based query language is used for that.
  18. The compendium, as mentioned before, contains an extensive list of standard service descriptions. Services like HTTP, logging, preferences and pluggable XML parsers are things that a lot of applications share and by sticking to these services, you get excellent substitutability, where you can develop with light weight implementations and then at runtime switch to more heavy weight ones.
  19. at the very least, your developers are happy now: they have components, and the complexity of the codebase is manageable. Your support personnel isn’t http://www.flickr.com/photos/mpsfender182/2681841205/
  20. at the very least, your developers are happy now: they have components, and the complexity of the codebase is manageable. Your support personnel isn’t http://www.flickr.com/photos/mpsfender182/2681841205/
  21. Goals of Dynamic Deployment
  22. What exactly is deployment?
  23. What exactly is deployment?
  24. History is important
  25. History is important
  26. History is important
  27. The topology. Disclosure: I am an Apache ACE committer, Apache ACE is an open source project that aims to build a system with the characteristics described before.
  28. Leaving the topology for a while, let’s look at the logical aspects.
  29. First: DEPENDENCY MANAGEMENT Note that the repository has versions too...
  30. FEEDBACK
  31. management agent stores all life cycle related events in an audit log this log gets synchronized back to the server There is a part I did not yet talk about: the management agent.
  32. DEPLOYMENT Leverages standard OSGi features; ‘management agent’ is mentioned in the spec, but not as a component. - module / lifecycle layer - PackageAdmin - StartLevels - ConditionPermissionAdmin
  33. Management agent is a set of activities, which can be deployed as a (number of) component(s), but also added into the framework.
  34. We borrowed a little something from the OSGi specification, known as the Deployment admin Now, how does that all fit together?
  35. Way too dangerous; I prepared some screencasts. http://dl.dropbox.com/u/2438787/www/2009-10/1-Community%20edition.mov http://dl.dropbox.com/u/2438787/www/2009-10/2-Pro%20edition.mov http://dl.dropbox.com/u/2438787/www/2009-10/3-Specials.mov http://dl.dropbox.com/u/2438787/www/2009-10/4-Customer%20support.mov