Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Quick Introduction to Software Architecture

DZone 's Guide to

Quick Introduction to Software Architecture

If you're interested in becoming a software architect, read on to get a quick glimpse into a day in the life.

· Microservices Zone ·
Free Resource

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

You Will Learn

  • What software architecture is.
  • What software architects do.
  • Some of the important decisions software architects make.
  • Why we need software architecture.

This is the first article in the following series of articles on software architecture:

What Software Architecture Is

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

Software architecture

This application architecture has multiple microservices: Microservice 1, Microservice 2, and Microservice 3. There are a set of common components that handle functionalities 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 needs to be three microservices, and assigned specific responsibilities 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 important decisions. It involves starting 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 that other applications need from a particular application.
  • What are the common functionalities that can be identified in the system? How do you design them as components, and how do you integrate them with the other applications/components?
  • What services of the system need to be abstracted into the common infrastructure? How do you decide to make these services available to the rest of the system?

Why Do We Need Software Architecture?

A few decades ago, software programs 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 is driven by a cluster of hundreds of systems.
  • Device Explosion: Years ago, 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 a lot more! 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.

Topics:
microservices ,microservices architecture ,software architecture

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}