Centralized control over a monolithic IT architecture is giving way to agile microservices that are easily consumable and scalable. How should businesses in the middle of this transition think about the move to microservices? Azuqua and Apigee share how companies make the transition and gradually shed older toolsets.

1. ARE ESBs RELEVANT IN THE AGE
OF MICROSERVICES?
ALAN HO, APIGEE
NIKHIL HASIJA, AZUQUA

2. INTRODUCTIONS
ALAN HO
APIGEE
HEAD OF DEVELOPER
PROGRAMS
NIKHIL HASIJA
AZUQUA
CEO

3. A BRIEF HISTORY OF ESBs, APIs, AND
MICROSERVICES

4. THE 90s Called – they want their tech back
ESBS CAME ABOUT
FROM A NEED TO
MANAGE PROTOCOLS.
INHERENTLY BUILT FOR
HEAVY WEIGHT
ARCHITECTURES FOR
INITIATIVES THAT TAKE
MONTHS.

5. THE REAL QUESTION: CAN YOU GET GOING FAST?
ANOTHER WAY OF SAYING THIS: ESB IS NOT A CONSUMPTION STRATEGY AND DEFINITELY NOT ONE BUILT FOR SPEED
AND SCALE.

6. TO ESB OR NOT TO ESB
• PROS
• CONNECTOR ORIENTATION
• CONS
• MESSAGE ORIENTED ARCHITECTURE
• TOO MUCH WORK FOR VERY LITTLE OUTCOME
• DOES NOT SCALE
• DOES NOT PROCESS AT SPEED
• TAKES TOO LONG
• DEATH BY TRANSFORMATION

7. WHERE TECH TEAMS STRUGGLE
• Too much to do
• Can’t deliver fast enough
• Not enough resources to support
all business needs
• Business stakeholders add
requirements as new needs
arise

8. MICROSERVICES NIRVANA
Data Data Service Service
Service Service Service Data
Workflow Processes Apps Widgets
Web UI Mobile UI User Layer
Consumption Layer
Service Layer

9. WHY IS THIS HARD
EASY INTEGRATIONS
• Simple data syncs to support ad hoc reports
• One-way data calls to systems of record
• Simple email notifications
HARD INTEGRATIONS
• Automated workflows that eliminate error-prone,
manual work
• Continuous data synchronization to enable
always-right dashboards
• Real-time availability of data in the system
business stakeholders use
• Asynchronous usage of microservices

10. BEST PRACTICES FOR CREATING MICROSERVICES
• Atomic, usage first orientation (i.e. focused around enabling business outcomes)
• Built to be absorbed through the network
• Built-in failure tolerance
• Completely stateless
• Horizontally scalable
• Follow a request-response pattern
• Expose consumption blueprint

11. Azuqua is the consumption platform for the APIs, microservices, and processes
to power the agile, digital enterprise
8/31/16 11Confidential.

12. AZUQUA & APIGEE
DEMO

13. THANK YOU!
azuqua.com
connect@azuqua.com
Download Azuqua’s
DEFINITIVE GUIDE TO API CONSUMPTION
go.azuqua.com/api-consumption-strategy-whitepaper.html