If AWS Step Functions keeps adding more integrations, it would be even better. Otherwise, the UI is great, the functionality is great, and everything is great. AWS Step Functions already has many integrations, but adding more is always good for enterprises.
The solution's pricing could be cheaper. It is cheaper than Airflow. We cannot directly pass the parameters of any SQL, emails. It is a simple state, but if they provide any coding platform inside, we need to make it more dynamic instead of drag and drop.
Senior Software Engineer at a tech services company with 11-50 employees
Real User
Top 20
2024-01-29T18:52:00Z
Jan 29, 2024
There could be better integration with IDEs, such as more seamless access to credentials without needing daily updates. Additionally, it would be helpful to have better visibility into Step Functions, such as being able to view parallel executions within the same Step machine. Improved profiling and logging features would also enhance the management of processes. The interface can sometimes feel limited, as we're unable to see what AWS is running behind the scenes. Having a desktop option might provide more detailed information, especially for teams like ours that need to validate multiple sub-functions concurrently. It would be beneficial to see these functions running in parallel for performance validation purposes.
In terms of improvement, I would like to see more data transformation features in Amazon Step Functions, like additional operators and logic, to enhance its capabilities in handling and transforming data during workflows.
Solution Architect at a comms service provider with 11-50 employees
Real User
Top 10
2023-09-14T11:53:33Z
Sep 14, 2023
It wasn't easy to understand the licensing model. It's like if you use just a little, it's cheap, but it becomes more expensive as you use more. It's like a hook that ties you inside the Amazon ecosystem. So, it creates a dependency. I don't like it because it creates a dependency, like Microsoft or other players who want you to stay within their ecosystem as much as possible.
The solution has a data limit of 256 KB which means you can only pass under 256 KB of data to a state machine and between its state transitions. This can be improved.
It is hard to coordinate the declaratory language, especially when you have it embedded. Furthermore, the limits are not to be controlled, and having a limit of 256 KB for the data could be much better.
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...
It is difficult to suggest improvements at the moment. No critical issues or pain points come to mind immediately.
If AWS Step Functions keeps adding more integrations, it would be even better. Otherwise, the UI is great, the functionality is great, and everything is great. AWS Step Functions already has many integrations, but adding more is always good for enterprises.
The solution's pricing could be cheaper. It is cheaper than Airflow. We cannot directly pass the parameters of any SQL, emails. It is a simple state, but if they provide any coding platform inside, we need to make it more dynamic instead of drag and drop.
There could be better integration with IDEs, such as more seamless access to credentials without needing daily updates. Additionally, it would be helpful to have better visibility into Step Functions, such as being able to view parallel executions within the same Step machine. Improved profiling and logging features would also enhance the management of processes. The interface can sometimes feel limited, as we're unable to see what AWS is running behind the scenes. Having a desktop option might provide more detailed information, especially for teams like ours that need to validate multiple sub-functions concurrently. It would be beneficial to see these functions running in parallel for performance validation purposes.
In terms of improvement, I would like to see more data transformation features in Amazon Step Functions, like additional operators and logic, to enhance its capabilities in handling and transforming data during workflows.
It wasn't easy to understand the licensing model. It's like if you use just a little, it's cheap, but it becomes more expensive as you use more. It's like a hook that ties you inside the Amazon ecosystem. So, it creates a dependency. I don't like it because it creates a dependency, like Microsoft or other players who want you to stay within their ecosystem as much as possible.
The pricing of the solution can be improved.
The solution has a data limit of 256 KB which means you can only pass under 256 KB of data to a state machine and between its state transitions. This can be improved.
It is hard to coordinate the declaratory language, especially when you have it embedded. Furthermore, the limits are not to be controlled, and having a limit of 256 KB for the data could be much better.