The software integration market is heating up with many new-entry cloud-based vendors and a sea-change in customer expectations. What does this means for traditional Enterprise Application Integration? How do modern integration tools add value and where is the integration market heading? Microsoft is leading the charge forward with a new emphasis on microservice-based integration. What are microservices? How do they relate to iPaaS and what does the Azure-based microservice ecosystem offer? How will this emerging world transform integration in the future?
Nell’iperspazio con Rocket: il Framework Web di Rust!
Microservices and the Cloud-Based Future of Integration
1. tSponsors
Charles Young
Solidsoft Reply, Principal Consultant
Microservices and the Cloud-Based Future
of Integration
BizTalk Summit 2015 – London
ExCeL London | April 13th & 14th
2. Charles Young
Principal Consultant
Solidsoft Reply
www.solidsoftreply.com
geekswithblogs.net/cyoung
Specialist Microsoft development consultancy
1993 Microsoft certified application developers
1999 Microsoft managed partner
2000 Microsoft BizTalk integration specialists
2002 Microsoft global advisory council
2010 Windows Azure “cloud first” solutions
2013 Joined Reply
Microsoft® Global Partner Network™
PARTNER OF THE YEAR
2006 Winner Application Integration
2008 Finalist Application Integration
2010 Finalist Custom Development
2011 Winner Application Integration
2012 Finalist Government Solutions
2013 Winner Cloud Solutions
Today
UK “SME” £10M revenue
Core team of 60 specialists
100% Microsoft focus
ISO 9001 & 27001 compliant
UK Government IL3 certified
International Society for Pharmaceutical
Engineering GAMP5
who we are
5. Integration • Adaptation
• Mediation
• Transformation
• Routing
• Orchestration
Enterprise
Application
Integration
Data
Integration
Electronic
Data
Integration
• Extract, Transform and
Load
• Data Warehousing
• Change Data Capture
• Federation
• Master Data Management
• B2B
• EDIFACT/X12
• TRADACOMS
• HL7
• Partner Management
• VANs
6. Enterprise Application Integration (EAI)
Web Site Email
Mobile
Devices
CMS
CRM
ERP
Channels
Line-of-Business
Back Office
Cloud ServicesTrading Partners
Data
Services
Hub
Adaptation
Mediation
Orchestration
7. ESB Service Integration
Web Site Email
Mobile
Devices
CMS CRM ERP
Distributed Services
On-Ramp
Services
Off-Ramp
Services
Adaptation
Mediation
Routing
Bus
8. ESB Service Integration
Web Site Email
Mobile
Devices
CMS
CRM
ERP
Channels
Line-of-Business
Back Office
Cloud ServicesTrading Partners
Data
Services
9. Layered Architecture
Web Site Email
Mobile
Devices
CMS CRM ERP
Data / Integration
Business Logic
(Application Domain)
Presentation
Mediation
Boundary
10. Hexagonal Architecture - Alistair Cockburn
Web Site
Mobile
Devices
Email
CMS
CRM
ERP
Channels
Line-of-Business
Back Office
Cloud ServicesTrading Partners
Data
Services
Application
Domain
Ports &
Adapters
19. Microservices in Hexagonal Architecture
Web Site
Mobile
Devices
Email
CMS
CRM
ERP
Channels
Line-of-Business
Back Office
Cloud ServicesTrading Partners
Data
Services
Application
Domain
Ports &
Adapters
Microservices
20. Microservice Principles
Monolith Monolith
Monolith
Monolith
Presentation
Data / Integration
Microservices
Avoid centralised governance
and management
Use lightweight communicationDeploy, host and version independentlyOrganise around business capabilitiesDo one thing and do it wellDecompose monoliths into
microservices
MicroserviceMicroservice
REST
No container needed
28. Azure Containers Today
MABSApp Service
Web Apps
Mobile Apps
API Apps
BizTalk Apps
Logic Apps
PaaS Roles
Web Roles
Worker Roles
29. Windows Server Containers
Windows Process
Windows Process
Windows Server Container
Windows Process
Hyper-V Container
Windows Process
OS Kernel
Docker Engine
Docker Client
30. Bins & LibsBins & LibsBins & Libs
Docker
Kernel
OS
Docker
Engine
Bins & Libs Bins & Libs Bins & Libs
Docker
Container
Docker
Container
Docker
Container
Docker
Container
Docker
Container
Docker
Container
Docker
Container
Docker
Container
Docker
Container
Docker
Container
Docker
Container
Docker Hub
Public & Private Repos
Local Registry
Base Image
Read Only
Writeable
Bin & Libs
Base
Docker
Client
Tools / API
Containership
Base
45. Thank You!
Charles Young
Principal Consultant
Solidsoft Reply
www.solidsoftreply.com
geekswithblogs.net/cyoung
Specialist Microsoft development consultancy
1993 Microsoft certified application developers
1999 Microsoft managed partner
2000 Microsoft BizTalk integration specialists
2002 Microsoft global advisory council
2010 Windows Azure “cloud first” solutions
2013 Joined Reply
Microsoft® Global Partner Network™
PARTNER OF THE YEAR
2006 Winner Application Integration
2008 Finalist Application Integration
2010 Finalist Custom Development
2011 Winner Application Integration
2012 Finalist Government Solutions
2013 Winner Cloud Solutions
Today
UK “SME” £10M revenue
Core team of 60 specialists
100% Microsoft focus
ISO 9001 & 27001 compliant
UK Government IL3 certified
International Society for Pharmaceutical
Engineering GAMP5
who we are
Editor's Notes
After getting some feedback, I have re-worked this slide from the version presented at the BizTalk Summit 2015 conference. The points to note here are really central to the App Service value proposition, but I didn’t really manage to get them across as clearly or fully as I wished.
Although, like other iPaaS offerings, Microsoft provide us with a container, this is a container for anything we might wish to use from the rich ecosystem of services (microservices, etc.,) which Microsoft hopes will grow around App Service. This is the very opposite of most iPaaS offerings which are not in a credible position to grow a significant non-proprietary ecosystem. Most iPaaS technologies only allow proprietary components from the single vendor (obviously, these may be able to invoke custom code or external services). Some are attempting to grow an ecosystem around their connector model, but it is unlikely that most will ever be able to achieve the volume and choice that App Service will (probably) achieve. The ecosystem is central here. By (in a future release) hooking it into the Azure Market Place, as well as public and private galleries, Microsoft is opening up models which third party companies can use to create revenue streams. This is ‘AppStore for Microservices’.
Another important point is that, although like other iPaaS technologies, App Service provides a workflow engine, this is decoupled entirely from the microservices that it orchestrates. Again, this is a very different model to most other iPaaS offerings which tightly couple their adaptation, mediation and transformation componentry to a workflow or ‘pipeline’. This is why I described most of today’s iPaaS offerings as ‘monolithic’. Microsoft’s iPaaS approach represents a democratised, open, value-generating approach with minimal proprietary lock-in and maximum opportunity and choice.
One point I didn’t really articulate fully at the conference is we need still to think very carefully through architecture when exploiting App Servive. This is where hexagonal architecture comes to bear. With the exception of the Application Gateway, nothing else in the App Service model explicitly calls out the separation of ‘ports and adapters’ from business logic. For example, it would be entirely possible for people to create connectors with embedded business logic. This would generally be a very questionable design. The application of Hexagonal architectural thinking to our designs will keep us true!