Technical Specification

OpenLegacy Hub Enterprise is a container-based legacy modernization platform designed for flexible deployment on servers or container orchestration platforms such as Kubernetes. This approach enables consistent, scalable, and manageable deployments aligned with modern DevOps and cloud-native practices.

Core Deployment Components

• Postgres Database
  Serves as the primary persistent data store for the Hub's metadata, configuration, and legacy service repositories. Database schema is initialized and maintained through dedicated DB migration scripts jobs, ensuring the database structure is always up to date.

• Keycloak (Identity and Access Management - IAM) Keycloak is an open-source, actively maintained IAM solution widely adopted in enterprise environments.

  • It supports Single Sign-On (SSO), allowing seamless user authentication across multiple applications with a single login.
  • It integrates with LDAP to leverage existing corporate directory services for centralized user management and compliance.
  • Keycloak supports OAuth2, OpenID Connect, and SAML, providing robust security and compatibility standards.
  • Its active community and continuous development ensure regular feature updates and security patches, which is critical for enterprise-grade identity management.

• OpenLegacy Hub Enterprise Application
  The core platform that generates, manages, and deploys modernization-ready APIs exposing legacy assets. It securely connects legacy systems to modern applications and services.

Deployment Flexibility

• The Hub can be integrated with an existing Postgres database and Keycloak installation, allowing customers to use their current infrastructure and identity management frameworks.
• Alternatively, customers can deploy the entire stack using the provided deployment bundle, which includes a preconfigured Postgres database and a Keycloak realm tailored specifically for the Hub's requirements. This option accelerates initial setup in new or test environments.

Versioning & Update Policy

• The installation bundle contains both installation and update scripts.
• Installation steps and upgrade procedures are documented in the bundle's README files.
• Upgrading requires running database migration scripts followed by updating the Hub application version.
• Best practice before running the upgrade procedure is to backup the Postgres database to prevent data loss.
• Supported upgrade paths and long-term support (LTS) or stable release information are provided to ensure smooth transitions between versions.

Architecture Highlights

• Container-based design enables deployment on traditional servers or orchestration platforms such as Kubernetes. The following containers are required.
  • OpenLegacy Hub Enterprise
  • OpenLegacy Hub Enterprise DB Migration
  • Keycloak
  • PostgresDB
• Scalable and consistent deployment aligned with cloud-native and DevOps best practices.
• Secure access management through Keycloak enables centralized and robust authentication and authorization.
• Supports hybrid cloud, multi-cloud, and on-prem environments, ensuring adaptability to diverse enterprise IT landscapes.

Summary

OpenLegacy Hub Enterprise is a modern, containerized legacy modernization platform backed by a robust Postgres backend and secured by enterprise-grade Keycloak IAM. It offers flexible deployment options suitable for integrating into existing enterprise infrastructures or fresh deployments with provided service bundles. Keycloak’s SSO and LDAP integrations enhance security and user experience while the container architecture supports scalable and manageable deployments.