Using Hybrid Integration To Open Up The Cloud

    What is Hybrid Integration?

    hybrid integration cloud

    OpenLegacy is a Hybrid Integration Platform (HIP) connecting cloud-based and on-premise applications. HIP solutions leave the data and applications where they currently exist, both on-prem and in the cloud, and leverage the integration between them based on user scenarios.

    OpenLegacy’s B2B solution makes it easier for the integration specialist to parse metadata from the on-premise systems and use templates to generate standard Java code. The integration specialists only need to know Java, a common language for cloud development.

    How do you know if you need HIP?

    OpenLegacy’s HIP is ideal for organizations with business-critical data in both on-premise applications and in the cloud, or which have all their data in the cloud and need an on-premise-focused solution. HIP solutions aren’t new, but products vary in how much they help or inhibit a true HIP process. These include:

    hybrid integration for iPaaS (Integration PaaS) and iSaaS (Integration SaaS)

    iPaaS (Integration PaaS) and iSaaS (Integration SaaS) focus on cloud applications exclusively and therefore need a separate HIP that supports on-premise systems.

    hybrid integration for cloud data integration

    Cloud Data Migration use data integration to move data into the cloud but ignore a critical asset -- the application business logic.

    hybrid integration and SOA/ESB

    SOA/ESB based API Management Solutions manage APIs but their integration tooling adds middleware, so integration specialists must have domain expertise in both the on-premise system and middleware.

    Benefits of Hybrid Integration

      Benefits OpenLegacy support
    Flexible deployment model Users decide where to place integration: public or private cloud Generation of microservices for easy deployment
    Support for integration scenarios Support for translating green screens, reading metadata, converting DB interfaces, etc. Pre-built platform connectors support various different scenarios including screens, metadata, DBs, etc.
    Agile approach Flexibility in developing integrations based on urgency Automated API creation makes development fast and doesn’t require specialized platform knowledge

    Hybrid Integration Resources

    OpenLegacy has many case studies on our website that focus on companies' HIP scenarios. Here are some examples:

    hybrid integration for finance
     

    Financial Services

    Finance,AS/400,Mainframe,
    Microservices,APIs for Credit Application,Web Service

    Global bank uses OpenLegacy to launch a Global API, the foundation for customer experience innovation

    hybrid integration for manufacturing
     

    Manufacturing

    SAP, Digital Transformation

    OpenLegacy exposes SAP backend applications for use in new digital channels for Indian conglomerate

    hybrid integration for Insurance
     

    Insurance

    AS400, Digital Transformation, DevOps

    OpenLegacy empowers Ayalon’s digital transformation and DevOps methodologies. Shortens policy creation from months to minutes.

    hybrid integration for automotive
     

    Automotive Industry

    Automotive,AS/400,IBM i,CRM,ERP,Mobile App

    Spare parts distributor speeds towards IBM i-based tablet application

    Using Microservices to Implement a Hybrid Integration Platform Solution

    Challenge Solution
    On-premise platforms are expensive to change Create a microservice using a popular language, Java, that calls the current legacy interface.
    Expose APIs incrementally to limit the need for change and data breaches Microservices expose only the data needed for specific scenarios.
    Allow integration teams to work in parallel Microservices are small, self-contained services that teams can work on in parallel
    Develop APIs with optimized connections to the on-premise system. A microservice with a direct connection is optimized.
    Support DevOps processes by making the APIs self-contained. Microservices package APIs for easy deployment inside containers.

    By generating microservices, OpenLegacy fits the requirements of a HIP very well, but OpenLegacy’s platform also includes deployment of the microservices inside Docker containers, built in JUnit testing and is a complete HIP solution that focuses on the integration of the legacy into a cloud environment.

    Learn More