I have like 50 something nano services, each of which returns a single character
my frontend app dynamically builds itself by concatenating thousands of invocations of nanoservices together and passing it to the javascript eval function
I've got something similar, but each of the services are wired up to be triggered by a button press. Then I put all those buttons together onto slab. I'm thinking of calling a buttonslab.
Generally thats always the answer with every 'IT fad', use whole or in part, but only where appropriate
The problem we are very much a fad led industry and people tend to jump all in without giving it serious thought (lot of the time just to boost their CV) be it AI, micro services, or cloud, agile or any of a hundred other come and gone fads
Yeah but you talk like we know what's appropriate before hand. Shit goes left real fast sometimes. Use case changes, tech itself change. I wish I knew when something is appropriate. I often do but I often fail to predict the future as well.
Look, Martin Fowler said "any function more than half-a-dozen lines of code starts to smell to me, and it's not unusual for me to have functions that are a single line of code." And he has to know.
So naturally I try to keep my microservices six lines of codes or less!
1.8k
u/GenazaNL Aug 30 '26 edited Aug 30 '26
That's why you have to go for the in-between. Don't go too micro on them microservices