Reasons to Transition from Prefect 1.0 to 2.0

An updated version of the pipeline orchestration framework we know and love

Photo by Federico Beccari on Unsplash

If you’re an avid Prefect user like I am, then you’ve probably heard that they recently launched Prefect 2.0 as a new and improved version of Prefect 1.0. With many popular tools, version changes don’t often include such drastic improvements. They may fix a few bugs and add a few new features.

However, Prefect 2.0 really helps to simplify the previous workflows being used in 1.0. It still includes all of our favorite features (scheduling, retries, notifications, an easy way to pass data, etc) while making it easy to take on incremental adoption. Scheduling a new workload is now even simpler, with two lines of code:

pip install prefect
@flow

In this article, I’ll be highlighting the main reasons to transition from Prefect 1.0 to 2.0 now, rather than waiting. Like you, I had to do my research too to see if it was worth prioritizing the migration over other projects. I have to say, I’ve come to the conclusion that migrating now will save me work down the line, and allow me to take advantage of some of the new awesome features now! By switching to 2.0, you will no longer have the FOMO that comes along with working with an old version of a tool when everyone else is…