Programming

18394 readers

63 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

110

Death by a thousand microservices (renegadeotter.com)

submitted 1 year ago by abobla@lemm.ee to c/programming@programming.dev

19 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] lysdexic@programming.dev 5 points 1 year ago* (last edited 1 year ago) (1 children)

Someone in the thread mentioned that to get the benefits of micro services in a monolith, you can use a linting rule to prevent dependencies across modules

I don't think that makes any sense. The main benefit of microservices is organizational, more specifically how a single team gets to own all aspects of developing, managing, and operating a service.

Lower in priority, there's enabling regional deployments and improved reliability.

How are linting rules even expected to pull that off?

[–] Moc@lemmy.world 4 points 1 year ago

Should have explained my viewpoint. Most startups should not do micro services.

Using linting to prevent coupling between modules can give you some of the benefits of micro services without going all in.