Have you ever looked back on something you did and wondered, "What was I thinking?" For me, it's when I see photos from my teenage years. Every time I go through them, I ask myself, "Why did I choose that hairstyle? Did I really think this was cool?".

The fact is, at that time, it was cool. I liked the hairstyle of my favorite soccer player, and because of that, many kids in my school also had the same hairstyle. Therefore given the information and context I had, I made decisions that made sense. When others see the picture in my absence they might not understand the context because it's in my head.

In summary, some decisions are sensible if you understand the context. Context is KING.

This article explains how to combine various applications to bring value to the client. It starts with a real-world example of a burger business and demonstrates how to use the saga pattern to construct a value stream integrating numerous applications.

Capabilities are the foundation of other important viewpoints and techniques that can be used to move the business forward.

This post highlights how business capabilities can be used in other core domains of business architecture. Furthermore, the post highlights how capabilities can be used in techniques like heat mapping and planning.

In the past 3 months my curiosity drove me to business architecture. I read multiple articles and I landed in rabbit hole which increased my curiosity. During the process, I discovered multiple frameworks addressing business architecture but I stuck with "Guide to the Business Architecture Body of Knowledge".[#3]. The guide outlines that there are four core elements of business Architecture which includes:

1. Business Capability Map
2. Value Stream map
3. Information map
4. Organisation Map

This post focuses on Business Capability Map. The post defines business capability, business capability map and discusses the benefits of creating a business capability map.

I recently listened to InfoQ podcast where Susanne Kaiser spoke about DDD, Wardley Mapping & Team topologies. Responding to one of the questions she said, “when we are building systems in general, we are faced with challenges of building the right thing and building the thing right.”

I was fascinated by how swapping two words, “wrong” and “right,” makes such a huge difference, and I decided to dig deep.

Introduction​

I have been involved in multiple orchestration vs choreography conversation. Conversation are normally about which one is better. At the end of most conversations, there’s no common ground, all goes down to preference.

One Friday morning on my way to work I listened to Design time coupling in microservices podcast and Chris Richardson touched on this subject. When the host asked him to talk about orchestration and choreography he said “I use those terms in the context of a saga pattern”. That’s when the penny dropped and I thought...this makes sense.

In this post I will define these concepts and explain the relation between saga,orchestration and choreography.

Introduction​

When I was introduced to C4 in 2019 there were few tools that supported it. Today there's multiple and I'll go through few tools in this post.

It is ok to create c4 in a tool of your choice. The most important part of creating C4 diagrams is to follow notation and recommended guidelines.

Introduction​

"Architects ride the Architect Elevator from the penthouse, where the business strategy is set, to the engine room, where the enabling technologies are implemented" ~ Gregor Hohpe

Scenarios​

Scenario 1: Imagine you are at the airport in a foreign country and about to fly to your home country.A stranger sits next to you, greets you and ask you where are you from. What will be your response?

Scenario 2: Imagine you are at the domestic terminal in your home country, and you are about to fly to another city. A stranger greets you and ask you where are you from. What will be your response?

Scenario 3: You are in a coffee shop at local shopping centre and stranger asks you where are you from, what will be your response?

Do you have different answers in the 3 scenarios? If so why?

"One of the undecided problems of software development is deciding what the boundaries of a piece of software is" - Martin Fowler. This is statement is so true, creeps into most of my design conversation.

Photo by goodtherapy.org