SimpleDB?

[davidpelaez]

Fred,

could you tell me why you chose to use SimpleDB. I was looking in depth at the aws flow framework and it has way to many bad design decisions on it, so I came back to see how to improve some thing in SimplerWorkflow and I found SimpleDB in some parts of the code and I don't know why they're needed. It seem it's to save some tasks information shared by distributed systems, so that one component's activity can jump to the next one without going to the decider?

Also, I'm seeing up to 5s for a simple HelloWorld with occasional triggers being skipper, any ideas where to start looking at this possible 'skips'?

[fredjean]

There are some attributes of an execution that I needed to hold through out. They do not fit neatly into the attributes allowed by SWF. SimpleDB was an easy place to put them. Most of them have to do with what to do next with the default decider that comes with SimplerWorkflow.

I am open to suggestions if there are better options.

I'm not sure what you mean by triggers being skipped. Could you provide an example?

[davidpelaez]

I see. Maybe using execution contexts and markers would make sense? It really depends on the exact information you need to keep. Maybe passing everything in a specific input/result format, like a series of conventions for those messages. I'm working on a simple adapter of AWS::SWF exactly like we want it to work and it's stateless, I'll drop you an e-mail when it's ready.