* [Topics](/en/topics "Topics") * [Integration](/en/topics/integration "Integration") * Why choose Red Hat for agile integration? Why choose Red Hat for agile integration? ========================================= Published January 29, 2019•*3*-minute read Copy URL Jump to section --------------- Innovation isn't enoughTo ESB, or not to ESBWhat is agile integration?Success story Because innovation isn't enough ------------------------------- Don't get us wrong, continually delivering innovative products and services is the key to staying competitive in digital markets. But what good is a new application if it isn't well connected to the rest of your legacy technology? What's more, how long before it represents any real value for your business if integrating this new app with your existing architecture takes months or years? The days of waterfall development cycles are over thanks to [agile methods](/en/topics/devops/what-is-agile-methodology), [DevOps](/en/topics/devops), [CI/CD automations](/en/topics/devops/what-is-ci-cd), and the rest of your favorite IT buzzwords, but this increase in [developer productivity](/en/products/developer-productivity) isn’t the end of the story. [Innovation needs integration](/en/topics/integration), and it needs it at a speed that matches your current development practices. Red Hat believes that a distributed and iterative integration architecture, rather than a centralized and siloed one, can bring agility to your infrastructure, not just your app dev. What exactly does that involve? An architectural framework that aligns containerized [microservices](/en/topics/microservices), [hybrid cloud](/en/topics/cloud-computing/what-is-hybrid-cloud), and [application programming interfaces](/en/topics/api) (APIs) with the agile and DevOps practices that developers know well. To ESB, or not to ESB, that is the question ------------------------------------------- Although it represented a step forward from the days of a few point-to-point or hub-and-spoke connections, the enterprise service bus (ESB) was intended for rigid, siloed infrastructures. This traditional approach to integration, with centralized teams controlling monolithic technologies, can impede the development and long-term usefulness of newer, distributed applications. ESBs have benefits like prioritizing security and data integrity, but they also rely on a single team to define integrations for the entire enterprise. Moreover, they represent a single point of failure for the integration architecture. Instead, today's loosely coupled, [cloud-native application](/en/topics/cloud-native-apps) architectures developed through agile and DevOps methods need an equally agile and scalable approach to integration. You need these new applications to connect with each other; you also need them to be able to access your legacy applications and data. Red Hat supports both of these business needs by providing integration platforms and management software that let you rapidly connect legacy technologies and microservices across hybrid cloud environments. We call this approach "agile integration." Red Hat resources ----------------- [Keep reading](/en/resources "Keep reading") What is agile integration? -------------------------- Red Hat's view of agile integration combines integration technologies, agile delivery techniques, and cloud-native platforms to improve the speed and [security](/en/topics/security) of software delivery. Specifically, agile integration involves deploying integration technologies like APIs into Linux containers and extending integration roles to cross-functional teams. In this framework, microservices can be rapidly developed and rapidly integrated. With integrations built with the Red Hat Build of [Apache Camel](https://camel.apache.org/) (included with a [Red Hat® Application Foundations](/en/products/application-foundations) subscription) and APIs managed through [Red Hat 3scale API Management](/en/technologies/jboss-middleware/3scale), microservices can essentially get "dropped into" your existing architecture seamlessly, so they start providing value to internal and external users quickly. To share data within your infrastructure, [Red Hat AMQ](/en/technologies/jboss-middleware/amq) facilitates messaging with high throughput and low latency. Updating or removing services no longer run the risk of breaking the entire app, since a loosely coupled architecture connected through agile integration processes has increased fault tolerance. In short, agile integration changes enterprise integration from a problem that must be overcome, to a platform for elastic scalability across decentralized services. This video can't play due to privacy settings To change your settings, select the "Cookie Preferences" link in the footer and opt in to "Advertising Cookies or try disabling adblockers." [Read the blueprint for agile integration](https://go.redhat.com/agile-integration-devops-containers-20180801) UPS streamlines package tracking and delivery with Red Hat ---------------------------------------------------------- **Problem:**UPS, a global leader in logistics, wanted to optimize package operations and delivery using a new application platform, called the Center Inside Planning and Execution System (CIPE). In addition, the company wanted to adopt a more agile, collaborative DevOps approach—and technology that would support both CIPE’s new capabilities and this new work method. "We needed to move from our old technologies to the cloud, to make better decisions using real-time, big data analytics," said Rich West, senior application development manager at UPS. **Solution:** After deciding that container technology would best meet its needs for agile, cloud-based workflows, UPS evaluated many solutions. It chose to create its new application environment with enterprise open source technology from Red Hat. In addition, UPS used Red Hat Consulting to help plan and deploy CIPE. "They also quickly trained our developers on container platform technology," said Stacie Morgan, senior application development manager at UPS. "We were able to launch the first iteration of the site application in 3 months. We’ve never brought up a platform that quickly." > Insights and innovations are happening at a faster rate than ever before. It’s an exciting time at UPS, and Red Hat technologies have played a major role in our journey. > > Nick Costides > > President Information Technology, UPS The official Red Hat blog ------------------------- Get the latest information about our ecosystem of customers, partners, and communities. [Keep reading](/en/blog "The official Red Hat blog") All Red Hat product trials -------------------------- Our no-cost product trials help you gain hands-on experience, prepare for a certification, or assess if a product is right for your organization. [Keep reading](/en/products/trials "All Red Hat product trials") 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 application integration? Application integration connects different systems and applications by enabling them to work together through exchanging data and using services. [Read the article](/en/topics/cloud-native-apps/application-integration "article | What is application integration") ### 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") Integration resources --------------------- ### Featured product * #### [Red Hat Application Foundations](/en/products/application-foundations) A set of components engineered to help build, deploy, and operate applications. Includes Red Hat 3scale API Management, Red Hat Data Grid, Red Hat JBoss Web Server, Red Hat AMQ, Red Hat builds of open source technologies, and a migration toolkit for applications. [See all products](/en/technologies/all-products "See all products") ### Related content * Case study [[node:rh-smart-meta-title]](/en/resources/holcim-digital-center-case-study) * Case study [Advent One modernizes IT with Red Hat](/en/resources/advent-one-case-study) * Case study [HCA Healthcare develops predictive analytics using Red Hat software](/en/resources/hca-healthcare-case-study) * Blog post [Evolving our ServiceNow integration: Sunsetting the Notification Service for more capable alternatives](/en/blog/evolving-our-servicenow-integration-sunsetting-notification-service-more-capable-alternatives) ### Related articles * [What is a service mesh?](/en/topics/microservices/what-is-a-service-mesh) * [What is application integration?](/en/topics/cloud-native-apps/application-integration) * [What is middleware?](/en/topics/middleware/what-is-middleware) * [What is Apache Kafka?](/en/topics/integration/what-is-apache-kafka) * [Why choose Red Hat for middleware?](/en/topics/middleware/why-choose-red-hat-middleware) * [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 an event mesh?](/en/topics/integration/what-is-an-event-mesh) * [How microservices support IT integration in healthcare](/en/topics/microservices/microservices-in-healthcare) * [What is a service registry?](/en/topics/integration/what-is-a-service-registry) * [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 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 a REST API?](/en/topics/api/what-is-a-rest-api) * [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) * [What is GraphQL?](/en/topics/api/what-is-graphql) * [What does an API gateway do?](/en/topics/api/what-does-an-api-gateway-do) * [What is API design?](/en/topics/api/what-is-api-design) * [What is API management?](/en/topics/api/what-is-api-management) * [What is API security?](/en/topics/security/api-security) * [What is integration?](/en/topics/integration/what-is-integration) [More about this topic](/en/topics/integration "More about this topic")