How to start with micro services ?

Filipe Costa — Sat, 04 Jan 2025 10:52:07 +0000

When are the best moment to start with distributed system ?
When i have decide about decouple my system in a distributed system ?

Our Case

Imagine a bakery where have a one baker, imagine after now our orders increase a lot and his baker can't make breads for everyone, what is your better way ?

When the distributed system are important ?

our can pay more money for this baker to him to make more breads and working more hours to attending our clients, yes ?

probably our baker can achieve our goals , to attending more clients , but we have a some problems with this approach.

some problemas we can have

our baker might get sick
our baker may resign

if any this situations happen , all our clients not can have breads , this is called single point of failure.

How the moment to start a micro services structure ?

I believe when we have a lot of orders(requests) and our system that's so important to many clients and a single point of failure can destroy our company.

first step

Our baker probably make a do a lot of things, made breads , sweet breads, pizzas, manager delivery , charge clients, how many responsibilities to this baker , no ?

the first step for me, we can choose the main responsibilities for this baker .

for our context, the main responsibilities are make breads and sweet breads.

if you pay attention on our problem , our bakery have a lot of responsabilities, the first step problem is a remove all responsabilities that not are to a baker job, like charge money, manager delivery system ant many other things.

our first service

we need a new worker , his name is gateway , this worker are distributed the orders in our bakery .

then when a new customer to go our bakery our customers talk first with our worker gateway and gateway distruted the orders in our bakerey.

second service

our first service are called kitchen , kitchen are responsibilities to do breads, sweet breads, pizzas and all other things related like food.

third service

another responsibility that we removed from our only baker is manager delivery , when send a ready order , manager a transit deliver and many things about delivery system in a bakery shop.

Fourth Service

We removed another responsibility from our baker: handling money. It’s very difficult to bake bread while also managing financial reports and taking care of cash transactions.

Final Structure

Why is this our final structure so important? Our primary goal was to eliminate a single point of failure. If our baker gets sick at any point, it’s no longer a problem. We can simply hire another baker to keep things running smoothly.

Another issue we addressed was reducing the responsibilities of our sole baker. Now, we can easily improve our bakery by scaling the team. Need more bakers? No problem, we hire additional bakers. Too many deliveries? That’s fine, we can hire more people to manage addresses.

This is the first part of our article. Comment below if you’d like to see part 2!

Vertical or Horizontal Scale?

Filipe Costa — Mon, 10 Jun 2024 02:10:06 +0000

System Design

Horizontal Scaling or Vertical Scaling?

Hi, this is my first article in English, so I apologize for any mistakes. I'm trying to improve my English each day. In this article, I will explain some basic principles of system design for beginners.

Scenario

Imagine that you have built software and an API. Suddenly, you get more and more users, and your application starts experiencing timeouts. You need to increase the capacity of your server.

What is the best way to scale your server?

Vertical Scaling

Vertical scaling involves upgrading a single machine with more resources—such as memory, processor, and disk space—instead of adding more machines.

Horizontal Scaling

Horizontal scaling involves adding more machines to your infrastructure, increasing the number of servers rather than the resources of a single server.

Which is the Best Choice?

It depends on various factors. Below are some good and bad points of each design:

Vertical Scaling

Good Points	Bad Points
Consistent data	Single point of failure
Single point of process	Hardware limits
Small infrastructure (no need for load balancer)

Horizontal Scaling

Good Points	Bad Points
Scales well	Potential data inconsistency
Resilient	Many network calls
Good for increasing users	More expensive to maintain
	Larger infrastructure

As we can see, there are many good and bad points for each design. Horizontal scaling tends to have more complexity and costs but can handle more users and provide better resilience.

Key questions to consider:

Is data consistency very important to you?
Can a single point of failure destroy your company?
Are your users critical?
Does your company have a perspective to increase users?

These considerations can help you choose the best option. Normally, in early stages of a company, vertical scaling is the best way. However, at some point, a single machine might not be enough to support your growth.

Unfortunately, there is no definitive answer to these questions—it depends on your specific situation and moment.

DEV Community: Filipe Costa

How to start with micro services ?

Our Case

When the distributed system are important ?

How the moment to start a micro services structure ?

first step

our first service

second service

third service

Fourth Service

Final Structure

Vertical or Horizontal Scale?

System Design

Horizontal Scaling or Vertical Scaling?

Scenario

Vertical Scaling

Horizontal Scaling

Which is the Best Choice?

Vertical Scaling

Horizontal Scaling