Tap a claim on the ring to put it at the centre.
← Successful microservice systems almost always began as a monolith that…
14 connected korrents · 10 moments on record from 3 Jun 2015 to 1 Sept 2026.
Everything filed under TypeScript
TypeScript
Everything filed under vibe coding
vibe coding
Everything filed under JavaScript
JavaScript
Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject
Read this korrent: Successful microservice systems almost always began as a monolith that grew too big, and systems built as microservices from scratch end up in serious trouble.
Successful microservice systems almost always began as a monolith that grew too big, and systems built as microservices from scratch end up in serious trouble.
Last stated 11 years ago
3 Jun 2015
MF
Martin Fowler — holds since 2015-06-03 — tap for who they are
Same subject: Build a new application as a monolith first, even when you are confident it will eventually need microservices. — tap to centre the map on it
Build a new application as a monolith first, even when you are confident it will eventually need microservices.
Last stated 11 years ago
3 Jun 2015
MF
Martin Fowler — holds since 2015-06-03 — tap for who they are
Same subject: Service boundaries cannot be got right at the start, and moving functionality between services is far harder than moving it inside a monolith. — tap to centre the map on it
Service boundaries cannot be got right at the start, and moving functionality between services is far harder than moving it inside a monolith.
Last stated 11 years ago
3 Jun 2015
MF
Martin Fowler — holds since 2015-06-03 — tap for who they are
Same subject: Uber's thousands of microservices were not an architectural preference but a survival decision: under that growth only independent, unblocked teams could build fast enough to stay alive. — tap to centre the map on it
Uber's thousands of microservices were not an architectural preference but a survival decision: under that growth only independent, unblocked teams could build fast enough to stay alive.
Last stated 5 months ago
1 Apr 2026
TP
Thuan Pham — holds since 2026-04-01 — tap for who they are
Same subject: Kubernetes won because Docker had already won: it inherited the one container runtime the whole industry had agreed on, instead of shipping another. — tap to centre the map on it
Kubernetes won because Docker had already won: it inherited the one container runtime the whole industry had agreed on, instead of shipping another.
Last stated 3 months ago
3 Jun 2026
KH
Kelsey Hightower — holds since 2026-06-03 — tap for who they are
Same subject: Letting non-programmers vibe-code features into a large existing product destroys its architecture, even when every individual change looks defensible. — tap to centre the map on it
Letting non-programmers vibe-code features into a large existing product destroys its architecture, even when every individual change looks defensible.
Last stated 2 weeks ago
26 Aug 2026
DH
David Heinemeier Hansson — holds since 2026-08-26 — tap for who they are
Same subject: A proprietary language licensed from Microsoft had zero chance in the JavaScript ecosystem: TypeScript had to be open source or nobody would come. — tap to centre the map on it
A proprietary language licensed from Microsoft had zero chance in the JavaScript ecosystem: TypeScript had to be open source or nobody would come.
Last stated 4 months ago
13 May 2026
AH
Anders Hejlsberg — holds since 2026-05-13 — tap for who they are
Same subject: Because its types are erased before the program runs, TypeScript can afford not to be sound: checking 99% beats the 0% JavaScript checked, and buys features a sound language cannot offer. — tap to centre the map on it
Because its types are erased before the program runs, TypeScript can afford not to be sound: checking 99% beats the 0% JavaScript checked, and buys features a sound language cannot offer.
Last stated 4 months ago
13 May 2026
AH
Anders Hejlsberg — holds since 2026-05-13 — tap for who they are
Same subject: Fiscal multipliers vary across time and place but are generally nonzero, positive for spending, negative for taxes, and larger when monetary policy cannot offset them. — tap to centre the map on it
Fiscal multipliers vary across time and place but are generally nonzero, positive for spending, negative for taxes, and larger when monetary policy cannot offset them.
Last stated 4 years ago
1 Jun 2022
OB
Olivier Blanchard — holds since 2022-06-01 — tap for who they are
Same subject: A person at maximum vibe-coding speed has about three productive hours a day, and a company that will not let them stop there is going to break. — tap to centre the map on it
A person at maximum vibe-coding speed has about three productive hours a day, and a company that will not let them stop there is going to break.
Last stated 6 months ago
11 Mar 2026
SY
Steve Yegge — holds since 2026-03-11 — tap for who they are
Same subject: A sense of achievement in software survives writing almost none of the code yourself. — tap to centre the map on it
A sense of achievement in software survives writing almost none of the code yourself.
Last stated 2 weeks ago
26 Aug 2026
DH
David Heinemeier Hansson — holds since 2026-08-26 — tap for who they are
Same subject: A vibe-coded codebase grows heresies: wrong ideas that take root among the agents, keep coming back, and are very hard to weed out. — tap to centre the map on it
A vibe-coded codebase grows heresies: wrong ideas that take root among the agents, keep coming back, and are very hard to weed out.
Last stated 6 months ago
11 Mar 2026
SY
Steve Yegge — holds since 2026-03-11 — tap for who they are
Same subject: A programming language is a ten-year play: version one has issues, version two fixes them, version three is finally good — and only then does adoption start. — tap to centre the map on it
A programming language is a ten-year play: version one has issues, version two fixes them, version three is finally good — and only then does adoption start.
Last stated 4 months ago
13 May 2026
AH
Anders Hejlsberg — holds since 2026-05-13 — tap for who they are
Same subject: For a TypeScript team, Rust belongs on the backend — API servers — and not in the front end. — tap to centre the map on it
For a TypeScript team, Rust belongs on the backend — API servers — and not in the front end.
Last stated 4 months ago
20 May 2026
AR
Alice Ryhl — holds since 2026-05-20 — tap for who they are
Same subject: If you can use Effect for TypeScript, you should -- to the point of not starting a new project without it. — tap to centre the map on it
If you can use Effect for TypeScript, you should -- to the point of not starting a new project without it.
Last stated a week ago
1 Sept 2026
DM
Dillon Mulroy — holds since 2026-01-09 — tap for who they are
DM
Dillon Mulroy — holds since 2026-09-01 — tap for who they are
same subject or similar wording a cloud: claims about one subject, named for it bar: when it was last stated, on a scale from 2015 to today — full is today a face: someone on record holding the claim — tap it for who they are
At the centre
Successful microservice systems almost always began as a monolith that grew too big, and systems built as microservices from scratch end up in serious trouble.
Last stated 3 Jun 2015 · 11 years ago
Holds MF Martin Fowler
Read this korrent →
Similar wording
Build a new application as a monolith first, even when you are confident it will eventually need microservices.
Last stated 3 Jun 2015 · 11 years ago
Holds MF Martin Fowler
Similar wording
Service boundaries cannot be got right at the start, and moving functionality between services is far harder than moving it inside a monolith.
Last stated 3 Jun 2015 · 11 years ago
Holds MF Martin Fowler
Similar wording
Uber's thousands of microservices were not an architectural preference but a survival decision: under that growth only independent, unblocked teams could build fast enough to stay alive.
Last stated 1 Apr 2026 · 5 months ago
Holds TP Thuan Pham
Similar wording
Kubernetes won because Docker had already won: it inherited the one container runtime the whole industry had agreed on, instead of shipping another.
Last stated 3 Jun 2026 · 3 months ago
Holds KH Kelsey Hightower
Similar wording
Letting non-programmers vibe-code features into a large existing product destroys its architecture, even when every individual change looks defensible.
Last stated 26 Aug 2026 · 2 weeks ago
Holds David Heinemeier Hansson
Same subject: JavaScript
A proprietary language licensed from Microsoft had zero chance in the JavaScript ecosystem: TypeScript had to be open source or nobody would come.
Last stated 13 May 2026 · 4 months ago
Holds AH Anders Hejlsberg
Same subject: JavaScript
Because its types are erased before the program runs, TypeScript can afford not to be sound: checking 99% beats the 0% JavaScript checked, and buys features a sound language cannot offer.
Last stated 13 May 2026 · 4 months ago
Holds AH Anders Hejlsberg
Same subject: JavaScript
Fiscal multipliers vary across time and place but are generally nonzero, positive for spending, negative for taxes, and larger when monetary policy cannot offset them.
Last stated 1 Jun 2022 · 4 years ago
Holds Olivier Blanchard
Same subject: vibe coding
A person at maximum vibe-coding speed has about three productive hours a day, and a company that will not let them stop there is going to break.
Last stated 11 Mar 2026 · 6 months ago
Holds SY Steve Yegge
Same subject: vibe coding
A sense of achievement in software survives writing almost none of the code yourself.
Last stated 26 Aug 2026 · 2 weeks ago
Holds David Heinemeier Hansson
Same subject: vibe coding
A vibe-coded codebase grows heresies: wrong ideas that take root among the agents, keep coming back, and are very hard to weed out.
Last stated 11 Mar 2026 · 6 months ago
Holds SY Steve Yegge
Same subject: TypeScript
A programming language is a ten-year play: version one has issues, version two fixes them, version three is finally good — and only then does adoption start.
Last stated 13 May 2026 · 4 months ago
Holds AH Anders Hejlsberg
Same subject: TypeScript
For a TypeScript team, Rust belongs on the backend — API servers — and not in the front end.
Last stated 20 May 2026 · 4 months ago
Holds AR Alice Ryhl
Same subject: TypeScript
If you can use Effect for TypeScript, you should -- to the point of not starting a new project without it.
Last stated 1 Sept 2026 · a week ago
Holds Dillon Mulroy