DeployHub is a SaaS or on-premise configuration management and deployment solution designed for the next generation of software releases. Unique to DeployHub is its ability to version the unique parts of a software release supporting the release of objects that are independently deployable, such as microservices . DeployHub is unique in the way in incorporates the use of Domains. Domains are used to catalog and share microservices across teams.
DeployHub uses an agentless architecture that is designed to support the modern architecture of containers and Kubernetes as well as legacy systems. DeployHub has plug-ins to CI/CD, external repositories and image build solutions such as Helm, Ansible and RedHat Operators.
DeployHub organizes your shared or private microservices and reusable components via Domains. Domains support the creation of catalogs where developers can go to find and share reusable objects of any type (microservices, scripts, web components, SQL.) Domains are defined to meet your unique requirements as no two organizations are alike in terms of structure. Domains are organized based on functional areas, geographical divisions, and security. Building a Domain Driven Design is a key step in achieving a successful microservices implementation. Without Domains, microservices and reusable objects are not easily shared across teams.
Note: DeployHub Team, the free SaaS version, does not include the use of “Divisional Domains.” It allows as many ‘Global’ Domains as needed.
The lowest level Domain is a Life Cycle Domain. A Life Cycle Domain includes steps that can integrate with your external Continuous Delivery (CD) Pipeline orchestration tools. Life Cycle Domains can be used in place of a CD Pipeline and integrate with Continuous Integration workflows.
DeployHub includes a central engine that can be installed locally or accessed via the SaaS offering. The central engine connects to external repositories, CI/CD engines, DevOps tools, datasources, transfer protocols and notification tools. DeployHub’s open architecture allows you to plug-in the tool set you use to define your deployment configurations.
Reverse Proxy and SaaS
If you are a SaaS customer, a ‘one-way’ reverse proxy is used on your side of the firewall. The reverse proxy can be timed to submit request for deployments based on the installation parameters.