For half a century, it has stood on the edge of the Ginza district, one of Tokyo’s most curious, baffling and brilliant buildings. A 13-storey assembly of 140 steel cubes bolted to two central towers, it looks like the world’s biggest Lego kit.
It was built by a visionary architect and its tiny 8ft by 13ft apartments have been home to writers, artists and musicians. But in a matter of days Nakagin Capsule Tower will be no more.
Have you ever been in a meeting where someone is trying to explain how a software system works?
I was having a conversation with a relatively new solutions architect who was trying to describe a system they had come up with. It had about eight different components to it and they all interacted with each other in multiple ways.
They were explaining the solution using hand gestures and a lot of “and this piece communicates with this one by…”
I understood the words coming out of their mouth, but they didn’t make sense strung together.
Words get lost when explaining complex conceptual architecture. I was trying to build a mental model while following a train of thought. I needed a visual.
I needed a diagram.
But not just any diagram. Architecture diagrams are not a “one size fits all” solution.
We’ve discussed recently that a significant part of being a solutions architect is effectively communicating your ideas to both technical and non-technical audiences.
Your diagrams must take that into consideration. If you want to get your idea across to different sets of people, you must make multiple versions of your diagrams.
Today, we are going to talk about the five different types of diagrams you should make depending on five different audiences.
We will take an example from my fake business but real API, Gopher Holes Unlimited, where we add a new gopher into the system to be tracked.
1. The Flow Diagram
The most generic and generally broadest-reaching diagram you can make is the flow diagram. It is a medium- to high-level diagram that shows all the pieces of a workflow.
This diagram illustrates the moving parts in a business process.
The audience for this type of diagram is generally technical. It may be used to pitch an idea to an architecture board or describe how a business process works to a developer.
The major component of the architecture flow diagram is the inclusion of all the moving parts. In the case of our serverless AWS environment, we label each managed service and which ones communicate with each other.
No details on how the pieces interact with each other are described, but the diagram does show the connections. It shows how data flows through the system.
This day and age, you hear everyone talking about going green. Whether you want to admit it or not, at some point, everyone will have to follow with the green movement. This is because at the rate we are going, the earth is simply not sustainable. That means that over the years, we will begin to run out of certain natural resources that are needed for us to survive.
Indeed, that is alarming to some people, which is why there are so many people that focus on the green building today. But what exactly is green building? Let’s take a closer look at what it is, why you should consider it, and what the goals of a green building are. You are sure to find that it is something that you should take part in.