Take a look please at this simple kid toy what just my 2 years old son enjoy of. I thought it is simple kid task to put oranges to oranges and carrots to carrots. I thought this way until I came at ... AWS. Yes, my daily routine is to design and implement software which just puts bananas to bananas, carrots to carrots and limes to limes. Software is smart and perform its job carefully and in exact way - no bananas will be mixed with oranges, no single carrot will be missed or forgotten, no in any magic way one tomato turns into two. You may think then, what the rubbish this guy is talking about. And you are right, until, one small nuance comes to the picture. The amount of fruits to process is ~250000000 per/second or 900000000000 per/hour and just guess further :)Let's spice this picture with requirements - no single fruit is allowed to be lost, no fruit is allowed to be shown up at end result twice or more, indeed no-one likes her delivery failed, or double bill at end of month, right? In addition, the processing time is limited, hence if you are given just one hour to do work, there is no excuse if you failed due too 'some extra fruits arrived'.Is it all? No. Such system(s) must be able operate 24/7 and be prepared and ready to growing business. Today it can process 250*10^6 fruits, next year amount of fruits can be doubled and you must sustain to it. And finally, what if something goes wrong and one banana was lost or orange delivered to wrong destination? How fast you will be able find lost banana from the billions of other bananas and reprocess? Even worse scenario, what if somebody by mistake cut underground cable and your system is out of the service for X hours? Will it recover after that at all? Yes this is something what is on my shoulders as well. In one word this is BigData, this is AWS.Are you still thinking this simple kid toy is that simple indeed? :)