Quick Introduction To Software Architecture - What, Why and How?


Good Software Architecture is essential to building great software. What is Software Architecture all about?

You will learn

  • What Is Software Architecture?
  • What do Software Architects do?
  • What are some of the important decisions software architects make?
  • Why do we need Software Architecture?

This is the first article in the following series of articles on Software Architecture :

What Is Software Architecture?

To understand what software architecture is all about, let us look at the following diagram:

image info

This application architecture has multiple microservices - Microservice1, Microservice2 and Microservice3. There are a set of common components that handle functionality such as security, logging, archetype creation, and the like. You also have components to handle common infrastructure concerns/ These include an API Gateway, a naming server, and a centralized logging system.

Answering Some Important Questions

  • Who made the decision that there need to be three microservices, and assigned specific responsibility to each one of them?
  • Who decided that certain functionalities of the application need to be handled by common components?
  • Who designed the mode of interaction between the microservices and the common components?
  • Who classifies the common infrastructure components, and designs their interfaces with each of the microservices?

Architecture Is All About Making Decisions

Designing an application architecture is all about making such important decisions. It involves staring from a level that involves these decisions:

  • What are the applications? What are their individual boundaries?
  • What are the interactions between the individual applications? In other words, the services of which other applications are needed by a particular application?
  • What are the common functionalities that can be identified in the system? How do you design them as components, and how to interface them with the other applications/components?
  • What services of the system need to be abstracted into the common infrastructure? How do you decide on how to make these services available to the rest of the system?

Why Do We Need Software Architecture?

A few decades earlier, software programs built were small and simple. However, things have changed dramatically.

Software has become quite complex, with the advent of cloud computing, microservices, big data, and what not.

Factors that have contributed to this complexity include:

  • Distributed Systems: Even a single web page that you may view online, might be driven by a cluster of hundreds of systems.
  • Device Explosion: Earlier, devices owned by users were limited to a single PC or laptop per person. Nowadays, you have a choice of mobile phones, tablets, IoT devices, and what not! Software that needs to run on more than one device, will be complex
  • Enormous Scale: The load or the scale of users that an enterprise application needs to support has also gone up significantly
  • Technology Evolution: The languages, frameworks, tools and processes used in software development continuously undergo change, and applications need to keep pace with them
  • Non Functional Requirements: It is very important to ensure that all non functional requirements are adhered to when designing your applications.

The challenge in such a dynamic scenario, is to develop applications that work today, and adapt to stay relevant tomorrow. This is the puzzle that architects try to solve.

That’s also the reason why you need to pay attention to the architecture, when you develop applications.

Do check out our video on the same topic:

image info image info

Summary

Software architecture is all about making decisions. It mainly involves identifying applications and components, and clearly demarcating their boundaries.

10 Step Quick Introductions to Frameworks

Related Posts

Spring Boot Tutorials for Beginners

At in28Minutes, we are creating a number of tutorials with videos, articles & courses on Spring Boot for Beginners and Experienced Developers. This resources will help you learn and gain expertise at Spring Boot.

Spring and Spring Boot Video Tutorials for Beginners

At in28Minutes, we are creating a number of tutorials with videos, articles & courses on Spring Boot for Beginners and Experienced Developers. Here's a list of video tutorials and courses for you

Creating Spring Boot and Vue JS CRUD Full Stack Application with Maven

This guide helps you create a full stack application with all the CRUD (Create, Read, Update and Delete) features using Vue JS as Frontend framework and Spring Boot as the backend REST API. We use Maven as the build tool.

Software Design - Separation Of Concerns - with examples

Software architects and programmers love having Seperation of Concerns. What is it? Why is it important? Let's get started.

Object Oriented Software Design - Solid Principles - with examples

Software design is typically complex. Object oriented design takes it to the next level. There are a number of design patterns and other stuff to be aware of. Can we make things simple? What are the goals to aim for when you are doing object oriented design? SOLID Principles is a great starting point for Object Oriented Design.

Software Design - Open Closed Principle - with examples

Open Closed Principle is one of the SOLID Principles. You want your code to be easily extended. How do you achieve it with minimum fuss? Let's get started.

Software Design - What is Dependency Inversion Principle?

Dependency Inversion Principle is one of the important SOLID Principles. Dependency Inversion Principle is implemented by one of the most popular Java frameworks - Spring. What is it all about? How does it help you design good applications?

Introduction to Four Principles Of Simple Design

With agile and extreme programming, the focus is on keeping your design simple. How do you keep your design simple? How do you decide whether your code is good enough?

Software Design - Single Responsibility Principle - with examples

For me, Single Responsibility Principle is the most important design principle. What is Single Responsibility Principle? How do you use it? How does it help with making your software better? Let's get started.

What is an In Memory Database?

In this article, we understand what the term "In-Memory Database" actually means. We see what scenarios they can be used, and why they are important.