Prefect Cloud
PrefectReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
124 reviews
from
External reviews are not included in the AWS star rating for the product.
Prefect is Awesome
What do you like best about the product?
I love the flexibility! Also, the automatic replies
What do you dislike about the product?
So far, all our issues have been around infrastructure, but that's just bc it's a learning curve for our team.
What problems is the product solving and how is that benefiting you?
Automation, automatic retries, triggered loading
Prefect Review
What do you like best about the product?
1. It stays as close to Python best practices as possible.
2. Easy to get started with and experiment.
3. Hybrid nature allows for secure data handling.
4. integrations
2. Easy to get started with and experiment.
3. Hybrid nature allows for secure data handling.
4. integrations
What do you dislike about the product?
1. Two many ways to do things
2. Too frequent changes to API
3. Documentation not consistent
4. Hard to search in documentation
5. No best practices
6. Complicated to deploy
2. Too frequent changes to API
3. Documentation not consistent
4. Hard to search in documentation
5. No best practices
6. Complicated to deploy
What problems is the product solving and how is that benefiting you?
we use prefect to orchestrate ETL processes. extract data with web scrapers, doing some preliminary cleaning and loading them into a warehouse. we use prefect because it's easy to use locally
Powerful flow management with a learning curve
What do you like best about the product?
Once you get the hang of Prefect, it genuinely "just works". It offers reliability and seamless operation, which is exactly what one would expect from a flow management tool.
Even for our simpler flows, the capability to automate retries and the visibility it provides into the process is a significant advantage. This feature not only ensures that our operations are efficient but also helps in pinpointing and rectifying issues effectively.
Even for our simpler flows, the capability to automate retries and the visibility it provides into the process is a significant advantage. This feature not only ensures that our operations are efficient but also helps in pinpointing and rectifying issues effectively.
What do you dislike about the product?
As powerful and comprehensive as Prefect is, it comes with a rather steep learning curve. New users might find it overwhelming due to the multitude of configuration options available.
While the platform is robust, it was disappointing to find that the self-hosted version lacks the ability to send mails.
While the platform is robust, it was disappointing to find that the self-hosted version lacks the ability to send mails.
What problems is the product solving and how is that benefiting you?
It helps us manage ETL and scheduled jobs, knowing that we have visibility on errors and built-in retries. Handling credentials in a much smarter way than I could imagine doing with cron/bash
Great for ETL and DataScience
What do you like best about the product?
I like that the product is a open source code and that they provide you with a service (Cloud) that solves all the borring stuff like IAM /RBACfor you. The flows and task python apis are great. Simple to understand for data scientist. One of the best platforms for ETL
What do you dislike about the product?
Some of the concepts are quite complex (Infrastructure block) and the documentation is not explaining them well. YOu can then find official Prefect YT videos that do better. Some of the solutions are a bit lacky/sloppy once you really use them. For example Prefect AWS worker that spawns ECS tasks will do that in a way that it triggers AWS API rate limiting.
What problems is the product solving and how is that benefiting you?
UI representations of work flows that are split into smaller tasks. We use it to manage data science workloads. The UI is nice. It helps us scale the capacity of the data that we can process.
Great tool to start quick and scale later
What do you like best about the product?
Easy to get started on a single machine and manage complex data processess without investment into cloud and big teams
What do you dislike about the product?
Still lacking task dependency visualisation graph
What problems is the product solving and how is that benefiting you?
It helps manage multuple data processing jobs with complex dependency that can be executed at destibuted infrastracture
I am a Data Engineer working in CloudFactory right now. I started my career using Prefect.
What do you like best about the product?
I started my career using Prefect so, Airflow became second orchestration tool I knew about. Prefect provides the flexible architecture to orchestrate our flow.
What do you dislike about the product?
The fact that Prefect 2 doesn't provide us the power to generate DAG. The visualization of the flow was helpful to us.
What problems is the product solving and how is that benefiting you?
It has helped us eliminate some SaaS products that we used for ETL purpose and benifit us reducing the cost of using unnecessary ETL tool. More people are making flows in Prefect now and it's free to create a flow.
Simple, powerful, easy to use locally and to deploy anywhere. Prefect is a must
What do you like best about the product?
Its simplicity to use compared to other dinosaures of orchestration. It just works everywhere with very little effort: on my laptop when developing, anywhere in the cloud
What do you dislike about the product?
Still struggling a bit on how to manage all the secrets I have stored as Blocks on my local setup, especially in case I miss internet.
What problems is the product solving and how is that benefiting you?
- Validation of my scheduled data pipelines
- increase robustness of my data pipelines
- increase scalability of their executions
- increase robustness of my data pipelines
- increase scalability of their executions
Prefect is awesome
What do you like best about the product?
1. Prefect has an incredible community around it.
2. They are dedicated to improving the product with helpful features and regular updates.
2. They are dedicated to improving the product with helpful features and regular updates.
What do you dislike about the product?
I can't really think of anything bad about it :)
What problems is the product solving and how is that benefiting you?
1. Workflow orchestration.
2. Visibility and alerts on long-running pipelines and tasks.
3. Logging.
4. Creating SLAs
2. Visibility and alerts on long-running pipelines and tasks.
3. Logging.
4. Creating SLAs
Overall good
What do you like best about the product?
Being able to write a flow just like a python script and then have it run as a job in a kubernetes cluster. Pydantic parameter validation is nice too.
What do you dislike about the product?
Upgrading from Prefect 1 to 2 was a lot of work on the infra side, and the new UI is a bit unintuitive. Onboarding a new user and getting them to understand the distinction between flows and deployments, and find what they're looking for in the UI wasn't straight forward.
There doesn't seem to be any way to stream flow run logs from the CLI which is annoying because we have flows that are triggered from a CI/CD pipeline and we want their execution to be blocking. I had to write a custom script to poll the API for flow run states.
We're currently experiencing intermittent issues with flow runs temporarily switching into a Failed state and then back into Running. So far have been unable to consistently reproduce or debug, but it breaks our integration tests regularly.
We're running flows in our AKS cluster with Dapr sidecars so that they can access databases and message queues. We've had issues configuring the sidecar to shut down properly at the end of a run, or when a run fails. I think this might be more of a Kubernetes issue than a Prefect one though.
There doesn't seem to be any way to stream flow run logs from the CLI which is annoying because we have flows that are triggered from a CI/CD pipeline and we want their execution to be blocking. I had to write a custom script to poll the API for flow run states.
We're currently experiencing intermittent issues with flow runs temporarily switching into a Failed state and then back into Running. So far have been unable to consistently reproduce or debug, but it breaks our integration tests regularly.
We're running flows in our AKS cluster with Dapr sidecars so that they can access databases and message queues. We've had issues configuring the sidecar to shut down properly at the end of a run, or when a run fails. I think this might be more of a Kubernetes issue than a Prefect one though.
What problems is the product solving and how is that benefiting you?
We're using prefect to orchestrate customer-triggered machine learning training and deployment workflows on an AutoML platform. It allows us to run everything as a job in our cluster rather than chaining together serverless functions or relying on an enterprise ML platform that doesn't quite fit our use case (which they never quite do).
Prefect is very good tool for data pipelines
What do you like best about the product?
With Prefect tests are first-class citizens and you can run your prefect flows in the terminal.
What do you dislike about the product?
Limited support with third-party libraries.
What problems is the product solving and how is that benefiting you?
Testable workflows and task orchestration.
showing 81 - 90