Flowers @ Jinendram

Lantana (Yellow), Lantana (Red/Yellow), Sevanti AKA Chrysanthemum, Nastritium(Yellow), Rose(Red/Pink/Orange),

Badminton @ MKM

Malhar Krida Mandal (MKM)

Many thanks to Bargal sir for getting this club integrated, one of the finest one in Indore & being an inspiration. 
Your commitment towards fitness and making others aware of its importance is really valuable.

The Croods

For last one week Aryaa, Shruti & me are watching 'The Croods' in parts. Aryaa started playing characters from movie, see herself as 'Eep' & me as 'Grug', though I don't have any resemblance. Daily a 20 minute 'The Croods' show has went very well. Yesterday the last part of movie was amazing, when Croods were about to reach their destination, an earthquake opens a deep ravine in their path. Grug throws each of the family member across the gap and reconciles with Eep while creating the first hug with her. This moment touched me & watching this with Aryaa turned me a bit emotional. Grug then throws her across the ravine and was left behind. Left apart Grug was sad and missing his family and was about to give a last try to patch himself with the departed. In that effort he was lost in the volcanic lava and everyone assumed him dead. Now this Aryaa's character game turned me down, as if I am Grug, I don't wanted to depart and left alone. I was yelling why has director done this, and not sending a right message. And of a sudden, dramatically Grug appears from the a huge lump of smoke, both me and Aryaa jumped up high and celebrated the Croods togetherness.

30DC #1 Reading

I was always fond of reading technology, programming languages, new programming paradigm, best practices... But when it comes to reading novel, literature, religion, sci-fi etc. I couldn't keep my spirits high. I don't know WHY, but this is the case. I am aware of importance of reading, it immensely impacts ones way of seeing the world and life. But reading has been a difficult job for me. I tried different shortcuts to it, following Ted & listening audio books but I cannot find varieties in contents in this mode.
Yesterday, I heard Matt Cutt on his '30 day challenges' theory. Immediately after that, I thought of, why not give it a try? Reading has always been difficult task to me, lets take this as first 30 day challenge.

'Reading (something other than technology) is my #1 30DC'

Guidelines to Cloudify

#Loose coupling mantra

When designing an application for cloud, consider design with decoupled components. This can be ensured by minimizing the assumptions that one component makes about another while exchanging message from one to another. Since components are loose they concentrate more on individual features, these components can be tied together using a reliable & highly available infrastructure viz. message oriented middleware or datastore.

#Chatter will shatter

Network in cloud is unreliable when compared to one in hosted environment. Chatty APIs works well in LAN but fall upside down in cloud environment. Relying on chatty protocol can dramatically drop in performance of application. Below are a few important consideration to get this minimized:

1. Minimize round trips: Closely inspect application APIs to identify if calls can be clubbed together in one. Instead of designing fine grain APIs rely on coarse grain ones, these can be practices by including aggregates over entities as return parameter in interface definition of endpoints.
2. Service oriented design: Another reason why protocols become chatty, programmers thinks exposed APIs in terms of fine-grained distributed objects rather coarser-grained services.
3. Design Async-Ackless APIs
4. Consider thick client based design to hand off responsibility on clients.

#Graceful degradation

"Everything fails all the time" keep this phrase behind the mind while thinking of designing application for cloud. Avoid SPOF (single point of failure) is the key to achieve this, while designing consider assume nothing and consider failures as 'first class citizen' of the service. Failures in the system generally cascades and there by has an effect on all the components of the application.

#Statelessness with REST

In an application with each component running on different compute node, the chance of occurrence of failure increases when they are deployed on cloud, reason being cloud nodes have an inherent behavior of a low availability. Also, to meet the demand there are needs for horizontal scaling in and out. Thereby component has to be designed in a way that they do not contain any internal state, but completely rely on external persistent storage. Since the component instances do not have an internal state, no data is lost if an instance fails. Such a setup also significantly increases the capability of the componentized application to scale-out, because multiple components can share a common data store and thus act as if they all had the same common internal state. Adding and removal of components, part of scaling operations, is also simplified. However, the scalability of the central data store becomes the major challenge when using stateless components.
REST based architecture is an absolute fit per above discussion. REST consider transmitting the state each time component is accessed.

Trekking Ralamandal

View from Ralamandal peak

Holkar's Shikargah @ Ralamandal 

Kashid-Lonavala-Mumbai

On the way to Elephanta Caves from Gateway

Leisure at Dukes Retreat

Kashid Beach

Mumbai - Pune Express way from Dukes