Mike's Notes
A note to myself as I ponder what is next to do.
Resources
References
- Reference
Repository
- Home > Ajabbi Research > Library >
- Home > Handbook >
Last Updated
18/04/2025
Article
Mike is the inventor and architect of Pipi and the founder of Ajabbi.
Having completed a crash course in DevOps over the last few months, the next task is setting up DevOps as part of the stack before I go any further.
So far, I haven't even needed to use formal version control with the refactoring. Over the last 18 months, it was pretty much "snip snip snip" into microservices with a bit of a tidy-up along the way. All looks good, and it works roughly.
But it is a very different story now, getting it ready to deploy to the cloud so people can use it.
Criteria
What am I looking for when setting up DevOps?
- Version control
- It has to scale, be robust and reliable
- Automated builds
- Automated testing
- Automated deployment to multiple cloud environments
- Automated everything
- Continuous development
- Great for teams and remote developers
- Frequent small commits to the main branch and test
- It can also generate documentation
- Great reporting
- Great integration with other tools via open API
- Can include Database versioning
- Continuous Integration (CI)
Languages
It must work with;- Java
- Python
- Julia
- SQL
- CFML
- XML/XSD
- JSON/YAML
- JavaScript
- HTML5
- CSS
- and more.
Options
I prefer to go open-source, with a command line and a good GUI available, and be well-documented. So what is out there?
