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.
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.