Does coding with LLMs mean more microservices?
1–10 of 73 posts
Re: Does coding with LLMs mean more microservices?
#2[flagged]
Re: Does coding with LLMs mean more microservices?
#3[dead]
Re: Does coding with LLMs mean more microservices?
#4[flagged]
Re: Does coding with LLMs mean more microservices?
#5Why microservices when small composable CLI tools seem a better fit for LLMs?
Re: Does coding with LLMs mean more microservices?
#6This seems like the idea of modularizing code, and using specific function sighatures for data exchange as an API is being re-invented by people using AI. Aren't we already mostly doing things this way, albeit via submodules in a monolith, due to the cognitive ctrain it puts on humans to understand the whole thing at any given time?
Re: Does coding with LLMs mean more microservices?
#7This makes no sense. You can easily make a monolith and build all parts of it in isolation - i.e. modules, plugins, packages.
In fact, my argument is that there will be more monolith applications due to AI coding assistants, not less.
Re: Does coding with LLMs mean more microservices?
#8[flagged]
This makes no sense as you’re able to have similar interfaces and contracts using regular code.
Microservices solve an organizational problem mostly — teams being able to work completely independently, do releases independently, etc — but as soon you’re going to actually do that, you’re introducing a lot of complexity (but gain organizational scalability).
This has nothing to do with context sizes.
Re: Does coding with LLMs mean more microservices?
#9What matters for LLMs is what matters for humans, which usually means DX. Most Microservice setups are extremely hard to debug across service boundaries, so I think in the future, we'll see more architectural decisions that make sense for LLMs to work with. Which will probably mean modular monoliths or something like that.
Re: Does coding with LLMs mean more microservices?
#10That's an argument for components with well-defined contracts on their interfaces, but making them microservices just complicates debugging for the model.
It's also unclear whether tight coupling is actually a problem when you can refactor this fast.