Integrating microservices with JBoss Fuse
•
3 likes•1,454 views
Monolithic applications can be successful, but increasingly people are feeling frustrations with them - especially as more applications are being deployed to the Cloud. Change cycles are tied together - a change made to a small part of the application, requires the entire monolith to be rebuilt and deployed. Over time it's often hard to keep a good modular structure, making it harder to keep changes that ought to only affect one module within that module. Scaling requires scaling of the entire application rather than parts of it that require greater resource. Microservices is a software architectural style, in which complex applications are composed of small, independent processes communicating with each other using language-agnostic APIs. These services are small, highly decoupled and focus on doing a small task.
More Related Content
What's hot
What's hot (20)
Similar to Integrating microservices with JBoss Fuse
Similar to Integrating microservices with JBoss Fuse (20)
Recently uploaded
Recently uploaded (20)
Integrating microservices with JBoss Fuse
- 1. Integrating Microservices with JBoss Fuse Evan Wong Middleware Solution Architect
- 2. 2 Monolith
- 3. 3 It’s so hard to move
- 4. 4 Monolithic Application SCALE ! Redeploy entire application for a small change ! Longer downtime for deployment ! Requires scaling of entire application
- 5. What is Microservices? 5 Microservices is a software architecture style, in which complex applications are composed of small, independent processes communicating with each other using language- agnostic APIs. These services are small, highly decoupled and focus on doing a small task. Wikipedia
- 7. 7 Assemble
- 8. 8 Reuse
- 10. 10 Evolution of Microservices Architecture
- 12. Benefits of Microservices Small code base = Faster Software Delivery Scale Easier Easy to understand & maintain 12
- 13. Why Integration is so hard? Multiple Transport Protocol Different Message Format Heterogenous Platforms 13
- 14. JBoss Fuse 14 Lightweight Open Source Integration Bus
- 15. Apache Camel 15 Apache Camel ™ is a versatile open-source integration framework based on known Enterprise Integration Patterns. http://camel.apache.org
- 16. Why the name Camel? 16 It stands for Concise Application Message Exchange Language A Camel can carry 4 times the load of other beasts of burden The creator loves Camel cigarettes Very fast, even when the going gets tough!
- 17. The Power of Camel
- 21. Apache ActiveMQ 21 Apache ActiveMQ ™ is the most popular and powerful open source messaging and Integration Patterns server. http://activemq.apache.org
- 22. The Value of ActiveMQ Asynchronous Processing Location Transparency Multiple Clients 22
- 24. Why JBoss Fuse for Microservices 24 ! Comprehensive ESB – make integration easier ! Small footprint & lightweight engine ! Not "reinventing the wheel” - Developers can focus on solving business problem ! Lower total cost of ownership
Editor's Notes
- Change on a small part of the application but requires the entire monolith to be rebuilt and deployed. Scaling requires scaling the entire application Monolithic applications can be successful, but increasingly people are feeling frustrations with them - especially as more applications are being deployed to the cloud . Change cycles are tied together - a change made to a small part of the application, requires the entire monolith to be rebuilt and deployed. Over time it's often hard to keep a good modular structure, making it harder to keep changes that ought to only affect one module within that module. Scaling requires scaling of the entire application rather than parts of it that require greater resource.
- In short, Microservices is about architectural style: building applications as suites of services.
- SOA = bigger, coarse grain, high coupling Microservices = smaller, fine grain, low or no coupling
- As well as the fact that services are independently deployable and scalable, each service also provides a firm module boundary, even allowing for different services to be written in different programming languages. They can also be managed by different teams .
- Enterprise Integration Patterns provides a consistent vocabulary and visual notation to design and document integration solutions independent from implementation technologies.
- Enterprise Integration Patterns provides a consistent vocabulary and visual notation to design and document integration solutions independent from implementation technologies.
- Management API Registry Visual Camel Route MQ Resources