Microservices – Old dog … new tricks

Software architecture is founded on key principles. Principles (made up of name, statement, rationale and implications) are then translated or mapped into key architectural patterns and qualified amongst a number of criteria (robustness, completeness, consistency and stableness to name a few) to justify its quality.

A lot of attention and hype is on the use of microservices architecturally and its implementation with more cutting edge technologies is becoming more and more popular with modern software stacks. Why is this appealing now? Have we not come across this before but failed to give it full attention cause we couldn’t realise its benefit.
Continue reading

Outcome based Innovation

Getting to what customers really want

Literal voice of the customer does not translate into meaningful inputs. Customer-driven movement has failed to produce the desired results because asking the customer what he wants solicits wrong inputs.

Companies gather requirements however they do this without ever really understanding what types of inputs they need to obtain from customers. Neither does the customer. Customers offer their requirements in a language that is convenient to them but unfortunately not convenient for the creation of breakthrough products.

Continue reading