Pirates are known for drawing treasure maps to their most prized possession. These documents detail the decisions pirates made in order to hide and find their chests of gold. As software engineers, programmers, and architects we need to treat software implementations much like our treasure chest.
There are many ways to sabotage a project. Recognizing them is the first crucial step to counter them. In this brief handbook I will present a number of ways of sabotage that I have encountered in various projects. This post is the saboteur’s handbook. The countermeasures will be saved for another post.
In this talk we describe the limitations of a monolithic architecture. You will learn how to use the scale cube to decompose your application into a set of narrowly focused, independently deployable back-end services and an HTML 5 client.
For some time I’ve been trying to understand the different combinations of CAP theorem system properties and what do they mean in practice; having some time at various airports I caught up on reading, and here’s what I came up with.