Skip to content

ElasticDev

What is ElasticDev

ElasticDev provides complete DevOps solutions through an open source marketplace.

The missions is two fold:

  • Provide usable DevOps automations for developers - no assembly required.
  • Provide technology glue for DevOps engineers to layer their existing investments into immutable automations

Through ElasticDev stacks, DevOps expertise is encapsulated and transmitted from DevOps experts to developers.

Why ElasticDev

Ready to Use Automation

  • Instead of having to learn developer tools, you select off the shelf DevOps solutions that work out of the box.
  • Whether it is continuous integration with AWS Codebuild or learning Elastic Kubernetes Service, ElasticDev provide single entry points solutuions.
  • You browse, select, and launch.

Integrate Existing Investments

With ElasticDev:

  • Do not abandon your existing investments with technologies such as Terraform and Ansible. ElasticDev extends those investments.
  • Similar to Docker, ElasticDev layers automation on top of automation. ElasticDev stacks are immutable, reusable, and shared.

Customization and Complexity

ElasticDev allows you to create complex automation while preservering authoring simplicity.

  • Authoring occurs only the “current” layer.
  • Downstream layers and dependencies are automatically handled.

Unlike other pipelines (e.g. Gitlab, CircleCI, Jenkins), ElasticDev stacks (pipelines) allow for many layers (nested) of automation. For example, Gitlab permits one parent, one child, and at most one grandchild. It is not uncommon for a single ElasticDev stack (pipeline) to contain 5 to 10 layers.

Secure

Most automation products do not tracked and recorded sources of automation. You need to perform periodical audits that are costly and resource intensive.

ElasticDev’s (ED) approach is intrinsically transparent, visible, and secure.

  • Low level components are glued into stacks.
  • Sources are always known. Through source repositories (e.g. Github,Bitbucket …) We record who authored the component, what the component is, and when the component was committed.
  • During execution, automation is broken into discreet actions that are listed, executed, and recorded.

In summary, source components are tracked and recorded. Security audits before, during, and after execution are itemized and presented.

assets_graph

Graph Assets