Label: architecture_principle

All content with label architecture_principle.
Related Labels: architecture

Page: A software architect is a part-time Archeologist (KM: Software Architecture)
Title says is all, really :) http://97things.neartime.net/forum/usercontributedaxioms/communityaxiomscon tributenewaxioms/3209?page=11
Page: A software architect is a part-time Archeologist (KM: Service Oriented Architecture (SOA))
Title says is all, really :) http://97things.neartime.net/forum/usercontributedaxioms/communityaxiomscon tributenewaxioms/3209?page=11
Page: Availability Over Consistency (KM: Service Oriented Architecture (SOA))
Quote "I am not aware of any information from Google about the cause of their outage but, again, we as an industry are still learning how to keep ever more complex applications and services available. The article cited above, expresses the dismay ...
Page: Build to excel, buy to support (KM: Service Oriented Architecture (SOA))
from HSBC Center of Excellence... will find wording and reference soon
Page: Clear and consistent responsibility power all great architectures (KM: Software Architecture)
Clear and consistent responsibility power all great architectures As all architects learn, architecture is all about balancing tradeoffs, but there is one trade off which should never be broken; namely the clear and consistent responsibility throughout your system or system ...
Other labels: architecture
Page: It is all about the data (KM: Service Oriented Architecture (SOA))
http://97things.neartime.net/forum/usercontributedaxioms/communityaxiomscon tributenewaxioms/3209
Page: Scalability Axiom no 1 - Utmost scalability (KM: Service Oriented Architecture (SOA))
Tight data and function at the usage edge is the utmost of all scalability options. Latency Latency is Everywhere and it Costs You Sales How to Crush it http://highscalability.com/latencyeverywhereanditcostsyousaleshowcrushit Latency is Everywhere and it Costs You Sales How to Crush it My Take http ...
Page: Scalability Axiom no 2 - CAP theorem (KM: Service Oriented Architecture (SOA))
What goals might you want from a shareddata system? Strong Consistency: all clients see the same view, even in presence of updates High Availability: all clients can find some replica of the data, even in the presence of failures ...
Page: Scalability Axiom no 3 - Divide and Conquer (KM: Service Oriented Architecture (SOA))
Since simplicity rules http://labs.google.com/papers/mapreduce.html an all massive scalability strategies, we need to ensure that we are heavy on the divide and conquer bandwagon when building scalable solutions. !mshn69l.jpg
Page: Software Orthogonality (KM: Software Architecture)
related to the DRY principle and Totto's axiom on responsibility Clear and consistent responsibility power all great architectures. The concept is explained well in The Pragmatic Programmer http://www.pragprog.com/thepragmaticprogrammer: In computing, the term has come to signify a kind of independence or decoupling. Two ...