The document discusses two architectural styles: service-oriented architecture (SOA) and microservices. SOA supports service-orientation with components like a service bus and repository. Microservices take a different, more lightweight approach with independently deployable services that communicate via HTTP APIs. Integration can follow patterns like migration, broadcast, or aggregation.

1. Architectural Styles & PatternsArchitectural Styles & Patterns

2. Architectural stylesArchitectural styles
Service oriented architecture (SOA)Service oriented architecture (SOA)
An architectural style that supports service-
orientation. Service-orientation is a
way of thinking in terms of services and
service-based development and the
outcomes of services.
2

3. SOA ComponentsSOA Components
3
SOA
Service
bus
Service
repository
ServiceApplication
frontend
InterfaceImplementationContract
DataBusiness Data
logic

4. Integration Style – MULE ESBIntegration Style – MULE ESB
4
Componentize micro services with API
policies
Pro:
• Scalability
• Reusability
• Promotes services
Independence
Con:
• Longer time-to-value
but even bigger ROI

5. Architectural stylesArchitectural styles
MicroservicesMicroservices
 Evolved from SOA, but takes a different approach
to service design and management

 Lightweight, distributed model, rather than
heavyweight, monolithic model
 -Often minimal or lightweight
management tools
5

6. MicroservicesMicroservices
 Based on the concept of lightweight, self contained
services
 Services represent business capabilities
 Communicating with lightweight mechanisms
-Often an HTTP resource API
 Independently deployable by fully automated
deployment machinery
 Often just a bare minimum of centralized management
of these services
 Lightweight, distributed model, rather than
heavyweight, monolithic model
 Often minimal or lightweight management tools
6

7. AdvantagesAdvantages
 Gives developers the freedom to independently
develop and deploy services in small teams
 Code for different services could be in different
languages and frameworks
 Easy integration and automatic deployment
 Easy to understand and modify for developers, thus
can help a new team member become productive
quickly
 The developers can make use of the latest technologies
 The code is organized around business capabilities
7

8. Integration PatternsIntegration Patterns
 Existing integration solutions are often modeled after either
business processes/functionalities or data flows
– A combination of both is not common and could
be difficult to design and implement
 Most integration solutions’ architecture can be deducted
into just a few common patterns
– Migration
– Broadcast
– Aggregation
– Bi-directional synchronization
– Correlation
8

9. EndEnd

10. EndEnd