InfoQ Homepage Integration Content on InfoQ
-
/articles/ballerina-cloud-native-programming/en/smallimage/-C2PlY3M-1631543404121.jpg)
Ballerina Swan Lake: 10 Compelling Language Characteristics for Cloud Native Programming
The Ballerina language has come a long way with significant improvements since the 1.0 release in 2019. The latest Swan Lake release further simplifies building and deploying cloud native apps.
-
/articles/api-first-integration/en/smallimage/a-seven-step-guide-to-API-first-integration-small-logo-1604605388784.jpg)
A Seven-Step Guide to API-First Integration
For a successful digital transformation project, following an API-first approach is more effective and future proof than using an integration-first approach.
-
/articles/multi-runtime-microservice-architecture/en/smallimage/Multi-Runtime-Microservices-Architecture-logo-1582629543965.jpg)
Multi-Runtime Microservices Architecture
Best practices have emerged around “microservice” architecture and “12-factor app” design. As cloud, containers, and container orchestrators (.g. Kubernetes) have become popular, new solutions to address common integration principles have emerged. This article discusses the approach of using "mecha" components to provide enterprise integration pattern functionality for microservices.
-
/articles/book-review-digital-experience-platforms/en/smallimage/QA-on-the-Book-Building-Digital-Experience-Platforms-l-1576141025766.jpg)
Q&A on the Book Building Digital Experience Platforms
The book Building Digital Experience Platforms by Shailesh Kumar and Sourabhh Sethii describes methods, techniques, and practices for using digital experience platforms (DXP) and provides a digital transformation case study from a banking application.
-
/articles/application-integration-service-mesh/en/smallimage/role-application-integration-cloud-native-microservices-landscape-logo-small-1557478517420.jpg)
Application Integration for Microservices Architectures: A Service Mesh Is Not an ESB
A service mesh is only meant to be used as infrastructure for communication between services, and developers should not be building any business logic inside the service mesh. Other frameworks and libraries can be used to implement cloud native enterprise application integration patterns.
-
/articles/TOGAF-enterprise-architecture/en/smallimage/togaf-logo-small-1536250135544.jpg)
How the TOGAF Standard Serves Enterprise Architecture
Any architect working with large enterprise systems has probably looked for guidance on how to manage the complexity and communicate with various stakeholders. This introductory overview of the TOGAF standard explains the structure of the framework, as well as discusses the benefits of using enterprise architecture to manage complex systems.
-
/articles/tool-integration-hard-truth/en/smallimage/GettyImages-480500648.jpg)
How Difficult Can It Be to Integrate Software Development Tools? The Hard Truth
Integrating tools used in software development and delivery is very hard. Getting endpoints to inter-operate is not a purely technical challenge, it’s more of a business problem. While there are a few choices in selecting the technical integration infrastructure (integration via APIs or at the database layer), the real challenges have more to do with friction caused by the dissimilarities.
-
/articles/integration-mistakes/en/smallimage/pamod-logo.jpg)
Two Mistakes You Need to Avoid When Integrating Services
With SOA, businesses moved from monolithic applications to heterogeneous designs by decomposing functionality into services. However, architects must be careful when integrating services. Often enterprises assume adopting patterns like ESB can help. Unfortunately, there are hidden challenges with these patterns. The danger is they go unnoticed during development but surface when a system is live.
-
/articles/reactive-messaging-patterns-with-actor-model-book-review/en/smallimage/ShowCover (1).jpg)
Reactive Messaging Patterns with the Actor Model Book Review and Q&A with Vaughn Vernon
Vaughn Vernon in his new book Reactive Messaging Patterns with the Actor Model shows how this model can simplify enterprise software development. After an introduction to the basics of the actor model and tutorials on Scala and Akka the rest of the book is a patterns catalogue describing most of the patterns in the book Enterprise Integration Patterns from an actor model perspective.
-
/articles/eip-designer/en/smallimage/logo-eip.jpg)
EIP Designer: Bridging the Gap Between EA and Development
This article presents the EIP Designer project, an Eclipse-based tool for introducing integration patterns into an EA design, providing fluidity and continuity while filling the gap existing between EA practices and concrete software development.
-
/articles/twenty-years-of-patterns-impact/en/smallimage/logo.jpg)
Twenty Years of Patterns’ Impact
In this article, authors talk about the impact of pattern languages on the software design community over the past 20 years. They discuss patterns like Enterprise Integration Patterns, open source ESBs and patterns as a design tool.
-
/articles/cloud-eai/en/smallimage/logo.jpg)
Bridging Subsidiaries With the Cloud to Create a Global API
One of the biggest challenges in modern business is how you integrate subsidiaries and present a single global view so that customers and partners find it simpler to integrate with your organisation. In this article we will discuss a fictitious sample based on a real-world scenario and look at some of the challenges and good practices that you should look to implement to be successful.