OpenLegacy is in the Hybrid Integration Platform (HIP) product category which connects 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.
OpenLegacy 's HIP is ideal for organizations with business-critical data in both on-premise applications and in the cloud, or organizations that 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:
These solutions focus on cloud applications exclusively and therefore need a separate HIP that supports on-premise systems.
This solution uses data integration to move data into the cloud but ignores a critical asset -- the application business logic.
These types of solutions manage APIs, but their integration tooling adds middleware, therefore integration specialists must have experience in both the on-premise system and middleware.
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 integration based on urgency | Automated API creation makes development fast and doesn't require specialized platform knowledge |
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.
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 team 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 packages APIs for easy deployment inside containers |