Skip to content

QuickStart: Usage for Developers

Warning

This functionality was originally offered by the parent company as a separate product Fathomable. It is undergoing consolidation into Cyvive's core and is restricted to beta customers at this time. Please contact your account manager via live-chat should you wish to participate.

Governance Overview

Cyvive.io is Cloud Native & Layer 4 - 7 OSIMM Compliant and as such implements a Governance via Policy approach through YAML configuration files created per Micro/NanoService.

The language used in configuration description is not arbritary, and is architecturally and contexturally derived from partnership with 3 Universities and over 35 industry publications with containerization viewpoint spanning from MicroServices Architecture through to Enteprise Architecture principles.

The configuration approach is powerful enough to handle governance of any type of application in the modern technology stack including 'cloud functions' while being flexible enough to be used in ordinary conversation between teams, departments and vendors.

A detailed explanation of the configuration options is available

Enabling Governance of your Micro/NanoService

… is accomplished via a POST call to Cyvive.io. If running via the provided 'httpie' container

http POST cyvive:3000/data technologyDescriptor:='{"exampleGroup": {"exampleApp": {"version": "v1.8.x"}}}'

YAML as a string can also be provided if required under the technologyDescriptorYAML parameter

Governance assets are automatically versioned based on the version parameter

Deploying a Governed Micro/NanoService

… is also done via POST call. If running via the provided 'httpie' container

http POST cyvive:3000/namespace deploymentTarget=development require:='["exampleApp.exampleGroup/"]' template=dev

Briefly expanding the parameters:

  • deploymentTarget is the namespace / environment that Cyvive.io should create or update
  • require albiet an optional field will be used frequently by all developers. It provides the root of the governed dependency tree(s) to be deployed. As Cyvive.io is Layer 7 compliant each require is a Uniform Resource Identifier (URI)
  • template is a higher level Governance Technology Descriptor. At its core separated into 4 logicical types (development (dev) => high availability (ha) => performance (perf) => production (production)) with the default names provided in bold. Any number of template(s) can be created with custom names for each as long as they map to one of the core types for enabling / disabling elevated functionality. Additional information is available

Removing a deploymentTarget

… accomplished via standard DELETE call. If running via the provided 'httpie' container

http DELETE cyvive:3000/namespace/development

Purging a Micro/NanoService from Governance

… accomplished via standard DELETE call. If running via the provided 'httpie' container

http DELETE cyvive:3000/data/exampleGroup.exampleApp

This will not actively purge any deployed assets in targets, just this asset from Governance and by defacto future deployments.

Additional Reading / Information