In my experience, the result is just more crawling across the separate microservices and additional reasoning to confirm how it all fits together.

The monolithic codebases are easier to crawl for any problem that can't be conveniently isolated to a single microservice.

phkahler a day ago | parent | next [-]

A good API should be documented, and AI should not have to read the internal code to understand how to use it.

	▲	Aurornis a day ago \| parent [-]
		Like I said, if your work is already contained neatly inside one microservice then it doesn't matter. The same would be true in a monolith: The context to understand what's happening would be contained to a few files. When the work starts crossing through domains and potentially requiring insight into how other pieces work, fail, scale, etc. then the microservice model blows up complexity faster than anything, even if you have the API documented.

gedy a day ago | parent | prev [-]

Sounds like tight coupling issue, not services per se