In my previous blog post, I discussed the importance of Database DevOps and why it's worth embracing in your business. Now, I want to take this opportunity to delve into the world of Redgate and share with you why Flyway, our flagship DevOps Automation tool, should be on your radar.
If you're not familiar with Redgate or haven't had the chance to be one of our clients, allow me to introduce you to our current focus and projects in terms of DevOps automation at Redgate. As an Automation specialist at Redgate, one of my goals is to facilitate the development and implementation of our solutions, while also providing training and guidance on best practices, internally and externally. This involves leveraging Redgate tooling, integrating automation into clients' pipelines, and fostering a culture of continuous improvement.
Fortunately, Flyway by Redgate offers a seamless and straightforward approach to DevOps Automation. Flyway provides a comprehensive solution for rapid database development, version control, migration script generation, and automated deployments. But it doesn't stop there - Flyway also incorporates numerous features that enhance visibility, reliability, and scalability. However, what truly sets Flyway apart, in my opinion, is what I refer to as the Flyway Framework.
When you choose Flyway, we equip you with both a user-friendly desktop GUI and a command-line interface (CLI). A huge benefit that comes with Flyway is that every action you perform within the GUI or application can be translated into CLI commands, seamlessly integrating with other tools like Azure DevOps pipelines. As part of my role, I dedicate myself to crafting elegant Flyway code and pipelines that enable seamless deployment cycles, ensuring ease of integration for our customers utilising CI/CD tools and platforms.
Unlike other methods that aim to streamline manual processes as we do, Flyway emphasizes openness and framework-like flexibility. While similar tools often impose rigid workflows and strict requirements based on specific database types and locations, Flyway allows users to work with diverse environments and maintain their existing workflows. This means that transitioning to Flyway incurs minimal costs, as users can incorporate automation without completely redesigning their systems or infrastructure, abandoning established working practices, or disrupting team dynamics. At Redgate, our mission is to empower our customers to embrace DevOps in a way that aligns with their unique needs. As a result, Flyway can adapt to the requirements of an enterprise account just as effectively as it caters to a startup. We actively collaborate with our customers, understanding their current processes, and assisting them in transitioning smoothly while retaining the aspects they value most.
I often describe Flyway as an underlying layer that enhances existing systems, improving what already works and addressing areas that require attention, all while providing ample room for future enhancements. At Redgate, we are committed to providing our customers with the freedom to utilize our solutions in the way that best suits them. For example, if a customer prefers to integrate the Flyway CLI into a Jenkins build, they have the flexibility to do so. Similarly, if a customer wishes to adopt automation at a slower pace due to readiness concerns, they can selectively choose the Flyway features they want to employ immediately.
By offering this level of adaptability and empowering our customers to leverage Flyway according to their unique requirements, we ensure a smooth and customizable DevOps journey that builds upon their existing systems and processes, ultimately driving significant improvements when they are ready. Recently, I had the opportunity to work with a customer who expressed their delight in our customer-centric approach.
One crucial aspect of the Flyway Framework is its Versioned Script capability. Let me share an example with you. One of our clients faced challenges in implementing DevOps, particularly in managing a specific deployment order that often resulted in unsynchronized production databases. They required a solution that could automate this process, providing visibility into each independent database within their extensive estate of over 200 databases, while intelligently synchronizing them without burdening their team. Many existing solutions would have forced them into rigid workflows with synced databases but limited freedom or unsynchronized databases without a reliable deployment process. However, Flyway stood out as the tool that could meet their requirements due to its unique approach and comprehensive feature set. After a short whiteboarding session, we came up with a very elegant design:
The beauty of Flyway doesn't end there. Every time I engage with customers, they're amazed by the capabilities of Flyway. It's a testament to the value it brings. Migrating to this kind of DevOps approach can often be perceived as complex and costly, leaving organizations with solutions that may not fully align with their needs or are overly burdensome. However, we at Redgate believe that DevOps automation doesn't have to be daunting or expensive. In just a matter of weeks, we were able to guide the aforementioned customer, who initially lacked confidence in their ability to transition to DevOps, through the design of an ideal system. We demonstrated the tangible benefits of automation with Flyway, leaving them impressed and confident in the value it brings. In the end, the workflow we made looked amazing, and sums up Flyway:
In conclusion, Redgate's Flyway Solution is an advanced and remarkable tool that can significantly enhance your DevOps journey. Regardless of whether you're a small company or a large enterprise, Redgate offers a path forward for achieving greater DevOps maturity. If you're sceptical about the simplicity I've described, I encourage you to get in touch with us. Let us show you first-hand what Flyway can do for your organization.
Next time I am talking about Unit Testing, and how to implement it into your workflow, if you noticed the image above you should see a Build database, which is where all of that will take place!
Comments