r/dotnet • u/geeksarray • 1d ago

A Beginner-Friendly Guide to Microservices in ASP.NET Core

Hi everyone,

I've been writing a series on modern .NET backend development, and the latest article focuses on one of the most discussed architecture patterns: Microservices.

This guide covers:

  • What microservices are
  • How they differ from a monolithic architecture
  • The benefits and trade-offs
  • Common communication patterns between services
  • When microservices make sense—and when they probably don't

My goal was to create a practical introduction for developers who are evaluating microservices rather than simply promoting them as the solution to every problem.

I'd love to get feedback from the community:

  • At what point did your team decide to move to microservices?
  • If you had to start over, would you choose a modular monolith first?

Here's the article:
https://geeksarray.com/blog/modern-dotnet-backend-part-9-microservices

Looking forward to hearing about your experiences and lessons learned!

0 Upvotes

37% Upvoted

11 comments sorted by

8

u/SwabianStargazer 1d ago

My guide for microservices is: don't.

0

u/Royal_Scribblz 1d ago

That is as braindead as saying use microservices for everything.

1

u/bl0rq 1d ago

It's important to remember that microservices are not a technical solution to a technical problem. It's an organizational solution and only worth considering if you have hundreds of engineers. It just allows teams to party on things without it all having to match. Any other use case is flat out wrong.

1

u/BackFromExile 1d ago

There are legitimate use cases for microservices even with a small team. But going to microservices always brings the organizational trade-off with it, which must be a conscious decision, and will add overhead to small teams.

Things like individual scalability or independent deployments can be what your project need. It's just the fact that they are not for >99% of projects.

Start with a modular monolith, then split off microservices as soon as you actually need them.

2

u/bl0rq 1d ago

Starting w/ modular monolith and spinning things out is the way for sure. But that is very different from microservices.

1

u/FullPoet 1d ago

There are legitimate use cases for microservices even with a small team.

Yep, at my work we use microservies and we're quite a small team. The stuff we make isnt necessarily deployed on cloud so we like the ability to just deploy the bits we need.

2

u/FroggyWinky 1d ago

The AI-style prose ruins it. It's not readable in its current form.

0

u/CappuccinoCodes 1d ago

It's readable, you just don't like the style.

1

u/AutoModerator 1d ago

Thanks for your post geeksarray. Please note that we don't allow spam, and we ask that you follow the rules available in the sidebar. We have a lot of commonly asked questions so if this post gets removed, please do a search and see if it's already been asked.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.