Architecture
DBaasNow is the company. Lifecycle Manager is a product developed by DBaasNow, also called DBaasNow Lifecycle Manager.
The product's primary architectural components are Gateway, Broker, Plugin, Monitor, DNCollector, Repository and Coordinator. Each has a distinct responsibility. The target PostgreSQL, MongoDB and Neo4j databases run on the customer's infrastructure.
Component responsibilities
| Component | Component name | Responsibility |
|---|---|---|
| Gateway | gateway |
Reverse proxy and HTTP routing to configured product services; TLS termination and optional load balancing according to the approved deployment |
| Broker | broker |
Web UI and customer interaction, including configuration, provisioning, project administration, monitoring views and Activity |
| Plugin | plugin |
Technology-specific automation and database lifecycle operations on managed targets |
| Monitor | monitor |
Database and host health, performance and metrics monitoring |
| DNCollector | dncollector |
Collection of host and database metadata and service status from managed targets |
| Repository | repository |
Central schema for lifecycle metadata and configuration, including inventory, access, licence and operational records |
| Coordinator | coordinator |
Distributed coordination, leader election and shared cluster state where implemented |
Product components and target databases
The components belong to Lifecycle Manager, but their placement differs. Server-side product services run according to the approved deployment. DNCollector runs on the target database hosts.
The targets may be on-premises or in the cloud, provided the required network connectivity is available. Customer application data remains in the target databases. The Repository holds Lifecycle Manager's metadata and configuration.
Use deployment topology to understand placement and the Installation Guide for the supplied installation process.
Gateway and Broker
The Gateway routes configured web traffic to the appropriate product service. HTTPS termination and load balancing depend on the deployment configuration.
The Broker is the customer interface for Lifecycle Manager. It also provides service interfaces used by the platform. The provisioning, administration and lifecycle procedures in these customer guides use the Broker UI.
Use the console URL provided for your installation. See network and security for the connection responsibilities.
Automation and operational records
An authorized user submits an operation through the Broker. The Plugin carries out the technology-specific work on the selected targets. Progress and results appear in Activity.
The Repository retains the configuration, inventory and operational records associated with the project. Review request execution and status and Repository and data ownership.
Monitoring and target collection
DNCollector is installed and configured automatically when an existing database service is onboarded through Discovery or a new database service is provisioned. Customers do not install it separately.
The agent collects target-host and database metadata and service status, then sends updates to the Broker. The Repository retains the corresponding records. Host/database performance observations reach Monitor through the configured metrics services and are presented in project views.
Metadata and metrics follow different update paths. See monitoring and metadata flow and DNCollector operations for verification and troubleshooting.
Coordination dependencies
The Coordinator provides coordination and shared cluster state for workflows that use it. Its use and placement depend on the database technology, topology and approved deployment.
A database deployment that depends on the Coordinator needs that service to remain available. Before changing its placement or removing Lifecycle Manager, the database owner must review the dependency and arrange any required handover. Follow uninstallation preparation.
Plan the deployment
Plan product capacity and availability separately from the target database workload. Agree component placement, Gateway configuration and coordination dependencies with DBaasNow for the intended environment.