Federal government spends roughly 80 percent of its $80 billion annual IT budget on maintaining legacy systems. Well, it’s about time that these systems are modernized. However, when migrating legacy environments to microservices and the cloud, it is not just the systems and applications that need to go through modernization. Shake up your integration strategy to enable digital transformation, says VP & Gartner Fellow Massimo Pezzini. This includes the approach and techniques used for enterprise integration. What may have worked in the past will no longer be applicable going forward. “Integration is dead. Long live integration!” screams the title of this session on the Integration track at the Red Hat Summit — hinting at the continuing need for enterprise integration with modernized approaches. This comes across loud and clear when I take a look at the sessions on this track. Join me as I explain why Integration gets modernized at the Red Hat Summit.
Take, for example, the Royal Bank of Scotland. Organizations like these are sitting on treasure troves of data. Business intelligence teams with the right tools can mine this data and unearth brilliant insights that could lead to the creation of new products and services and improve customer service and retention rates. With the possibility of such rich opportunities mere queries away, it’s no wonder that IT departments are increasingly interested in data usage for analytics. In financial services, it’s key to obtain more sophisticated information, captured from different systems (transactional, risk, ledger, static), having structured or less structured information to be delivered on multiple channels. Traditional integration approaches would involve the cost and complexity of data warehouses or extract, load, transform (ELT) techniques. Royal Bank of Scotland (RBS) used Red Hat JBoss Data Virtualization to implement a data access layer and support real-time data decisions within their organization. This is a technique that offers accurate, reliable data in real-time with no unnecessary data replication reducing costs of out-of-sync reports. Think differently with real-time data.
The art of going mobile across the enterprise is fundamentally enabled by the science of integration with the backend systems. This session showcases a better way to integrate Salesforce.com with your enterprise’s widespread data, apps, and mobile devices. You will see how to access the instance of salesforce.com with Red Hat Mobile Application Platform highlighting entire Salesforce integration capabilities with a live demo.
Gone are the days when you implemented an application first and added an API later. APIs are a mandatory component of application delivery these days—increasingly the first step in application design and development. As more projects are developed with an API-first mindset, IT teams are also looking for an API-oriented focus on the operational side of the house, too. Enter API Management, which allows developers and operators to address security, performance, life cycle, and governance concerns in a consistent, non-invasive way for all APIs deployed in the enterprise. Introducing Red Hat API management session provides an overview of API Management and introduce Red Hat’s new API management platform.
Integration is dead. Long live integration. Even though enterprise integration can be a complex, multi-faceted, and a messy discipline, there are best practices that can make things easier. Enterprise Integration Patterns (EIPs) are a set of commonly used patterns to integrate applications and provide a standard vocabulary to design and collaborate on integration projects. Apache Camel is an open source integration framework that provides implementation of EIPs, connectivity to multiple applications and the necessary wiring to connect all pieces together. Integration Modernized ! Architects from real enterprises using such modern integration techniques will share their experience-based insight on this panel. Panelists include Essa Mohammad, enterprise architect from GE Transportation, and Asif Sajjad, lead integration architect at DaVita Rx.
Modernized environments must scale to accommodate the dynamic requirements of newer workloads. Take messaging for example. With modern cloud technology, it’s practical to add and remove computing resources to accommodate changing workloads. But what if these scalable resources use messaging technology to deliver their services? How do you deploy message queuing that can handle the changing scale? Elastic scale for messaging using Red Hat JBoss A-MQ explains how.
With the plethora of legacy integration solutions in place across a diverse array of platforms, migration is a continuous journey. Healthy injections of automation with context significantly eases this transition making it as seamless an experience as possible. Wipro, a global premier partner of Red Hat, has developed a comprehensive migration framework that combines a mature methodology, automation tools, and proven expertise to help customers seamlessly move to Red Hat JBoss Fuse from other integration offerings from IBM, webMethods, TIBCO, and Oracle (JCAPS). This approach helps simplify and accelerate the migration process while reducing risk and adding predictability. The session, Automated migration from proprietary integration platforms to Red Hat JBoss Fuse describes how this migration framework addresses migration challenges along with a use case demo for a specific scenario.
Well, it’s time we reached out and got a view from the trenches. Join Jesmond Abela, CTO of Intelligent Payments, and Keith Lynch, leader of Red Hat’s Application Development business in the UK, to hear their direct experiences in the area of microservices-based integration.
Microservices is still a distributed-systems problem and integration is a core component of any distributed system. This session describes Fuse integration services for OpenShift – a Docker-native way of packaging microservices and to use powerful integration technology built on Apache Camel to connect the pieces. The session discusses the challenges of moving to microservices, how to integrate disparate pieces, and how to build, test, and deploy using an out-of-the-box (but pluggable) CI/CD toolchain built on OpenShift by Red Hat and Kubernetes with the open source projects already in place.
So, what does the roadmap for various Integration products look like?
- Red Hat JBoss Fuse and the art of enterprise integration presents an overview of the JBoss Fuse platform and discuss considerations from connectivity to deployment architecture. Due attention will be given to the latest features in Fuse 6.3 and Fuse integration services for OpenShift by Red Hat, and we’ll take a look ahead to JBoss Fuse 7. The session will include live demos, lessons learned, and best practices from Frost Bank’s successful migration to JBoss Fuse, resulting in a middleware architecture that maintained existing client interfaces and provided maximum flexibility to handle future requirements.
- Integration roadmap. This session provides insight into Red Hat’s integration roadmap for iPaaS, API management, RedHat JBoss Fuse, data virtualization, and more.
There you have it. Integration components within the enterprise IT landscape are also bonafide passengers in the transformation journey along with the very systems and applications they integrate. Just like they sunset certain legacy applications, enterprises may very well have to cease employing some integration techniques.
Which integration approaches stay? What are the new ones to be introduced? Please weigh in with your thoughts. And, if you attend any of these sessions on the middleware track, please look me up and I would be happy to engage in a discussion with you!