Featured WhitePapers & Blogs

This whitepaper covers how your CI/CD pipeline will be disrupted when you shift from a monolithic development approach to a microservice architecture.
Versioning Your Microservices
Moving away from monololithic style software development shifts the configuration issues from source code to microservices. This whitepaper discusses the upcoming challenges faced by teams moving to independently deployed services.
Navigate the Microservice Deathstar
This blog covers how configuration management is shifted to runtime in a microservice implementation.  Learn how DeployHub navigates the microservice deathstar with runtime configuration management.
Migrating to Microservices – Step 1: Define your Domains
Migrating to microservices requires you start thinking about how to organize your applications based on components and how those components are to be organized.  A Domain Driven Design is key to your long term success in microservices architecture.  This whitepaper introduces the concepts.
Solving the Kubernetes Pipeline Challenges with DeployHub
As you shift away from monolithic pipelines, you will be faced with a few new challenges to support Kubernetes and microservices. This whitepaper covers what these challenges will be and how DeployHub addresses them.
From Legos to Transformers – the Shift in Versioning and Configuration Management with Microservices
Now that software builds are small, or non-existent, the versioning and config. management tasks have shifted to run-time. This whitepaper explores this change.
Achieving Continuous Deployments with DeployHub and Jenkins
This whitepaper shows how to use your Jenkins Pipeline to orchestrate continuous deployments to production with DeployHub.
More

Technical Docs

Demos and Setup

Tips and Tricks

Use Domains to organize microservices and reusable components for easy sharing. Domains help you define logical groupings of services and supports your microservices domain driven design.

DeployHub supports the ability to jump between any two software releases (4.1 to 4.8 for example) incrementally for managing software deployment. No monolithic deployments are needed. This includes updates to the database.

DeployHub automatically updates configuration files even when embedded into your jars or wars. Deploying to different states in your continuous delivery pipeline requires that these configuration files be updated for the appropriate location.

Learn how to execute a procedure on a remote endpoint as part of a component or software deployment install step. This process automates your continuous deployment across the continuous delivery pipeline in a repeatable manner.

This Demo shows how you can bring z/OS into the Jenkins Continuous Delivery Pipeline, creating a ‘super’ Application Package that deploys artifacts from z/OS, and in this demo, Windows.

Tutorials