Can we make Cloud Automation as simple as Scratch? Coding, testing and secure running of automation workflows with Fylamynt.
My six year old son recently started learning how to code using Scratch.
As I watched him move the funny looking cat (called Sprite in Scratch) all over the canvas with a few simple drag-and-drop blocks that snap into a larger program, I was amazed at the simplicity of the environment and how intuitive it was. He was soon coding more complex programs and even tinkering with existing game projects.
The question that ran through my mind was:
Can we make Cloud Automation as simple as Scratch?
When Xiaoyun, David and I met in the early months of last year, we had long debates about the state of DevOps/SRE. All three of us are infrastructure geeks with more than a decade each of experience building products and managing teams that solved various management and operational problems in both the public and private cloud. And we all arrived at the same question via different routes:
Why is "fixing infrastructure problems" so hard?
We talked to dozens of practitioners with varying backgrounds ranging from on-call engineers, SRE teams, automation engineers, VPs of IT and CIOs - and we heard the same pain points again and again. It takes a village to maintain high availability (say 99.99%) and hundreds of late-night hours to fix problems in infrastructure.
As we dug into the Ops workflows that we were all too familiar with, we saw a familiar pattern. We could monitor every aspect of cloud infrastructure and analyze every log, metric and event that is generated. Advances in monitoring, tracing and data analytics (the Fylamynt founding team has personally built several products and have patents in this area) can help you in diagnosing problems.
What about fixing?
In today’s large-scale dynamic cloud environments, a fix is not simply one operation (e.g. reboot a VM) which you can quickly execute and move on. You need a runbook (or a workflow) that consists of a series of operations interspersed with logic that can be run in an automated fashion.
What’s the biggest challenge in building this workflow? We realized that the challenge is not the tools (e.g Terraform) or languages (e.g. Python). But, it lies in the the Coding, testing and secure running of automation workflows.
Let me introduce you to Fylamynt, a low-code platform that is as intuitive and simple as Scratch, that helps DevOps and SRE engineers automate their workflows. Using our intuitive visual editor, you can
- Configure an alert response
- Apply multiple changes in your infrastructure
- Add diagnostics
- Send messages over Slack
- Close JIRA tickets
- And much, much more
...all with drag-and-drop and a few clicks. You can run the workflow securely in a dedicated, single-tenant SaaS environment built for you.