Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
Great Orchestrator
What do you like best about the product?
- Easy to set up your first pipelines.
- Very code-centric. Making tasks feels more natural than other orchestrators.
- Easy to troubleshoot/debug.
- The automation feature on prefect cloud is great for managing notifications.
- Plenty of documentation.
- Very code-centric. Making tasks feels more natural than other orchestrators.
- Easy to troubleshoot/debug.
- The automation feature on prefect cloud is great for managing notifications.
- Plenty of documentation.
What do you dislike about the product?
- I'm not a fan of the deployment model. may be my fault but having the same pipeline for multiple environments (dev/prod) feels hacky.
- The flow UI can be confusing especially when writing a true DAG.
- Some examples on the documentation don't actually work.
- The flow UI can be confusing especially when writing a true DAG.
- Some examples on the documentation don't actually work.
What problems is the product solving and how is that benefiting you?
Prefect is solving the problem of centralizing orchestration. We have a lot of servers owned by different employees running cron jobs. Moving this to prefect allows us to see the whole environment. Prefect was also an easy transition for python developers to write automations since it feels like natural code.
- Leave a Comment |
- Mark review as helpful
Prefect Flows make your life easier!
What do you like best about the product?
The Logs for Flow Runs help you identify exactly where the problem lies which saves a lot debugging time. Prefect provides a seamless workflow for testing your code and logging the test results.
What do you dislike about the product?
Filtering through flow runs could be improved by adding more filters/search capability. I would prefer a filter for "My Flow Runs" to quickly access my flow runs. Maybe a search option with auto-populated tags related to the flow runs can help filter through the runs more efficiently.
What problems is the product solving and how is that benefiting you?
Prefect helps my team review each other's code on GitHub; we are required to add successful Prefect Flow Runs in our pull request template. It provides a standard workflow to test out the functionality of the code and log the tests' results.
Breaking down barriers for deploying workflows
What do you like best about the product?
I've followed Prefect since version 1, and have happily observed as my suggestions on their (very responsive) Slack-channel have made it into production.
Very little initial code is required to register a flow, subflows and subtasks, but the options are vast. I do relatively simple ETL-jobs, but find myself eliminating a lot of the manual checks as I can trigger flows based on events in others.
The API is decently documented.
Elegant retries, flow-naming and options for task-runners.
If your are like me and found Airflow daunting - this is a really good choice.
Very little initial code is required to register a flow, subflows and subtasks, but the options are vast. I do relatively simple ETL-jobs, but find myself eliminating a lot of the manual checks as I can trigger flows based on events in others.
The API is decently documented.
Elegant retries, flow-naming and options for task-runners.
If your are like me and found Airflow daunting - this is a really good choice.
What do you dislike about the product?
It's in rapid development, so pay attention to the release logs. As an example, I used to deploy using Python objects, but now there preferred option is the prefect.yaml file.
Some of the development is not always reflected in the documentation, but they are catching up.
The Flow-view can be a bit cluttered if you have some jobs that run for a few minutes and others for hours.
Some of the development is not always reflected in the documentation, but they are catching up.
The Flow-view can be a bit cluttered if you have some jobs that run for a few minutes and others for hours.
What problems is the product solving and how is that benefiting you?
Overview and orchestration of our daily imports using Python. I can rerun jobs with different input variables and get comprehensive results if something fails.
I can spend more time on other things.
I can spend more time on other things.
Pretty Solid Orchestration tool
What do you like best about the product?
It is quite easy to anotate existing python code and convert it in a prefect flow without changing a lot of code.
The hybrid architecture which uses agents or workers allows you to have a lot of flexibility on where and how the code is executed. This also allows you to have isolated environments for every flow in a cleaner way than something like airflow.
The hybrid architecture which uses agents or workers allows you to have a lot of flexibility on where and how the code is executed. This also allows you to have isolated environments for every flow in a cleaner way than something like airflow.
What do you dislike about the product?
Prefect 2 is still a young framework and it is still under construction so expect it to have a lot of constant updates and posible breaking changes.
Its community is not as big as something liker "Airflow" so it lacks a lot of connectors and also some of them are not frequently updated.
Its community is not as big as something liker "Airflow" so it lacks a lot of connectors and also some of them are not frequently updated.
What problems is the product solving and how is that benefiting you?
Prefect has allowed us to orchestrate all the processes needed to create and maintain our data warehouse and our data lake while being simpler and cheaper than Airflow.
An Amazing ETL Tool That Is Constantly Improving
What do you like best about the product?
Prefect allows me to develop, organize, deploy, and monitor my ETL processes quickly and easily. I appreciate that their documentation is top notch, and their support Slack channel is very active with both community members and Prefect members. Their Slack chatbot Marvin is also very helpful.
What do you dislike about the product?
The most frustrating part of working with Prefect is that they don't offer simpler on-prem compute.
What problems is the product solving and how is that benefiting you?
Prefect lets us develop and execute workflows to process client data daily. Since adopting Prefect we have been able to parallelize our processes very simply, which has been a great help.
Prefect: A great introduction to ETL and further.
What do you like best about the product?
Prefect has well maintained documentation and a helpful community willing to advise and assist people new to ETL and Data Orchestrations. Prefect cares about their user interface and it shows. I really enjoy working with the UI.
What do you dislike about the product?
Prefect is always working on new features/releases. So, it can be a bit overwhelming to keep up to date with all the useful features they release. The feature tutorials usually cover the fundamental uses. It would be nice to have some tutorials that cover more "complex" uses to contrast against.
What problems is the product solving and how is that benefiting you?
Prefect's environment helps us automate repetitve tasks saving us time and effort spent.
Prefect is always improving their user interface with user feedback. Thier UI helps us better visualise our workflows.
Prefect is always improving their user interface with user feedback. Thier UI helps us better visualise our workflows.
No strings attached onboarding and trial
What do you like best about the product?
Easy to pickup syntax and mental model. Decoupled code. Great documentation.
What do you dislike about the product?
Pricing plans. Big jump from free to the next paid plan.
What problems is the product solving and how is that benefiting you?
Data pipeline orchestration that anyone can easily understand.
Easy to get going, very flexible tool
What do you like best about the product?
Prefect's documentation is excellent, and the support team is responsive and knowledgeable. We've been able to quickly get up to speed with the tool and troubleshoot any issues that arise.
What do you dislike about the product?
There has been some parity differences between prefect 1 and 2 and although the team behind Prefect has been releasing new features / changes at an exceptional rate it would have been nice if some of those things were in the product at launch
What problems is the product solving and how is that benefiting you?
It is allowing us to orchestrate our data pipelines.. providing notifications and observability into the processes which run our data stack.. without which we could not operate.
A step above our previous tool - cronToGo
What do you like best about the product?
great ui
good visibility on workflows
easy to see dependencies between tasks
good visibility on workflows
easy to see dependencies between tasks
What do you dislike about the product?
Having to rewrite our existing cron jobs in python
What problems is the product solving and how is that benefiting you?
ability to orchestrate complex workflows with a lot of dependencies between them
Finally a workflow orchestration tool that just works
What do you like best about the product?
Prefect was seemless to setup and to operate. The documentation is clear, the team is super helpful and it's moving in the right direction. As a Data Scientist, I can focus on improving my models and tweaking my optimization logic. Prefect takes care of data, training and inference pipelines. I am getting notified in case of problems. I also like that it's cloud provider agnostic.
What do you dislike about the product?
It's still a young(er) tool, which had some bigger, breaking changes during the last year. This is causing quite some extra dev work. I hope they are done with those big changes.
What problems is the product solving and how is that benefiting you?
Prefect helps me to automatically schedule and run data & machine learning workflows in the cloud. With this serverless setup, I am saving costs and dev / maintainance work.
showing 51 - 60