Deliver your ideas in the cloud with just one tool
Reusable pieces of user defined cloud infrastructure, they are meant to be created once and reused as many times as you need. This solves the problem of needing to rewrite or adapt the infrastructure every time you want to reuse it in another project or product you are developing. Their reusability also comes from their isolation, they should not reference each other unless it is done through the Microtica configuration page, making them independent.
Microtica provides ready-to-use components that can handle your infrastructure or you can write your own using AWS Cloudformation templates, making the benefits obvious, easy to use, flexible, and a single source of truth for your infrastructure.
Use your existing CloudFormation templates to provision infrastructure with Microtica. Just include the two required files microtica.yaml (pipeline definition) and a schema.json (for validation) in the source code.
Infrastructure component for AWS DynamoDB table setup
AWS S3 bucket component with available access control
Infrastructure component for complete Kubernetes setup on AWS
AWS RDS MySql serverless database with backup and scaling support
Infrastructure component for managed Redis in-memory store
AWS VPC infrastructure setup with private and public subnets support
Automating your workflow can be achieved by using pipelines as they are the heart of the CI process in Microtica. The build process of every component and microservices, whether it’s triggered manually or automatically, is done in a pipeline. The build process is defined by a single source of truth, a microtica.yaml file in the root folder of the repository. With user customizability as a key feature, every user is able to define how their build process is done and what commands are ran by changing the microtica.yaml file.
Quickly see a detailed view of your build processes, allowing you to see what the build process are doing in real time and help you identify any issues, all without leaving the Microtica website.
A full integration with Slack allows users to recieve notifications after some actions are finished, in this case, whether the pipeline was successful or not.
Environments are isolated logical groups where components and microservices live and are deployed. Their isolation allows for teams to work on a different phases of software delivery without impacting each other. As environments house components, everything regarding them, from their configuration to deployment logs can all be seen on an environment. Before an environment deployment, an environment plan is automatically created, which gives an overview of the changes that will happen from the currently deployed version to the one you are trying to deploy, allowing for more control over changes.
If anything goes wrong with the deployment, in place is a system which will rollback the environment to the last working state, without needing anything to be done by the user.
With the replicate environment feature, it solves the issue of creating the exact environment for other purposes, example: temporary production-like environments for performance testing or going from DEV to TEST.
Microtica offers you to deploy microservices with Kubernetes in no-time.
Setting up a microservice can be done automatically, by using our microservice generator which generates the needed files, or manually, by creating the two required files – microtica.yaml (for the build process) and a schema.json (for validation). In the Microtica Kubernetes dashboard you can see all your microservices, monitor how they are running, and detect issues. Microtica automates your entire CI/CD microservices process.
Public DockerHub images
Private AWS ECR repository
Artifacts from Microtica pipelines
Automate your cloud sleep cycles. Wake cloud up only when you need it.
Invest the savings back in your business.