TechEcho

So, getters? We need X, so we call getX(). getX needs A and B, so it calls getA() and getB(). And so on, until getSomething() just reads input. Please correct me if I'm reading this wrong.

AWS SimpleWorkflow (SWF) replay mechanism seems close to this. <a href="http://docs.aws.amazon.com/amazonswf/latest/awsflowguide/awsflow-basics-distributed-execution.html" rel="nofollow">http://docs.aws.amazon.com/amazonswf/latest/awsflowguide/aws...</a>

Our whole platform is built from self-assembling components.<p>But sometimes they have to know about each other :)

I don't understand what problem is being solved here. Is this just an overly convoluted way to describe load balancing?

Can someone recommend a resource for researching scalability solutions like these? Book(s), or video series?

So... Netflix solved SAT?

I'm too old for this.

So, getters? We need X, so we call getX(). getX needs A and B, so it calls getA() and getB(). And so on, until getSomething() just reads input. Please correct me if I'm reading this wrong.

Our whole platform is built from self-assembling components.<p>But sometimes they have to know about each other :)

I don't understand what problem is being solved here. Is this just an overly convoluted way to describe load balancing?

Can someone recommend a resource for researching scalability solutions like these? Book(s), or video series?

So... Netflix solved SAT?

I'm too old for this.

Building Netflix Playback with Self-Assembling Components (2014)

7 comments

Building Netflix Playback with Self-Assembling Components (2014)

7 comments