dognewtricks
Image

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

reactive-traits
Image

Reactive applications and an introduction to event driven architecture

The release of the Reactive Manifesto in 2013 has popularized the term “reactive applications”. The purpose of the manifesto is to describe a new approach to systems architecture and the key characteristics that these systems will need to implement.  Why would we need a new approach to systems? A few years ago a large application would typically consist of tens of servers, response times of a few seconds, gigabytes of data and downtime was a generally accepted norm. Today this has changed dramatically. Applications now span hundreds of servers, are dependent on many other systems, response times need to typically be sub second, terabytes of data and 100% up-time. This is further compounded by the fact that organisations are becoming more transparent by allowing customers direct views of internal processes via the web and mobile devices.  The organizations that can adapt to this new playing field are the ones that can set themselves up for success tomorrow.

The Reactive manifesto takes many patterns and concepts and packages them together to form a cohesive set of terms and concepts. These together are termed reactive applications. Version one of the reactive manifesto addresses four design characteristics of responsive applications.

Continue reading

Bugs in the source code
Image

Utopia Enterprises – a division of Norris Ltd

Written by Abdur-Rahman Patel

I have recently come across an organisation where all their software, be it COTS or in-house built are free of bugs. Their LAN has quadruple redundancy, it never fails them, not even a single node. They guarantee zero percent downtime on every piece of hardware and software within the organisation and I’m not talking mission critical ones only. They also guarantee zero percent downtime on all external partner systems. Data is always perfectly in sync and up to date across the enterprise. When implementing, their ‘super technicians’ have a 100% record for going into production with the correct configuration across all components. Basically, they never make mistakes. Timeout, LAN latency, slow response? Not in their vocabulary.

Continue reading

Agile
Image

Numbered List of Agile Challenges

In my previous post(Corporate Agile Challenges Demystified), I expressed challenges that large organizations face trying to get Agile Projects off the ground. I eluded to several scenarios based on repetitive patterns I have seen whilst consulting, collaborating and observing.  Below, I unpack the reason South African(not limited to) organizations struggle with Agile Projects in, no order of importance.

PS: Don’t even start a project if you have not even seen The Agile Maifesto(http://agilemanifesto.org/). You may not be able to tick all the boxes at inception but at least understand all of them, adopt most of them and have a plan to address all of them in the future.

Continue reading

socket