Integration is still relevant. Change is ubiquitous and software architectures must constantly evolve. The adaptation of new technologies, concepts and tools is necessary in order to be flexible with regard to new requirements. Many companies use available cloud technologies for this purpose. This leads to elastic infrastructures and hybrid application ecosystems; on-premise systems and cloud services must be integrated, leading to increased complexity. To open up new sales channels, enterprise data and functions are made accessible to third parties in a scalable and secure manner. How can the resulting requirements for decoupling, performance or availability be met within the framework of a future-proof, scalable integration infrastructure that is also fault tolerant and highly fail-safe? This presentation takes you on a short journey through time and discusses the role and relevance of integration architectures, key patterns and their development (publish/subscribe, event sourcing, CQRS) as well as the way they should be implemented today. Are we still talking about monolithic integration platforms or is there a "New Kid on the Block" that is lightweight and follows an architectural style of Microservices?

1. © OPITZ CONSULTING 2019
¢¢¢ Digitale Service Manufaktur
© OPITZ CONSULTING 2019
Sven Bernhardt, Senior Solution Architect
From EAI to Serverless -
Evolution of Integration
architectures

2. © OPITZ CONSULTING 2019 Evolution of Integration architectures
About me
Sven Bernhardt
¢ Senior Solution Architect @OPITZ CONSULTING Deutschland
GmbH
¢ Oracle ACE Director
@sbernhardt
https://svenbernhardt.wordpress.com/
Seite 2

3. © OPITZ CONSULTING 2019 Seite 3
Agenda
1
3
4
5
6
Meaning of integration
Brave new integration world
Integration styles & patterns
Data perspective
Conclusion
Evolution of Integration architectures
2 „Traditional“ integration approaches

4. © OPITZ CONSULTING 2019 Seite 4
Meaning of integration
1
Evolution of Integration architectures

5. © OPITZ CONSULTING 2019 5
Simple definition of integration: Enabling systems to
talk to each other
System
A
System
B
XX
Evolution of Integration architectures

6. © OPITZ CONSULTING 2019 6
Ensure that data is where it is needed when it is needed
in the form in which it is needed
System
A
System
B
Evolution of Integration architectures

7. © OPITZ CONSULTING 2019 Evolution of Integration architectures Seite 7
Challenges of integration architectures today
¢ Monolithic / aging systems
¢ Disparate data models
¢ Architectural complexity
¢ Heterogeneous ecosystem
¢ Technical debt
¢ Bloated projects / overhead
¢ Visibility / error handling
¢ Production deployment

8. © OPITZ CONSULTING 2019 Seite 8
„Traditional“ integration approaches
2
Evolution of Integration architectures

9. © OPITZ CONSULTING 2019
Horizontal integration
Evolution of Integration architectures Seite 9
A long time ago in a galaxy far, far away… Integration
was mainly seen as a one-dimensional challenge
¢ Horizontal integration scenarios
¢ Classic System2System integration
¢ Need to deal with heavy-weight, proprietary
protocols
¢ Technical interfaces
¢ Batch processing
¢ Asynchronous interaction patterns (file-
based interactions)

10. © OPITZ CONSULTING 2019 Evolution of Integration architectures Seite 10
ESB as basic integration backbone
global internal specific
External Interfaces – Proxy Servics
Integration Logic
Internal Interfaces – Business Interfaces

11. © OPITZ CONSULTING 2019 Evolution of Integration architectures Seite 11
https://technology.amis.nl/2019/01/23/changing-views-on-integration-from-enterprise-service-bus-to-api-gateway-serverless-and-ipaas/

12. © OPITZ CONSULTING 2019 Evolution of Integration architectures Seite 12
ESB solutions are often based on a monolitihic
architecture with limited scalability
Loadbalancer
ESB 1 ESB 2 ESB 3

13. © OPITZ CONSULTING 2019 Evolution of Integration architectures Seite 13
„Technological trap“ - blocks the use of appropriate
technologies to address specific business needs
Oracle SOA Cloud
Service
Fixed Technologies Set
<XML />
{
„dialect“:“JSON“
}
…and other vendors as well!

