|
|
|
|
|
|
by parpfish
404 days ago
|
|
|
I’ve read a lot of pros/cons about micro services over the last decade, but don’t have a clear definition for what qualifies. My current job insists that they have a “simple monolith” because all the code is in a single repo. But that repo has code to build dozens of python packages and docker containers. Tons of deploy scripts. Different teams/employees are isolated to particular parts of the codebase. It feels a lot like microservices, but I don’t know what the defining feature of microservices is supposed to be |
|
|
Which honestly may be the future if LLMs stay in a dev's toolkit. Plugging in an AI model to a monorepo provides so much context that can't be easily communicated across microservices in separate repos.