korrents

Our readingWhat is a korrent?

Build a new application as a monolith first, even when you are confident it will eventually need microservices.

Drawn from what Martin Fowler said

What these subjects mean

design How things should be made and judged: what makes a design good, who should do the designing, and what an interface is for.

simplicity Less, but better: reduction as the way to make something good, and the argument about when it goes too far.

Should software be one program or many small services?under our view: Start with one program, because most systems never need more and splitting early is costly

What Martin Fowler actually said

  1. Martin Fowler Chief scientist at Thoughtworks and author of Refactoring
    This leads to a powerful argument for a monolith-first strategy, where you should build a new application as a monolith initially, even if you think it's likely that it will benefit from a microservices architecture later on.

    ↗MonolithFirstmartinfowler.com

    3 Jun 2015

    All 3 korrents from this piecethis one is 2nd

Added to korrents 7 Sept 2026 · How quotes work · Something wrong? Tell us

Do you hold this korrent?Do you also believe this?

I hold this too

Related korrents

Shared subject first, then similar wording. They may agree or disagree.

See this claim on the map