Jun 04, 2018 • 2 min read
Traditionally, deploying product or new features is a slow, complex & mentally draining process. Thus, deploying code to production comes with anxiety and a “hold your breath” mentality.
Developers have to stop building, refocus & babysit the release process. You can already see why we believed this traditional process had to be automated. We wanted to remove these pains and turn releasing code into a background task that requires minimal mental drain.
True to our vision
Veryfi’s vision is to simplify, optimize and automate bookkeeping. Keeping true to our vision and culture, we automated code deployments to remove the pains of rapid code releases at scale. This means we deploy across 4 geographies daily, multiple times each day without a drop in experience or downtime.
If you are a developer and wondering: “What about the database? How do you roll that back?” Well we’ve got that sorted also. But I’ll leave this for a future blog post.
These good internal practices have a positive effect on our customers and their experience with Veryfi product.
- Faster product updates & new features to your devices. When we start on your feature request it gets released faster — that’s days/weeks not months.
- Higher frequency of updates to your devices without a negative experience — bug fixes go out in minutes or hours! and…
- Fewer product downtime because there are less things that can go wrong with a release that’s 100% powered by machines.
Below is a series of articles which explain in detail (mostly technical) how we achieved this feat. Enjoy!
- Dockerizing a web app, using Docker Compose for orchestrating multi-container infrastructure (part 1 of 3)
- Deploying to Docker Swarm on Microsoft Azure (part 2 of 3)
- Creating a Continuous Deployment Pipeline with BitBucket, Jenkins and Azure (part 3 of 3)
Finally, if you have questions or want to learn more about this please reach out to us on firstname.lastname@example.org
All this in the ONE Place.
30 sec to get going. No credit card required.