Oatfin Universal Build Artifacts
Thanks again for subscribing to Cloud Musings! Last I checked, it was 46 subscribers strong on LinkedIn. If you haven't subscribed, subscribe to get automatic updates when I publish new editions! My ask as always is for introduction to investors and enterprise partners who are excited about the cloud and developer tools space.
In a previous edition, I mentioned how we solve the problem with managing and sharing cloud credentials among developers in one place and how it was a complete accident. There is a lot of examples of things we've done that fits this pattern.
This is an example where originally we wanted to simply define a team's docker containers. Super simple idea, but turns out it is a huge problem maintaining build artifacts and versions. Using our app, you can list any docker container from any registry.
Extending on this idea, we're building a complete lifecycle management for build artifacts whether that is a docker container, a war file, compiled javascript, etc.
Why is this important?
In my experience, having the ability to quickly switch between artifact versions is critical for a lot of teams. Developers often make mistakes and have to roll back production releases.
The current workflow is painful: find the bug, write a patch, regression test, build, push, and manually test the new artifacts which means a lot of downtime for users. At some companies, we only released code late at night when traffic was slow and depending on the release could last 12+ hours, but we still had to show up for work the next day because that fix we rushed through could cause further problems.
For developers, this is one of the main causes of burnout and often times, these problems can be solved with investment in the right tools. This is why we're working on Oatfin. Our mission is to improve developer productivity and the development experience.