Microservices: Breaking Down Traditional Application Design

Microservices: Breaking Down Traditional Application Design

Microservices: Breaking Down Traditional Application Design. Organizations around the world have begun breaking down their monolithic architectures into smaller and more manageable components. We broke these down even further with the microservices pattern.

Internationally known author and speaker Mike Amundsen discusses the advantages of having an API-first design.

Over the last 20 years, organizations around the world have begun breaking down their monolithic architectures into smaller and more manageable components. This paved the way for the emergence of the service-oriented architecture (SOA), where applications were broken down into their functional components.

Then, in the last 10 years, we broke these down even further with the microservices pattern, which aimed to address the inherent problems found within monolithic SOAs.

However, that doesn’t mean that monolithic architecture is dead.

According to Mike Amundsen, author of books such as 'Design and Build Great WebAPIs,' and 'Microservice Architecture: Aligning Principles, Practices, and Culture,' a good monolithic system still has its place.

"One of the advantages of a monolithic system is once I get my request or my data into the perimeter of your system, then everything is nearby. The database is local, all the other functions, all the other classes, all the other modules — they're all local. And I don't have to worry a lot about network traffic until I want to give a response back to the client." said Mike during an interview in Coding Over Cocktails, a podcast by TORO Cloud.

Microservices and Loose Coupling

The pros and cons of microservices lie with their very nature – loose coupling.

"With microservices, I can't be sure that all of those tasks I need to do to fulfill your request are living in the same space. They might be on another machine. They might be in another part of the company. They might actually be run by some of the third parties that might be hosted in the cloud by a major vendor. So, now I have to design with the assumption that everything is far away, that everything is actually connected by some network requests and that network requests might even go down." Mike explains.

api microservices soa monolithic

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

Top 10 API Security Threats Every API Team Should Know

Learn what are the most important API security threats engineering leaders should be aware of and steps you can take to prevent them

An API-First Approach For Designing Restful APIs | Hacker Noon

I’ve been working with Restful APIs for some time now and one thing that I love to do is to talk about APIs.

Public ASX100 APIs: The Essential List

The method used for this initial research was to obtain a list of the ASX100 (as of 18 September 2020). Then work through each company looking at the following

What Are Good Traits That Make Great API Product Managers

What is API product management and what can you be doing to be a better API product manager — get aligned with SaaS and enterprise software requirements. This guide lays out what is API product management and some of the things you should be doing to be a good product manager.

54% of Developers Cite Lack of Documentation as the Top Obstacle to Consuming APIs

APIs are perceived as reliable—more than half of respondents stated that APIs do not break, stop working, or materially change specification often enough to matter.