MonolithFirst


34 bookmarks. First posted by aezell june 2015.


"This pattern has led many of my colleagues to argue that you shouldn't start a new project with microservices, even if you're sure your application will be big enough to make it worthwhile."
microservices  architecture  advice 
6 weeks ago by niksilver
Monolith = bad, Microservices = good. If you are working in tech today, it is difficult to escape the microservices vs monolith debate. This debate is often one-sided and personally I'm not convinced that there is enough collective experience to justify the universal departure from the monolith.

> 1. "Almost all the successful microservice stories have started with a monolith that got too big and was broken up"
> 2. "Almost all the cases where I've heard of a system that was built as a microservice system from scratch, it has ended up in serious trouble."

In this article Martin Fowler explores the idea that trying to build out microservices from the start may be more challenging than starting out with a monolith and transitioning to a microservices architecture.

In my experience:
- You may not like your monolith, but it is an encapsulation of your business services, why throw that away?
- Getting the service or domain boundaries right is harder than you might think, the best evidence for boundary friction is almost certainly evident in the monolith
- Starting with microservices all too often means a new, spin-off, development team. How do you ensure they are equipped with the business understanding necessary to implement a solution that meets business need?
tech  techarch  microservices  domain 
9 weeks ago by billglover
Martin Fowler As I hear stories about teams using a microservices architecture , I've noticed a common pattern. Almost all the successful microservice stories…
from instapaper
9 weeks ago by bkeetman
This pattern has led many of my colleagues to argue that you shouldn't start a new project with microservices, even if you're sure your application will be big enough to make it worthwhile.
agile  architecture  development  microservices  programming 
9 weeks ago by ntschutta
Going directly to a microservices architecture is risky, so consider building a monolithic system first. Split to microservices when, and if, you need it.
programming 
9 weeks ago by Sergey
Some interesting reading going around on building “MonolithFirst”
from twitter_favs
9 weeks ago by adz
As I hear stories about teams using a microservices architecture, I've noticed a common pattern.

Almost all the successful microservice stories have started with a monolith that got too big and was broken up
Almost all the cases where I've heard of a system that was built as a microservice system from scratch, it has ended up in serious trouble.

This pattern has led many of my colleagues to argue that you shouldn't start a new project with microservices, even if you're sure your applic...
10 weeks ago by martinbalfanz
Old piece, valid and valuable as ever: "MonolithFirst"
rfw  cloud  microservices  from twitter
10 weeks ago by cveira
Almost all the successful microservice stories have started with a monolith that got too big and was broken up ... Almost all the cases where I've heard of a system that was built as a microservice system from scratch, it has ended up in serious trouble.
web_dev 
10 weeks ago by zephyr777
bliki: MonolithFirst // true that
from twitter_favs
10 weeks ago by parsingphase
Microservices is da bomb, I dig it. But unless you need it is your best choice in the beginning
MonolithFirst  from twitter_favs
june 2017 by sergiolopes
As I hear stories about teams using a microservices architecture, I've noticed a common pattern.

Almost all the successful microservice stories have started with a monolith that got too big and was broken up
Almost all the cases where I've heard of a system that was built as a microservice system from scratch, it has ended up in serious trouble.
This pattern has led many of my colleagues to argue that you shouldn't start a new project with microservices, even if you're sure your application will be big enough to make it worthwhile.
microservices  monolith  development 
march 2017 by jenkner
MonolithFirst
from twitter
june 2015 by dizz
RT : So much this:

Like the dark side, the lure of needlessly clever/complex architecture is strong.
from twitter_favs
june 2015 by aezell