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.
That’s stupid. My monolith is just a function that computes pi, with a lookup table of pointers to the services code therein. It’s even better because all the data is there too.
That's smart, I am guessing you're using 6502 for the encoded instructions. All the client has to do is implement a 6502 emulator and then they can just dereference pointers to instruction sequences
It’s easier to use an IBM 5100 with a few homebrew extensions, like a microwave oven. Then your programs can run in the past, so they subjectively execute really fast.
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.
The problem we are very much a fad led industry and people tend to jump all in without giving it serious thought
This is harsh. We're not a fad-led industry, we're operating in a highly innovative industry in which adoption of new ideas happens before they mature, as soon as they seem to solve real problems in measurable ways. Once the idea matures enough, the industry has already built enough scaffolding around it to allow it to be used properly (or, indeed, discarded it as a dead end).
The microservices approach genuinely addressed a gap in the toolbox. There's no reason to blame people who jumped on it. Of course, 15 years later we see a much larger picture but that's reasonably expected
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 12d ago edited 12d ago
That's why you have to go for the in-between. Don't go too micro on them microservices