Evolution of System Design, Web-Services to Microservices

Evolution of System Design, Web-Services to Microservices

Evolution of System Design, Web-Services to Microservices. We discussed about one of many possible journey for evolution of ‘System Design and Structure’ in search of Nirvana of Independence, i.e. Independence of development, technology, deploy-ability, scalability.

In the previous  article, we discussed one of many possible journeys for the evolution of ‘System Design’ in search of nirvana of Independence, i.e. Independence of development, technology, deploy-ability, scalability, and team structures (autonomous).

If we weave this whole journey so far, it is evident that effort and direction were always to achieve the following goals of System Design:

  • Keep implementation clean, readable so it can be maintained and extended easily — Smaller in Size, SPR, Clear Intent using naming convention, right package/project structure, Reuse code (DRY)
  • Modular Structure, Domain-Driven — Small self-contained unit of code that can be developed independently, by autonomous smaller teams
  • Independently Releasable — Code, Data everything bundled together without cross dependencies
  • Independently scalable & fault-tolerant - Making it easy to scale any specific unit of implementation
  • Freedom of using any technology *& communication protocol *— Technology-neutral interfaces and discovery mechanism, so implementation of individual units can be technology agnostic.

What is Microservice

‘Microservice’, one of the most talked-about panacea for the above goals nowadays.

Let us understand what is Microservice.

  • The name implies that Micro service must be smaller than a small service.
  • And it should be a service.

Service means ‘an act of doing work for someone’.

Which is correct for microservices, similar to any other service-oriented pattern (EJB, Rest, Webservice..).

design-systems system-architecture microservices

Bootstrap 5 Complete Course with Examples

Bootstrap 5 Tutorial - Bootstrap 5 Crash Course for Beginners

Nest.JS Tutorial for Beginners

Hello Vue 3: A First Look at Vue 3 and the Composition API

Building a simple Applications with Vue 3

Deno Crash Course: Explore Deno and Create a full REST API with Deno

How to Build a Real-time Chat App with Deno and WebSockets

Convert HTML to Markdown Online

HTML entity encoder decoder Online

Serverless Vs Microservices Architecture - A Deep Dive

Companies need to be thinking long-term before even starting a software development project. These needs are solved at the level of architecture: business owners want to assure agility, scalability, and performance.

The Service Mesh in the Microservices World - DZone Microservices

In this article, take a look at the service mesh in the microservices world. The software industry has come a long journey and throughout this journey, Software Architecture has evolved a lot. Starting with 1-tier (Single-node), 2-tier (Client/ Server), 3-tier, and Distributed are some of the Software Architectural patterns we saw in this journey.

Introduction to Design Systems for UX/UI Designers

For junior designers - those who have just started studying UX / UI design systems and those who have been working in this field for up to 1-2 years. The main goal of this article is to introduce you to the basic components of system design, to give you a basic introduction to this concept and to revise the material by demonstrating several examples of design systems that are already used by large companies.

Glossary: Design Systems Defined for Developers and Designers

Design systems are interdisciplinary by nature. They are built and consumed by designers and developers, therefore it is important for common terminologies to exist to support the communication between these two disciplines and other related actors.

What Is a Microservice Architecture? Why Is It Important Now?

Microservices are growing as the default architectural design pattern. But why has it become such a point of emphasis? Find out here.