Written by Ashwin Karpe, Committer and Project Management Committee (PMC) Member for the Apache Camel Project | Enterprise Integration Practice Lead at Red Hat
Why is it important to incorporate microservices in your app development strategy? Let me tell you why.
February 9, 2016 — For as long as we can remember, applications have been understood as disparate and monolithic entities, each serving a unique function. Changes and modifications were made to the applications, with minimal focus on the underlying capabilities or workflows. So long as each functioned to its full potential, there was little to no attention drawn toward duplicative capabilities or workflows across applications.
Yet, as users grow to expect a responsive, interactive, and dynamic experience across a range of devices, the kind of myopic orientation that characterized application development historically will not lead to the scalability, flexibility, and speed necessary for businesses to succeed in the future.
Microservices is an application development architecture approach that not only unlocks efficiency to remain competitive in the market, but is what will also ultimately drive the sustainable mindshift of applications as a way to support total compute capacity, rather than resources to be cut given total compute capacity.
I will be speaking at Dev:Network on February 16 at 10am PST in San Francisco, CA on the emergence of microservices and their impact to business infrastructures and processes. More specifically, the impact of the following building blocks to application development:
- Microservices: How to design for them & why to design for them.
- Microbrokers: Microbrokers are broker-based messaging microservices that are deployed on demand to drive data between systems. They enable business to elastically scale on demand while maintain stateful semantics and delivery guarantees.
- Microflows: Microflows initiate enterprise scalability and integration outside of the traditional ‘hub and spoke’ model because they define well-known integration patterns and direct traffic between systems.
Microservices is no longer a nice to have; it’s a requirement for businesses to be nimble and grow nimble. It is more than a stop-gap solution. It’s an approach that when adequately scoped, strategized, and sized for your environment, can have tremendous business implications.
About the Speaker
Ashwin Karpe is a Committer and Project Management Committee (PMC) Member for the Apache Camel project at the Apache Software Foundation. He has contributed several components to the Apache Camel, ServiceMix, ActiveMQ and CXF community projects. Ashwin regularly participates in Open source discussion forums, conducts seminars/webinars and consults on open source technologies that fuel his passion and interest. In his day job,
Ashwin is the Enterprise Integration Practice Lead for North America at Red Hat with two decades of experience in designing, developing and modeling large distributed enterprise systems. Ashwin has an extensive consulting and engineering background in SOA and Distributed Computing Technologies with an extensive set of successfully executed middleware projects. While not consulting for RedHat or volunteering at Apache, Ashwin continues his pursuit of happiness in Coppell, TX with his family.
Connect with Red Hat Consulting, Training, Certification
Learn more about Red Hat Consulting
Learn more about Red Hat Training
Learn more about Red Hat Certification
Subscribe to the Training Newsletter
Follow Red Hat Training on Twitter
Like Red Hat Training on Facebook
Watch Red Hat Training videos on YouTube
Follow Red Hat Certified Professionals on LinkedIn
This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License