DevOps

Updated: July 13, 2021

Contents

The DevOps module enables CloudBlue Connect users to manage their Extension as a Service environments within the system. Thus, before continuing with the DevOps module description, it is necessary to define the Extension as a Service concept on the CloudBlue Connect platform.

Extension as a Service

The Connect platform is designed to be integrated with various systems and services. Most accounts on the platform (whether it is Vendors, Distributors, or Resellers) are likely to be integrated with one or several systems as schematically illustrated in the following diagram.

As highlighted in the diagram above, these integrations require a specialized “middleware” service that represent an integration layer between third party systems and the CloudBlue Connect platform. Such middleware services are typically referred to as extensions.

In general, extensions are deployed and implemented by system integration teams (System Integrators) that work in the context of a particular Connect account. These integration teams should also build an operational environment as schematically illustrated in the diagrams below.

Furthermore, efforts that are required to implement an extension can be allocated into the following financial buckets:

Development Costs: Efforts that are required to learn the system and develop business logic required to perform the integration operation. These costs is usually expected and don’t cause many issues at this point of time.
Operational Costs: Efforts that are required to build an operational environment and use it to run the integration itself on a daily basis. These costs are mostly unexpected and cause issues since few system integration teams have relevant experience to accomplish this task in the first place.

Therefore, CloudBlue Connect presents an ultimate solution to drastically decrease operational costs for deploying and implementing required extensions. The Connect platform provides the users with an operational environment as a service, hence the term Extension as a Service.

Module Overview

The aforementioned extension-as-a-service environment is presented on the CloudBlue Connect platform within the DevOps module. Thus, Connect helps your integration team build a comprehensive extension for your system and the platform. Note that using the provided standardized environment is optional, meaning that Connect users can also deploy their own custom environment.

The following introduces, illustrates and describes general features of the standardized environment and the DevOps module:

Monitoring & Logging

The DevOps module provides an out-of-the-box functionality that enables Connect users to monitor their deployed extension on the platform. Therefore, you can examine your deployed service status, average network, memory, CPU usage, and more. In addition, note that Connect users can also learn more about their deployed systems by accessing logs and events that are available within this module.

Horizontal Scaling

Another out-of-the-box feature of the DevOps module enables Connect users to address the horizontal scaling. Namely, users can add more instances of machines to their existing pool of interconnected computer recourses. Therefore, your systems workload can be distributed across different machines, which in turn can greatly increase your system performance.

Local and Cloud Modes

The DevOps module features Local and Cloud development modes. Specifically, the Local mode, as the name implies, is used to develop and deploy required middleware locally. The Cloud development mode is used for the source code delivery and version management. The Cloud mode features Git repositories; note that private repositories are also supported. Furthermore, Connect users can switch between Local and Cloud modes at any given time with just a click of a button.

Deployment Environments

The DevOps module provides Connect users with different deployment environments that can be easily managed via a single dashboard. Deployment environments represent a computer system or systems in which your software component is developed and executed. This structured release management operations allows implementing various tests, phased deployment, and rollback in case of problems. Therefore, the DevOps module features the following deployment environments:

Development: An environment that usually runs in the Cloud mode and represents a sandbox where unit testing may be performed by developers.
Staging: This environment generally works in the Local mode and often referred to as the Test environment. Therefore, it is used by developers for their test and debug scenarios.
Production: Another environment that typically runs in the Cloud mode. It represents end-user or client system.