Microtica is a low-code DevOps automation platform that enables companies and individuals to adopt cloud much faster.
Microtica does that by standardizing the way to develop and release infrastructure and applications in the cloud.
#How is Microtica different
We take a different approach for infrastructure and application delivery automation that gets you started with the cloud immediately.
Here are some aspects that differentiate Microtica from the other tools:
- No need to write custom integration scripts to be able to interact with the cloud.
- Integrated with Kubernetes. From production-ready infrastructure to delivery automation for your applications.
- Ready to use infrastructure components to setup a complete infrastructure without writing any custom code.
- Rich CI/CD functionalities in one platform.
- Collaborate easily on solutions with your teammates using tried & tested collaboration tools (Git, Slack etc.)
Other CI/CD tools
The biggest difference between Microtica and other tools is that Microtica is more focused on abstracting the complex cloud and Kubernetes integrations supported natively in the platform and in the same time providing all core features for optimal CI/CD.
The other tools usually require the use of other provisioning tools and you need to write most of the scripts to make things work. Microtica provides cloud infrastructure setup and application lifecycle. Having them both you can deliver your solutions in the cloud with just one tool.
Other Low-code platforms
The biggest advantage of using low-code or no-code tools is that you can quickly release your applications without having to worry about additional setup and maintenance of the underlying infrastructure and automation.
The biggest disadvantage of using these types of tools is the lack of flexibility. If you need to do something more from what they are intended to do than you end up being limited or completely stacked.
Usually, no-code tools are subject to vendor lock-in which is not popular among companies and individual developers.
The difference with Microtica is that we do not vendor lock-in our users. Resources are provisioned and data is stored on the user’s cloud account. The user has full control over the resources provisioned by Microtica and his data.
No vendor lock-in
We enable you to continue operating infrastructure and applications provisioned by Microtica if you decide to maintain them without Microtica.
Compared with the limited CI/CD functionalities of the low-code platforms, Microtica provides feature-rich functionalities that can stand side-by-side with specialized tools for CI/CD automation.
Microtica is a collaborative platform where developers can work together building solutions.
What we want to achieve with Microtica is to have a really low bar for devs to start working on the cloud and infrastructure through that layer of abstraction, but on the other hand offer that really high ceiling in terms of flexibility of what you can achieve if you already know what you are doing or are experienced in DevOps.
An example of that would be an experienced developer in the AI field, can define a complete infrastructure and applications. He/she can write custom code to achieve this and here comes the flexibility. Now, another developer or even someone not so familiar with technology could pick the component and start using it without writing any custom code at all within Microtica. Having few of those custom components you can build any kind of system like playing with legos.
Project is a top level organizational entity in Microtica. It is a logical group for your infrastructure components, pipelines, environments and Kubernetes services.
There could be multiple users assigned to a project with certain access privileges. Adding users into a project is done by inviting them to join.
Component in essence is a wrapper around AWS CloudFormation with added values for:
- enhanced capabilities for distributing and sharing cloud infrastructure among teams and cloud accounts/regions
- built-in CI automation using Microtica Pipelines
- custom validation using JSON schema
- building complex infrastructure with drag-and-drop
Environment is a logical group of multiple combined components that represent one complete and isolated system.
Environments are usually represented as Development, Testing, Staging, Production etc.
Let’s say you need to build a system for order management. You create an environment dedicated for this setup and then add required components in the environment. Components could be: Virtual Private Cloud, MySql database, Kubernetes cluster, S3 bucket etc.
During environment deployment, all components will be provisioned on your designated cloud account leveraging CloudFormation.
Microtica has a built-in support for provisioning production-ready Kubernetes infrastructure and deploying resources on Kubernetes.
Kubernetes resources are represented as Services in Microtica. We provide default Kubernetes spec for services but you can also write your custom spec by placing kube.config file in the root path of your source code.
Using Microtica Kubernetes dashboard you can see all your services, monitor how they are running, and detect issues.