I would have preferred if some of the full comedic ones were toned down because this has some use. The amount of AWS services is hard to keep track of, especial

I would have preferred if some of the full comedic ones were toned down because this has some use. The amount of AWS services is hard to keep track of, especially considering when they have a bunch of slightly different solutions to a similar problem, is quite staggering. E.g. I want to deploy my code - should I use Ops Works, Pipelines, CodeDeploy, Ec2 Container Service, Elastic Beanstalk, Elastic Breadstick, CodePizza, blah blah blah? > SWF -> Amazon EC2 Queue Use this to Build a service of "deciders" and "workers" on top of EC2 to accomplish a set task. Unlike SQS - logic is setup inside the service to determine how and what should happen. I do not find this one to be that helpful, as "deciders" and "workers" doesn't make sense in this context. Logic isn't encapsulated inside of SWF, and the workers do not need to be hosted on EC2. SWF basically tracks workflow and activity versions, and is essentially a state management and work distribution system. It distributes out tasks to polling workers based on what the workers are polling, and what state is currently in SWF. I think a (possibly) better name/use this to would be Amazon Task Orchestrator/Schedule and run jobs that do a bunch of things in order that can be distributed, where you want to run the workers on either EC2 or your own machines. Ok, maybe not too much better, but I think it shows the use case a little bit better.