Even the most simple service is more complicated than it looks. As it grows, it increases the number of elements that make it up. Once the service is grown up, many elements mature and become specialised for their particular job in the service. It doesn’t matter if the service is digital or analog.
This friday at reclamador we are going to try to embrace such service complexity from a technology perspective. Both designers and engineers, organized into teams, are going to analyze the different pieces of the puzzle, trying to get the whole picture and sharing it with short talks.
There are a bunch of layers on that technology perspective, each one of them could be broken down into smaller layers too. So, it’s better to guide the first steps from top to bottom. We are going to rely on our code repositories, connecting the points to infraestructure.
Metaphors, people and plants.
George Lakoff and Mark Johnson gave us many proofs that we, people, use metaphors every time we speak. Both Metaphors we live by (Lakoff & Johnson) and More than cool reason. A field guide to poetic metaphor (Lakoff & Turner) are likely the top best-selling books, showing us not only that metaphors affect our communication, but actually structure our thinking.
One of these conventional metaphors is people are plants.
In this metaphor, people are viewed as plants with respect to the life cycle — more precisely, they are viewed as that part of the plant that burgeons and then winthers or declines, such as leaves, flowers, and fruit, though sometimes the whole plant is viewed as burgeoning and then declining, as with grass or wheat. (Lakoff and Turner, 6)
That metaphor may help to understand the technology arquitecture of a digital service. Let’s see!