14. © OPITZ CONSULTING 2019 Evolution of Integration architectures Seite 14
Insufficient support for DevOps principals leads to
limited agility
¢ Hard to implement Continuous Integration / Continuous Delivery
¢ Complex infrastructure
¢ Missing automated testing capabilities
¢ Expert knowledge needed for
¢ Implementation
¢ Deployment
¢ Error analysis

15. © OPITZ CONSULTING 2019 Seite 15
Brave new integration world
3
Evolution of Integration architectures

16. © OPITZ CONSULTING 2019 Evolution of Integration architectures Seite 16
New insights, contexts and use cases
¢ Increased need for scalability
¢ Need for Speed
¢ Tighter Security requirements
¢ Faster change cycle
¢ 24/7 Ops
¢ Scarcity of talent/developers
¢ Data/Domain modelling
¢ Data currency
¢ Increased use of Standard apps SaaS
¢ Advent of Cloud
¢ New architecture patterns
¢ Advances in technologies
¢ TCO of Middleware platforms
¢ Roadmaps of Middleware vendors

17. © OPITZ CONSULTING 2019 Evolution of Integration architectures Seite 17
The world is getting more complex!

18. © OPITZ CONSULTING 2019 Evolution of Integration architectures Seite 18
Integration is a multi-dimensional, enterprise-wide
challenge!

19. © OPITZ CONSULTING 2019 Evolution of Integration architectures Seite 19
Cloud enables new opportunities, but introduce
additional complexity: Hybrid integration scenarios

20. © OPITZ CONSULTING 2019 Evolution of Integration architectures Seite 20
Sharing is caring – Data is a key asset for enterprises
nowadays
¢ Formation of new digital economies
¢ Driven by APIs
¢ APIs & Data as digital products
¢ New requirements with respect to
¢ Data provisioning
¢ Data availability
¢ Data access
¢ Data currency Data
is the new
currency

21. © OPITZ CONSULTING 2019 Evolution of Integration architectures Seite 21
Technological evolution singificantly influences the way
how applications are built
Bare Metal Virtualization Cloud Computing Containers Serverless

22. © OPITZ CONSULTING 2019 Seite 22
Integration styles & patterns
4
Evolution of Integration architectures

23. © OPITZ CONSULTING 2019 Evolution of Integration architectures Seite 23
Independent of any evolutionary evolvement - Patterns
stays the same!
¢ Book „Enterprise integration patterns“ from 2003 is „the bible“ for
integration architectures
¢ Integration scenarios can be described using the proposed components
and patterns
¢ Endpoint
¢ Message
¢ Channel
¢ Router
¢ Filter
¢ Translator

24. © OPITZ CONSULTING 2019 Evolution of Integration architectures Seite 24
Integration patterns are supplemented by further
modern architecture patterns

25. © OPITZ CONSULTING 2019 Evolution of Integration architectures Seite 25
Vertical integration
¢ End User ”integration”
¢ API Gateway as runtime component for
¢ API policy enforcement
¢ Request routing
¢ (Near) Real-time, synchronous interactions
¢ APIs born from business requirements
¢ Who is using the API?
¢ How is the API being used?
¢ Use of lightweight, standard protocols
https://microservices.io/patterns/apigateway.html
API Gateway
Backend for Frontend

26. © OPITZ CONSULTING 2019 Evolution of Integration architectures Seite 26
API design-first approach to collaborativelly create
valuable business APIs

27. © OPITZ CONSULTING 2019 Evolution of Integration architectures Seite 27
Evolution of „vertical integration flow“ implementation

28. © OPITZ CONSULTING 2019
Horizontal integration
Evolution of Integration architectures Seite 28
Horizontal integration
¢ New insights: Relaxed freshness and consistency demands, data
replication
¢ New context: Cloud, hybrid, “dumb pipes, smart endpoints”, Standard
Apps & SaaS evolution
¢ Classic System2System integration
¢ Need to deal with heavy-weight, proprietary protocols
¢ Technical interfaces
¢ Batch processing
¢ Asynchronous interaction patterns

29. © OPITZ CONSULTING 2019 Evolution of Integration architectures Seite 29
The when, what and how for System-2-System
integration on a horizontal level

30. © OPITZ CONSULTING 2019 Evolution of Integration architectures Seite 30
(Cloud) Adapters & iPaaS platforms

