Amazon SWF vs Stream: What are the differences?

Developers describe Amazon SWF as "Automate the coordination, auditing, and scaling of applications across multiple machines". Amazon Simple Workflow allows you to structure the various processing steps in an application that runs across one or more machines as a set of “tasks.” Amazon SWF manages dependencies between the tasks, schedules the tasks for execution, and runs any logic that needs to be executed in parallel. The service also stores the tasks, reliably dispatches them to application components, tracks their progress, and keeps their latest state. On the other hand, Stream is detailed as "Build scalable feeds, activity streams & chat in a few hours instead of months". Stream allows you to build scalable feeds, activity streams, and chat. Stream’s simple, yet powerful API’s and SDKs are used by some of the largest and most popular applications for feeds and chat. SDKs available for most popular languages.

Amazon SWF and Stream are primarily classified as "Cloud Task Management" and "Activity Feeds as a Service" tools respectively.

Some of the features offered by Amazon SWF are:

• Maintaining application state
• Tracking workflow executions and logging their progress
• Holding and dispatching tasks

On the other hand, Stream provides the following key features:

• Activity, Notification & Personalized Feeds
• Real-Time Chat
• Multi-Region Support

StackShare, Product Hunt, and Bunch are some of the popular companies that use Stream, whereas Amazon SWF is used by Amazon, Better, and MaaS Global. Stream has a broader approval, being mentioned in 51 company stacks & 92 developers stacks; compared to Amazon SWF, which is listed in 13 company stacks and 19 developer stacks.