The solution is expensive. It is worth the money. AWS offers event bridges. Another service triggers any job and provides event buses to fasten parameters. For data lakes, event buses are very useful for obtaining keys for each file. Compared to Step Functions, the pricing is much higher, especially when moving from static infrastructure machines. The pricing model should be based on OpenEdge plans.
Solution Architect at a comms service provider with 11-50 employees
Real User
Top 10
2023-09-14T11:53:33Z
Sep 14, 2023
We went for the Step Functions service. The pricing for Step Functions was quite convoluted and difficult to understand due to the numerous small factors involved, such as data transfers and limitations on runtimes. Additionally, replacing existing Step Functions tasks was not straightforward. As a result, we opted for a solution that provided clear and understandable outputs, allowing us to effectively monitor and manage our workflows. For we went for Lambda function for more decent output and to see what was going on. It was more Amazon API for infrastructure. We were trying some EFS-related stuff and some proprietary APIs from Amazon. So, pricing depends on what I am doing. If you're consuming two or three things a day, it's fine. It's cheap. But then there's no price control because Amazon is about, "Let me help you consume as much as possible," so then I can be, like, hell at the end of the month.
I am unsure about the price, but I remember they were charging 0.25 cents for our conversions. For example, you're always charged based on the number of requests in your workflow and the duration. For example, it could be $1 per 1 million requests.
AWS Step Functions enables orchestration of complex workflows, parallel task execution, and seamless integration with AWS services, simplifying ETL automation and data pipeline management.
With AWS Step Functions, developers streamline task automation and ensure smooth microservices orchestration. It simplifies development and manages interdependencies, validates data, and integrates AWS services for cost-effective workflows. It offers a user-friendly graphical interface for creating...
The solution is expensive. It is worth the money. AWS offers event bridges. Another service triggers any job and provides event buses to fasten parameters. For data lakes, event buses are very useful for obtaining keys for each file. Compared to Step Functions, the pricing is much higher, especially when moving from static infrastructure machines. The pricing model should be based on OpenEdge plans.
The pricing for Amazon Step Functions is flexible and depends on the usage of the product. It is cheaper than Azure Workflow.
We went for the Step Functions service. The pricing for Step Functions was quite convoluted and difficult to understand due to the numerous small factors involved, such as data transfers and limitations on runtimes. Additionally, replacing existing Step Functions tasks was not straightforward. As a result, we opted for a solution that provided clear and understandable outputs, allowing us to effectively monitor and manage our workflows. For we went for Lambda function for more decent output and to see what was going on. It was more Amazon API for infrastructure. We were trying some EFS-related stuff and some proprietary APIs from Amazon. So, pricing depends on what I am doing. If you're consuming two or three things a day, it's fine. It's cheap. But then there's no price control because Amazon is about, "Let me help you consume as much as possible," so then I can be, like, hell at the end of the month.
The solution's price is reasonable.
I am unsure about the price, but I remember they were charging 0.25 cents for our conversions. For example, you're always charged based on the number of requests in your workflow and the duration. For example, it could be $1 per 1 million requests.