Products · Pattern or everyday thing
Microservices architecture
Raised as a usability problem by 7 people on Hacker News over 9 years (2015–2023), in 7 threads.
People raised many different problems with Microservices architecture, but no single problem has yet been raised by 3 people in 3 different months and threads.
Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.
The newest 7 complaints
- Complexity leaves people unable to get things done; APIs are poorly designed and slow2023-08-19
- Hard to debug and search for code split across many repos and services2023-01-03
- Nearly impossible to debug or reason about; building and booting took a year to figure out2022-11-13
- Setting up a local environment for one task takes days, with many services to configure2022-10-19
- Debugging spans disparate services, so one person needs access to everything to see what's happening2021-02-19
- Deleting one item requires large amounts of code in many services listening for events2018-07-11
- Composing asynchronous operations is confusing for new developers to read2015-10-06