Reducing insider trading in a microservice architecture

You are receiving this email because you subscribed to microservices.io


In November, I'll be teaching public workshops in Berlin and Milan. I hope you will enroll.


My service collaboration patterns online bootcamp is available at a discount. Use coupon CCMHVSFB to sign up for $95 (valid until November 8th, 2024). There are deeper discounts for buying multiple seats.


Reducing insider trading in a microservice architecture

During a workshop I taught this week, we had an interesting discussion about a common microservice architecture design problem:

The doSomething() operation, which is implemented by Foo Service, needs to get data from numerous services including Bar Service and Baz Service in order to respond to a request. Getting the data via their APIs seems lot of work. Why can’t it just query the databases directly?

Here’s my answer:

Read on to learn more.

Services must be loosely design-time coupled

A defining characteristic of the microservice architecture is that services are loosely design-time coupled. Consequently, services should not share their databases with other services since it results in type design-time coupling. Service must, instead, collaborate via their APIs.

APIs don’t guarantee loose design-time coupling

You might be tempted to think that as long as services communicate via their APIs, they are loosely design-time coupled. Foo Service could, for example, query each of the other services: ie. invoke getBarInfo(), getBazInfo(), etc. Alternatively, it could use the CQRS pattern The problem with both of these approaches is that they don’t guarantee loose design-time coupling. A service API might simply expose its database schema through its API.

It’s insider trading

One service retrieving data from another service can sometimes resemble the Inside Trading code smell. The service behaves like a class (or modules) that accesses the internal data of another class (or module). And, just like Inside Trading between classes, it can lead to a tightly coupled design that is difficult to understand, maintain, and evolve.

Design services to look like icebergs

A service should resemble an iceberg. Its API should encapsulate the implementation details. We can increase encapsulation in the above example by refactoring the doSomething() operation and moving the logic that uses some other service’s data from the Foo Service into the other service. The doSomething() operation then invokes an operation on each of the services that executes the service-specific logic. It would, for example, invoke doSomethingBar() on the Bar Service and doSomethingBaz() on the Baz Service. Such an approach can significantly increase encapsulation and reduce design-time coupling.

Applying the idea to takeout burritos

In my QConPlus 2021: Takeout burritos and minimizing design-time coupling in a microservice architecture talk, I applied this idea to the Order Service and Restaurant Service example. Originally, the Order Service’s createOrder() operation retrieving a restaurant’s menu to validate the line items and compute the Order’s subtotal. The drawback of this approach is that the Order Service is tightly coupled to the Restaurant Service: any change to the structure of MenuItem in the Restaurant Service would require a lockstep change in the Order Service. The solution was to reduce design-time coupling by moving responsibility for knowing the OrderLineItems and computing the Order’s subtotal into the Restaurant Service. The Restaurant Service simply passed the Order subtotal to the Order Service.

Need help with accelerating software delivery?

I’m available to help your organization improve agility and competitiveness through better software architecture: training workshops, architecture reviews, etc.

Learn more about how I can help

Older messages

Reminder: The evolution of the Microservice Architecture pattern language

Thursday, October 31, 2024

You are receiving this email because you subscribed to microservices.io In November, I'll be teaching public workshops in Berlin and Milan. I hope you will enroll. My service collaboration patterns

The evolution of the Microservice Architecture pattern language

Tuesday, October 29, 2024

You are receiving this email because you subscribed to microservices.io In November, I'll be teaching public workshops in Berlin and Milan. I hope you will enroll. My service collaboration patterns

Reminder: Architectural patterns for modular monoliths that enable fast flow

Thursday, September 12, 2024

You are receiving this email because you subscribed to microservices.io This month, I'm teaching an online public workshop Architecting for fast, sustainable flow: enabling DevOps and Team

Architectural patterns for modular monoliths that enable fast flow

Tuesday, September 10, 2024

You are receiving this email because you subscribed to microservices.io This month, I'm teaching an online public workshop Architecting for fast, sustainable flow: enabling DevOps and Team

Reminder: Architecting microservices for fast, sustainable flow

Thursday, September 5, 2024

You are receiving this email because you subscribed to microservices.io This month, I'm teaching an online public workshop Architecting for fast, sustainable flow: enabling DevOps and Team

You Might Also Like

Weekend Reading — More time to write

Sunday, November 24, 2024

More Time to Write A fully functional clock that ticks backwards, giving you more time to write. Tech Stuff Martijn Faassen (FWIW I don't know how to use any debugger other than console.log) People

🕹️ Retro Consoles Worth Collecting While You Still Can — Is Last Year's Flagship Phone Worth Your Money?

Saturday, November 23, 2024

Also: Best Outdoor Smart Plugs, and More! How-To Geek Logo November 23, 2024 Did You Know After the "flair" that servers wore—buttons and other adornments—was made the butt of a joke in the

JSK Daily for Nov 23, 2024

Saturday, November 23, 2024

JSK Daily for Nov 23, 2024 View this email in your browser A community curated daily e-mail of JavaScript news React E-Commerce App for Digital Products: Part 4 (Creating the Home Page) This component

Not Ready For The Camera 📸

Saturday, November 23, 2024

What (and who) video-based social media leaves out. Here's a version for your browser. Hunting for the end of the long tail • November 23, 2024 Not Ready For The Camera Why hasn't video

Daily Coding Problem: Problem #1617 [Easy]

Saturday, November 23, 2024

Daily Coding Problem Good morning! Here's your coding interview problem for today. This problem was asked by Microsoft. You are given an string representing the initial conditions of some dominoes.

Ranked | The Tallest and Shortest Countries, by Average Height 📏

Saturday, November 23, 2024

These two maps compare the world's tallest countries, and the world's shortest countries, by average height. View Online | Subscribe | Download Our App TIME IS RUNNING OUT There's just 3

⚙️ Your own Personal AI Agent, for Everything

Saturday, November 23, 2024

November 23, 2024 | Read Online Subscribe | Advertise Good Morning. Welcome to this special edition of The Deep View, brought to you in collaboration with Convergence. Imagine if you had a digital

Educational Byte: Are Privacy Coins Like Monero and Zcash Legal?

Saturday, November 23, 2024

Top Tech Content sent at Noon! How the world collects web data Read this email in your browser How are you, @newsletterest1? 🪐 What's happening in tech today, November 23, 2024? The HackerNoon

🐍 New Python tutorials on Real Python

Saturday, November 23, 2024

Hey there, There's always something going on over at Real Python as far as Python tutorials go. Here's what you may have missed this past week: Black Friday Giveaway @ Real Python This Black

Re: Hackers may have stolen everyone's SSN!

Saturday, November 23, 2024

I wanted to make sure you saw Incogni's Black Friday deal, which is exclusively available for iPhone Life readers. Use coupon code IPHONELIFE to save 58%. Here's why we recommend Incogni for