Top-Down, Self-Service, Collaborative Software Deployments
Self-service software deployment means that each team, from the development through production, can have a complete view of what deployments have been done without bugging someone else. DeployHub Pro uses a Domain Driven Design model to create Group Based Security across the DevOps pipeline. This Domain based Group Security allows a development team to manage all access to their Domain such as managing releases, defining application packages, creating installation logic, and adding new users independent of a high level administrator. In the same way, testing, DBAs, and production teams can be assigned their own Environments to manage in the same way.
To achieve a self-service model, DeployHub uses this top-down approach which allows you to model your environments based on your organizational structure, defining a self-service and sustainable microservice catalog tool across teams. Each Group can be assigned to their own unique environments (Clusters, Namespaces). Your production team can track production environments, leaving developers and testers to track their own environments independently. You can also allow your developers to have ‘view’ access to the testing and production environments so they may serve as trusted partners, even though they cannot make changes. The goal is to facilitate collaboration and knowledge across all teams.
Self-Service is required with a Microservice Implementation
When you move into cloud native architecture and begin building microservice applications that are built upon shared services, you begin to understand the importance of a self-service model. With the complexity of microservices, all teams need a clear view of what versions of services are running in what environments. The purpose of a microservice catalog is to allow anyone to quickly see the overall configuration of their microservice application running in any cluster. This type of self-service software deployment data is critical for managing incident responses and sorting out why one environment acts differently from others. With so many moving parts, it is essential that this type of information is readily available and easy to understand.
Do More with Less Staff
And the biggest benefit to a self-service approach is the ability to increase the number of microservices and microservice applications that your DevOps team support without a substantial ramp-up in staff. DeployHub’s hierarchical and model driven design eliminates team redundancies, and reduces confusion and errors that are common without a central unified catalog. Your team spends less time in long meetings dealing with breaking points and miscommunication and more time delivering frequent releases at lower risk.
DeployHub Key Features
- Microservice Catalogs Explored
- Microservice Supply Chain
- A Microservice Service Catalog for Incident Response
- Domain Driven Design Catalog to Tame Microservice Sprawl
- Ship Microservices Safely – Know Your Blast Radius
- Simplifying Microservice Applications
- Microservice Configuration Management
- Database Updates Pushed Across Your CD Pipeline