Simple Workflow Service - Amazon Adding One Enterprise Brick At Time
![Image](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhAr-8lLJdIybQmyC8oW2aYqlWQy5DnkdD13OrdyAUI_aBS2RNthe5nFyEXwQHnYxHDBH8TRJu5ERfaIe4CMXW5uSd7JLYGuVm1YhLjOBtcGqJHkqOOEK-22pMl6gFHIC2bl6ZDG4x9-n4/s400/sws.png)
Yesterday, Amazon announced a new orchestration service called Simple Workflow Service . I would encourage you to read the announcement on Werner's blog where he explains the need, rationale, and architecture. The people I spoke to had mixed reactions. One set of people described this as a great idea and were excited that the developers can now focus on writing domain-specific code as opposed to writing plumbing code to orchestrate their actual code. The other set of people felt that this service creates a new cloud lock-in making it difficult for the developers to switch from one cloud to another as well as being able to interoperate at the orchestration level. I believe this is a brilliant idea for a variety of reasons. Orchestration has always been painful. Ask the developers who have been involved in managing task execution across a cluster that required them to code for load balancing, handling exceptions, restarting hung processes, tracking progress etc. This is not a core c