* [Topics](/en/topics "Topics") * [Integration](/en/topics/integration "Integration") * What is application integration? What is application integration? ================================ Published June 11, 2024•*6*-minute read Copy URL Jump to section --------------- OverviewConcepts and typesUse casesBenefitsChallenges What to look forRed Hat can help Overview -------- Application integration connects different systems and applications by allowing them to work together through data and services. A simple example is enabling 2 isolated business software applications to talk to each other. This type of integration is usually done to improve operational efficiency and deliver better user experiences. Application integration can also improve scalability and reduce costs. [Learn about Red Hat Application Foundations](/en/resources/application-foundations-datasheet) Concepts and types of application integration --------------------------------------------- Application integration isn’t one-size-fits-all. It can take several forms and incorporate a variety of concepts. The 1 thing these ideas all have in common is they facilitate processes between 2 or more applications. Each organization might have different needs and adopt different types of application integration. ### Application integration concepts **Application programming interface (API)** An [API](/en/topics/api) is a set of definitions and protocols for building and integrating application software. APIs enable communication between products and services and simplify application development and integration. An API-led approach to application integration allows developers to build connections without the need for special skills, reducing time and helping increase business efficiency and flexibility. **Events** Important actions or incidents within an application, such as accessing, creating, or changing data, are events. Event-driven architecture ([EDA](https://developers.redhat.com/topics/event-driven)) is a way of designing applications and services to respond to events in real time. **Data mapping** Data mapping maps existing information to a structured format to make it easier for applications to use. This process specifies standard formats for data collected, so different applications can more easily analyze the same data. ### Types of application integration **Point-to-point integration** This is the simplest type of integration. A developer builds a connection between 2 applications so they can share information. The downside to point-to-point integration is that as applications and systems change, developers have to manually create a new connection for each new application or use case. This can lead to inefficiencies and make it harder to scale. **Hub and spoke integration** This type of application integration creates a central messaging exchange to manage connections among different applications. Compare it to making a connection at a hub airport to get from 1 city to another, instead of taking a direct flight. Each connection to the hub eliminates the need for point-to-point integration. One approach to hub-and-spoke integration is **enterprise application integration (EAI)**, where an integration application serves as the hub. Another approach employs an **enterprise service bus (ESB)**, which routes messages between services. These are related concepts and sometimes an ESB is considered a specific method for implementing EAI. **Integration Platform-as-a-Service (iPaaS)** iPaaS is a cloud-based service that handles various application integration functions. Through automation, iPaaS makes it simple to connect applications and data deployed in any environment. ### What about data integration? Application integration and data integration are often discussed as substitutes for one another, but the concepts and uses for each are different. Data integration, sometimes called batch-based data processing, creates a central place to access data from different sources. Generally, data integration takes place after application processes are finished. Organizations can use data integration to analyze performance and ensure consistency and quality. Think about a large organization with multiple divisions, each with their own data. Data integration can help these divisions share data, analyze it, and collaborate. Recommended for you The Need for a Unified Linux Strategy ------------------------------------- [Watch the webinar](https://www.redhat.com/en/events/webinar/need-unified-linux-strategy?percmp=RHCTG0250000455235) Application integration examples and use cases ---------------------------------------------- A big reason organizations adopt application integration strategies is to modernize legacy systems. This often goes hand in hand with modern practices such as agile integration. Here are a few examples of how application integration can make a positive difference in how organizations run. ### Integrating applications across systems and partners [Enterprise resource planning (ERP) systems](/en/topics/linux/what-is-erp), like [SAP](/en/blog/integrating-sap-other-applications-using-red-hat-openshift), are important hubs of all sorts of business activities throughout an organization. An ERP system can do much more when it can bring in information from other applications and services. That can mean anything from helping payroll run more smoothly or improving efficiencies in the supply chain. Customer relationship management (CRM) systems, like Salesforce, can also benefit from application integration by helping support teams deliver more personalized customer support or helping sales teams work more efficiently. ### Healthcare Integrating applications can make it easier for healthcare providers and insurance companies to share patient data. Integration with electronic health record (EHR) systems is 1 example. EHR integration gives medical providers access to more patient information, which can improve the quality of care. [Read a healthcare customer story](/en/success-stories/WHBE) ### Manufacturing, retail, and e-commerce In manufacturing and retail sectors, connected applications can monitor production lines and product lifecycles, and make sure the right products get produced and delivered to the right customers. In manufacturing and distribution, connected devices and integrated applications can work together to identify production problems, maintain quality, facilitate logistics, and control costs. ### Banking If you’ve ever paid a bill using your bank’s mobile app, you’ve probably benefited from application integration. Thanks to integrated applications, customers can access and manage their money, and interact with related products and services such as loans and mortgages. Application integration helps financial institutions provide better internal and customer-facing services while reducing IT costs and improving developer experiences.  [Read a banking case study](/en/resources/anz-case-study) Benefits of application integration ----------------------------------- Application integration can benefit organizations as they develop software. * **Connected environments:** Application integration gives developers flexibility and choice, including options to connect to a variety of endpoints. It can let users access data they otherwise couldn’t. Working with [edge computing](/en/topics/edge-computing/what-is-edge-computing), application integration can help organizations distribute resources across a large number of locations, providing faster, more reliable services. * **Quick adoption of new technology:** API-led integration and EDA enable developers to quickly incorporate new technologies. These methods can support moving with agility and making timely business transitions. * **Productivity:** Integrated platforms add flexibility and efficiency. For example, accessing data through an API can be far easier than going directly through a hosting platform. Integration helps connect applications deployed across different environments, whether they’re on premise, in the [cloud](/en/topics/cloud-computing), or at the [edge on Internet of Things (IoT) devices](/en/topics/edge-computing/iot-edge-computing-need-to-work-together). * **Reduced costs and simplified scaling:** When an organization needs to adjust capacity, an application integration strategy simplifies making changes. APIs and application connectors mean businesses don’t have to start from scratch when adding and scaling up new integrations. All of this can save time and lower costs while allowing businesses to pursue new revenue sources. * **Improved user experiences:** Customers can do more when the applications they use are connected to one another. Bringing systems together lets organizations deliver a unified digital experience—so users can access multiple services in a single destination. Challenges of application integration ------------------------------------- Despite its benefits, application integration introduces change and complexity, which can pose challenges. * **Complexity:** Integrating applications and business processes is both an organizational and technical challenge, requiring coordination of different teams and systems. An integration project can grow even more complex if you have manual processes that need to be automated first. * **Handling custom applications:** Connecting isolated applications or custom-built integrations may involve time-consuming coding work. * **Security concerns:** Maintaining information confidentiality and integrity is a critical requirement for most organizations. Teams need to ensure their integrated applications comply with their organization’s information security and data governance standards. What to look for in an application integration solution ------------------------------------------------------- When evaluating application integration solutions, consider the following factors. **Ease of use and skill-level accessibility:** Your application integration project is more likely to succeed when you choose a solution that’s easy for people of various skill levels to work with. Ease of use makes workflows more efficient and encourages adoption. **Application and environment flexibility:** Applications can run in many environments, and new ones come online all the time. An integration solution needs to accommodate this flexibility. In many cases, a managed, cloud-based solution will be the first to support new software and ensure maximum compatibility across platforms. **Security:** An integration solution should provide built-in security features such as encryption, authentication, and authorization. These safeguards help protect sensitive data and prevent unauthorized access. In addition to these considerations, organizations may want to use an [integrated development environment (IDE)](/en/topics/platform-engineering/what-is-ide), software that combines common developer tools into a single graphical user interface (GUI). An IDE allows developers to start programming new applications quickly because they don't need to manually configure and integrate multiple utilities as part of the set-up process [Learn how to integrate applications](/en/resources/mulesoft-integrates-solutions-brief) Red Hat can help ---------------- [Red Hat® OpenShift®](/en/technologies/cloud-computing/openshift) provides integration across the technology stack, including hybrid cloud environments. As an [application platform](/en/hybrid-cloud-solutions/application-development), Red Hat Openshift lets you build applications the way you want and need by supporting the application lifecycle, including application integration. It’s equipped with tools and frameworks for seamless integrations across development and deployment environments. In combination with Red Hat OpenShift, [Red Hat Application Foundations](/en/products/application-foundations) offers the tools to connect modern development practices with operational necessities so you can design and deploy modern cloud-native applications at speed and at scale. Application Foundations addresses integration challenges with a unified set of commonly used, Red Hat-integrated, and supported open source frameworks and technologies. This simplifies the overall development and management environment. Application Foundations also reduces sprawl and complexity by providing a single-vendor solution your development team can learn and quickly adopt. [Red Hat Developer Hub](/en/technologies/cloud-computing/developer-hub) is a developer portal that promotes efficiency and collaboration by visually consolidating elements of the development process. It streamlines onboarding speed, developer productivity, and collaboration through a unified and open platform while reducing cognitive load and frustration for the development team. Recommended for you E-book Cloud-native meets hybrid cloud: A strategy guide ------------------------------------------------- Discover ways enterprise architects and IT leaders can map and implement modern IT strategy. [Read the e-book](https://www.redhat.com/en/resources/cloud-native-meets-hybrid-cloud-strategy-guide-ebook?percmp=RHCTG0250000455234) Recommended for you Red Hat JBoss Application Administration I ------------------------------------------ best practices for installing and configuring Red Hat® JBoss® Enterprise Application Platform (JBoss EAP) 7 [View course](https://www.redhat.com/en/services/training/ad248-red-hat-jboss-application-administration-i?percmp=RHCTG0250000455236) Keep reading ------------ ### What is a service mesh? Read this article to find out more about what a service mesh is, how it works, and the benefits and challenges of implementing a service mesh. [Read the article](/en/topics/microservices/what-is-a-service-mesh "article | what is a service mesh?") ### What is middleware? Middleware is software that provides common services and capabilities to applications outside of what’s offered by the operating system. [Read the article](/en/topics/middleware/what-is-middleware "article | what is middleware") ### Why choose Red Hat for middleware? Middleware is software that provides services to applications outside of what’s offered by the operating system. [Read the article](/en/topics/middleware/why-choose-red-hat-middleware "article | why choose red hat for middleware?") Integration resources --------------------- ### Related content * Blog post [RPM and DNF features and enhancements in Red Hat Enterprise Linux 10.1](/en/blog/rpm-and-dnf-features-and-enhancements-red-hat-enterprise-linux-101) * Overview [Airlines partner with Red Hat to accelerate the AI revolution](/en/resources/accelerate-innovation-aviation-sector-overview) * Case study [Matmut modernized application development with Red Hat OpenShift](/en/resources/matmut-case-study) * Blog post [From maintenance to enablement: Making your platform a force-multiplier](/en/blog/maintenance-enablement-making-your-platform-force-multiplier) ### Related articles * [What is CI/CD?](/en/topics/devops/what-is-ci-cd) * [What is application lifecycle management (ALM)?](/en/topics/devops/what-is-application-lifecycle-management-alm) * [What is Istio?](/en/topics/microservices/what-is-istio) * [What is serverless?](/en/topics/cloud-native-apps/what-is-serverless) * [What is a CI/CD pipeline?](/en/topics/devops/what-cicd-pipeline) * [What is a service mesh?](/en/topics/microservices/what-is-a-service-mesh) * [Stateful vs stateless applications](/en/topics/cloud-native-apps/stateful-vs-stateless) * [What is application migration?](/en/topics/cloud-native-apps/application-migration) * [Shift left vs. shift right](/en/topics/devops/shift-left-vs-shift-right) * [Red Hat OpenShift for developers](/en/technologies/cloud-computing/openshift/developers) * [Red Hat OpenShift for platform engineers](/en/technologies/cloud-computing/openshift/platform-engineer) * [Why choose Red Hat for a DevOps Platform?](/en/topics/devops/why-choose-red-hat-for-devops) * [What is DevSecOps?](/en/topics/devops/what-is-devsecops) * [What is middleware?](/en/topics/middleware/what-is-middleware) * [What is an application development platform?](/en/topics/cloud-native-apps/what-app-dev-platform) * [What is Apache Kafka?](/en/topics/integration/what-is-apache-kafka) * [Security in the software development lifecycle](/en/topics/security/software-development-lifecycle-security) * [Why choose Red Hat for middleware?](/en/topics/middleware/why-choose-red-hat-middleware) * [What are cloud applications?](/en/topics/cloud-native-apps/what-are-cloud-applications) * [What is agile methodology?](/en/topics/devops/what-is-agile-methodology) * [What is an API?](/en/topics/api/what-are-application-programming-interfaces) * [Red Hat OpenShift application services](/en/technologies/cloud-computing/openshift/application-services) * [What is an independent software vendor (ISV)?](/en/topics/digital-transformation/isv-partners) * [What is a Kafka service?](/en/topics/integration/what-is-a-kafka-service) * [What is streaming data?](/en/topics/integration/what-is-streaming-data) * [Do banking APIs benefit from cloud technology?](/en/topics/api/banking-api) * [What is a service registry?](/en/topics/integration/what-is-a-service-registry) * [What is an event mesh?](/en/topics/integration/what-is-an-event-mesh) * [How microservices support IT integration in healthcare](/en/topics/microservices/microservices-in-healthcare) * [How to deploy Red Hat OpenShift](/en/technologies/cloud-computing/openshift/deploy-red-hat-openshift) * [Kubernetes-native Java development with Quarkus](/en/technologies/cloud-computing/openshift/quarkus) * [What is change data capture?](/en/topics/integration/what-is-change-data-capture) * [Why Red Hat for APIs?](/en/topics/api/why-choose-red-hat-apis) * [What is deployment automation?](/en/topics/automation/what-is-deployment-automation) * [What is service-oriented architecture?](/en/topics/cloud-native-apps/what-is-service-oriented-architecture) * [What is the Kubernetes API?](/en/topics/containers/what-is-the-kubernetes-api) * [What is an SDK?](/en/topics/cloud-native-apps/what-is-SDK) * [What is a REST API?](/en/topics/api/what-is-a-rest-api) * [What is a Java runtime environment (JRE)?](/en/topics/cloud-native-apps/what-is-a-Java-runtime-environment) * [Why choose the Red Hat build of Quarkus?](/en/topics/cloud-native-apps/why-choose-red-hat-quarkus) * [What is an application architecture?](/en/topics/cloud-native-apps/what-is-an-application-architecture) * [What is Quarkus?](/en/topics/cloud-native-apps/what-is-quarkus) * [What are Java frameworks?](/en/topics/cloud-native-apps/what-is-a-Java-framework) * [What is event-driven architecture?](/en/topics/integration/what-is-event-driven-architecture) * [What is API monetization?](/en/topics/api/what-is-api-monetization) * [REST vs. SOAP](/en/topics/integration/whats-the-difference-between-soap-rest) * [Why choose Red Hat for integration?](/en/topics/integration/why-choose-red-hat-integration) * [What is API management?](/en/topics/api/what-is-api-management) * [What is GraphQL?](/en/topics/api/what-is-graphql) * [What is blue green deployment?](/en/topics/devops/what-is-blue-green-deployment) * [What does an API gateway do?](/en/topics/api/what-does-an-api-gateway-do) * [What is API security?](/en/topics/security/api-security) * [What is an IDE?](/en/topics/platform-engineering/what-is-ide) * [What is API design?](/en/topics/api/what-is-api-design) * [What is integration?](/en/topics/integration/what-is-integration) [More about this topic](/en/topics/integration "More about this topic")