10 Reasons to use OSGi for your next cloud app

Learn why OSGi is a super productive technology to build modern (web) applications.

Transcript

1. Ten reasons to use OSGi for your next cloud app @pbakker
2. Paul Bakker @pbakker
3. Reason nr Developer Productivity 1
4. Code Maven build full project Deploy to app server Re-initialize full app Typical Java development workflow…
5. Typical OSGi development workflow… “Like working with a scripting language”
7. How does it work? Class loader per bundle OSGi supports updating a bundle On compile, bundle is rebuild and re-installed
8. Reason nr No more ClassNotFoundException 2
9. Imports / Exports OSGi bundles define explicitly what classes they import Imports must be exported by some bundle Imports are calculated from your byte code
10. Example code z
11. Import packages are generated Import-­‐Package:     org.apache.felix.dm;version=“[4.0,5)",   org.osgi.framework;version="[1.3,2)"
12. The framework tells you what’s missing Unable to resolve 1.0: missing requirement [1.0] osgi.wiring.package; (&(osgi.wiring.package=org.apache.felix.dm) (version>=4.0.0)(!(version>=5.0.0))) Forgot  to  install  Dependency   Manager  bundle…
13. API versioning Deploy multiple versions of an API Import a specific version range Semantic Versioning
14. Reason nr Great for Cloud Deployment 3
15. Great for (Cloud) deployment No application server Executable JAR file Very small memory footprint Perfect for building Docker containers
16. Building a binary gradle  build  export   java  -­‐jar  MyApp.jar
17. Dockerfile FROM  jeanblanchard/busybox-­‐java:8   COPY  release/myapp.jar  /app/myapp.jar   WORKDIR  /app   EXPOSE  8080   CMD  java  -­‐jar  myapp.jar
18. Great commercial support RTI Kubernetes based clusters Logging and Monitoring for OSGi Automated Blue/Green deployments
19. Reason nr Maintainable architecture 4
20. Maintainable architecture Implementation hiding Enforce module boundaries Modules during development, build and runtime
21. Bundles and services Only APIs are exported, the bundle’s contract Services provide functionality True decoupling Service Registry Bundle registering a service Bundle using a service Publish MyInterface Lookup MyInterface
22. Data Business UI Big ball of mud Big ball of mud Big ball of mud
23. Data Business UI
24. Rooms Resource AngularJS Client Rooms Service RabbitMQ Service STOMP AMQP RabbitMQ Chat Log Mongose Jongo REST Personalized Ad Generator Word Counter Product Service MySQL
25. Rooms Resource AngularJS Client Rooms Service RabbitMQ Service STOMP AMQP RabbitMQ Chat Log Mongo Jongo REST Personalized Ad Generator Word Counter Product Service MySQL Each part is a separate OSGi bundle
26. Reason nr Dependency Injection 5 @ServiceDependency
27. Register Demo component Inject dependency Lifecycle methods
28. Reason nr The road to Micro Services 6
29. Best preparation for Micro Services OSGi services are micro services within a VM Easy to migrate to remote services when needed Perfect balance between “Monolith First” and Micro Services from te get go
30. OSGi Remote Services OSGi spec for remote service discovery and invocation Pluggable discovery and transport No code changes required!
31. Client Server
32. Reason nr All the libraries you need 7
33. REST Scheduling Mongo JPA Web Resources Blob Stores Remote Services Security Email Config Components No core framework or half a zillion dependencies!
34. Amdatu REST example
35. Amdatu Mongo example Amdatu Mongo Service Setup Object Mapper Execute query
36. Reason nr Plugin systems 8 Plugin Registry Plugin Plugin Plugin
37. core.jar myplugin.jar Install plugin by installing a bundle
38. Real world examples Amdatu Bootstrap (even directly from Git repos) Spring Roo Eclipse Glassfish …
39. Reason nr Integration testing 9
40. Integration testing Looks like plain JUnit Runs in an OSGi framework
41. Reason nr Great resources to get you started 10
42. Don’t be afraid to ask! http://amdatu.org @pbakker