31. © OPITZ CONSULTING 2019 Evolution of Integration architectures Seite 31
Event-Driven integratiom
“Life is a Stream of Events”
https://www.slideshare.net/ConfluentInc/life-is-a-stream-of-events

32. © OPITZ CONSULTING 2019 Evolution of Integration architectures Seite 32
Event-Driven integration
¢ Systems act and react to internal & external
events
¢ Streams of events represent information
and behavior
¢ Data should end up in the right places…
eventually
¢ Popular design patterns:
¢ Event Sourcing
¢ CQRS
¢ Materialized view

33. © OPITZ CONSULTING 2019 Evolution of Integration architectures Seite 33
Event-Driven architecture doesn‘t just mean replacing
ESB by an Event-Hub!

34. © OPITZ CONSULTING 2019 Seite 34
Data perspective
5
Evolution of Integration architectures

35. © OPITZ CONSULTING 2019 Evolution of Integration architectures Seite 35
When data is needed? Just-in-Time (JIT) vs. Ahead-of-
Time (AOT) data

36. © OPITZ CONSULTING 2019 Evolution of Integration architectures Seite 36
In what form data is needed? Same set of data in
different forms and use cases
¢ Command Query Responsibility
Segregation
¢ Separate Read (Query) from Write
(Command) operations
¢ Freedom to choose data store technologies
depending on the use case
¢ Perfectly fit to be combined with
Backend-for-Frontends (BFF)
Command
Data
Store
Relational DB
Read
Data
Store
Read
Data
Store

37. © OPITZ CONSULTING 2019 Evolution of Integration architectures Seite 37
Where is the data needed? Shared data sets between
different companies to simplify B2B scenarios
¢ Formation of new Data Sharing Ecosystems (Collective Data Sets)
¢ Centralized, shared data store
¢ Each participant has it‘s might have it‘s own local representation of data (depending on the
implementation)
¢ Implementation approaches
¢ Classic integration approach (ESB)
¢ Event-based approach
¢ (Consortium/Private) Blockchain
Data
Store
Company
A
Company
B
Company
C
Company
D

38. © OPITZ CONSULTING 2019 Seite 38
Conclusion
6
Evolution of Integration architectures

39. © OPITZ CONSULTING 2019 Evolution of Integration architectures Seite 39
Key takeaways
¢ Integration is more relevant than ever
¢ Integration scenarios are increasingly complex because of:
¢ Data volumes
¢ Hybrid ecosystems
¢ Platform criticality
¢ Enables modern business models
¢ Leverages technology and architecture
¢ 3 main integration styles (Vertical, Horizontal, Event-Driven)
¢ Technology & concepts are evolving but integration patterns stay the same
¢ Asynchronous should be the preferred communication style

40. © OPITZ CONSULTING 2019 Seite 40
Q & A
Evolution of Integration architectures

41. © OPITZ CONSULTING 2019 Evolution of Integration architectures Seite 41
Resources
¢ Blog: ESB & API-led architectures = Enemies or friends, Vinay Kumar
¢ Blog: Changing views on integration – from ESB to API GW, Serverless &
iPaaS, Lucas Jellema
¢ Blog: Collective Data Set and Equal Data Position between B2B Partners in
sharing Ecosystems, Lucas Jellema
¢ Presentation: Evolution of API-driven architectures, Sven Bernhardt
¢ Website: Enterprise Integration Patterns
¢ Website: Microservices Patterns
¢ Website: International Data Spaces (example for Collective Data Sets)

42. © OPITZ CONSULTING 2019
¢¢¢ Digitale Service Manufaktur
@OC_WIRE
OPITZCONSULTING
opitzconsulting
opitz-consulting-bcb8-1009116
WWW.OPITZ-CONSULTING.COM
Seite 42
Thanks for your attention!
Sven Bernhardt
Senior Solution Architect | Oracle ACE Director
OPITZ CONSULTING Deutschland GmbH
Kirchstrasse 6, 51647 Gummersbach, Germany
Phone: +49 172 2193529
Mail: sven.bernhardt@opitz-consulting.com
@sbernhardt
https://svenbernhardt.wordpress.com
Evolution of Integration architectures