Microservices on Anypoint Platform

MicroservicesOn Anypoint Platform

Microservices are a top tech trend for 2016

2

Business model transformation

Enhancing customer

experiences

New products and services

3

Today’s speakers

Sandeep Singh KohliDirector of Marketing,

Platform

Rupesh RamachandranSenior Solutions

ConsultantJohn D’Emic

Client Architect Nial Darbey

Senior Solutions Consultant

Agenda

1. What are Microservices?

2. Microservices on Anypoint Platform

3. Decomposition of the Monolith and Continuous delivery

4. Domains and responsibilities of Microservices

4

What are Microservices?

Basics

6

Fundamental Building Block

Core Business Capability Participant in Customer transaction

Consumption Modes

7

REST API Event-driven Composition

Design Characteristics

• Business oriented

• Adaptable

• Autonomous

• Loosely coupled

• Discoverable

• Fault tolerant

• Composable 8

Microservices on Anypoint Platform

Build

Engage

Test

Model

Simulate

Validate

Solicit Feedback

Design

ManageAPI Designer

Mocking Services

Anypoint StudioMUnit

API Console

API Portal

Analytics API Notebook

End-to-End Microservice Development Lifecycle

Anypoint Exchange

Anypoint Exchange

Anypoint Exchange

Build

Engage

Test

Model

Simulate

Validate

Solicit Feedback

Design

ManageAPI Designer

Mocking Services

Anypoint StudioMUnit

API Console

API Portal

Analytics API Notebook

End-to-End Microservice Development Lifecycle

Build

Engage

Test

Model

Simulate

Validate

Solicit Feedback

Design

Manage

Discover, Contribute, Collaborate, Innovate

Anypoint Exchange

Anypoint Exchange

Anypoint Exchange

Anatomy of a Mule microservice

Mule deployable

archive(.zip)Mule Runtime

Logic

Connectivity

API Contract

RAML specification• Traits• ResourceTypes• SecuritySchemes• Re-usable properties….

Connectivity• MQ, Database, SOAP,

HTTP, SaaS, COTS software

• Protocol implementation

• Connections/resources management

• Pooling…

Business Logic flows• Routing• Enrichment• Transformation• Aggregation• Parallel execution• Splitting….

CloudHub

Mule microservice on CloudHub

• Fully hosted and managed• Secure, scalable, HA, DR• Self-serve• Global• No Microservice Premium

Mule Runtime

Logic

Connectivity

API Contract

Decomposing the Monolith & Continuous Delivery

• Large team, potentially complex code base

• Limited opportunities for reuse

• Potentially difficult to scale

• Harder to achieve operational agility

• Typically limited in languages dictated by the runtime container

16

Decomposing the Monolith

17

Decomposing the Monolith

● Small teams focusing on modest code bases

● Re-use via HTTP APIs and messaging protocols

● Deployment via independently packaged services

● Service-by-service choice for language and deployment runtime

18

Continuous Delivery

● Design the contract for a microservice

● Develop the microservice implementation

● Test the microservice● Automate the Release of

the microservice

3rd Party Tools

Build Runtime Platform Deploy, Manage, Scale

CI/CD

Studio

JUnit

Dev

Test

Stage

Prod Anypoint Platform (on-premises)

Runtime Manager

API Manager Exchange

Com

mit

ShipImage

Development

Operations

Mgmt Agent

Self-service of Microservice Consumption

• Decentralization of Microservice access requires API Management

• Publication of APIs across LOBs

• Adapt Microservices with auto-generated Proxies

• Apply policies in order to tailor Microservices for specific usage

20

Domains and Responsibilities of Microservices

Business Domain Orientation

• Focus on Business domains

• Cross-domain integration through Experience APIs

• Avoids the Monolith22

Microservice Responsibilities

23

Summary

• Holistic, platform-based - API-led connectivity

• Platform for:- new composite applications - connect to existing disparate systems.

• Pragmatic approach - LoB and IT as partners to build and innovate 24

25