How it
works?
The Rhizomind platform was created by hardcore Java developers fed up with doing the same things every time for new customers requiring a software solution: write, compile, verify, deploy. And with the CI/CD setup each time consuming up to 25% of the total resources allocated to a project, this was a costly process and always underestimated in terms of time and resources.
Identifying these steps helps to create a reliable development ecosystem, useful for multiple projects.
In order to write and launch code, the whole ecosystem is required.
Whether you’re going with a full, on-premises installation (bare metal or cloud) or integrating with your own environment, as a first step we transform available resources with our proprietary scripts (a mix of Ansible/Helm/Terramorph) by setting up a K8s cluster along with hosting several isolated spaces. It’s a highly customizable procedure in which the components can be freshly installed – or we can integrate existing ones (like your SCM, issue tracker, monitoring tools).
In around two hours your new Rhizomind platform will be transformed from a clean slate into a fully integrated ecosystem.
Log in to the Rhizomind dashboard and start creating a microservice right away.
Since Rhizomind’s philosophy is to focus on an opinionated stack, we offer numerous blueprints (constantly improved and expanded) to help kick off your project. For instance, you can go with a typical Spring Boot stack and spawn a backend or create a frontend POC along with React.js as a leading stack. The execution of code archetypes creates and pushes the first revision of the service straight to the SCM, which in turn instantly triggers the build pipeline.
Any pull request raised within the SCM triggers a rigorous test procedure.
A strict code quality gate will force the developer to create various types of tests right from the beginning of the lifespan of the service. Unit tests are mandatory, but integration, e2e, and OWASP tests can be enforced as well by changing platform settings. Emphasis on contract testing is one of the crucial aspects of the Rhizomind CI pipeline. All test types are backed by code templates so developers aren’t left clueless about where to place them or how to make their results available for evaluation.
Once code quality requirements are met, pull requests are automatically merged to the master branch.
You read that right. By default, Rhizomind does not utilise the develop branch, because if a code change passes the strict validation process, it's potentially production ready. Our solution was created with continuous deployment processes taken seriously, which drastically reduces time-to-market and promotes frequent but safe deployments.
Necessary Docker files are generated and pushed to the SCM when the service is first created. Likewise, the K8s config files and deployment profiles are also auto-generated and placed next to the code, saving time and reducing error probability – compared with the old-fashioned copy-paste style of work. Still, engineers are welcome to tune them if needed.
The final result: an updated service is redeployed, ensuring a true continuous delivery experience.
Instantly review changes in the updated revision of your software. We constantly relaunch services at our Kubernetes-governed spaces. There are four of them by default: SIT, UAT, REL, PROD. All accessible by developers, devops and managers alike via the Rhizomind dashboard, offering comprehensive oversight over the whole project. Your team can harness the power of information by just taking a glance at the constantly refreshed service statuses.
Rhizomind is a solution that unleashes developers’ potential.
It takes the process of software development to the highest level of automation, slashing communication and administration tasks to the barest minimum, leaving teams to focus solely on writing code!
... and last but not least
Since every service is constantly monitored, users can access their current status with ease: from an overview of recent commits, to the resource consumption of a particular service running inside the K8s cluster. The logs, health checks, quotas and general “liveness” of a given service are available instantly, as the Rhizomind platform integrates with industry standard solutions like Kibana, Grafana and Jaeger. Compacted into a simple panel, anyone, including management, can gain information about the current state of the whole system and react accordingly.
Have in mind
The regulated market environment requires that the acceptance procedure be strictly explicit; thus the manual release process is the only choice. The Rhizomind platform provides easy, wizard-styled functionality to aid the product owner in identifying changes since the last release. Test results and code metrics are also available, helping out when it comes to deciding on whether to sign off on the release or scrap it. Keep in mind that all activities are tracked, so it’s super easy to know exactly who created and deployed the release along with its changes.
