I didn’t see this coming and I think it’s funny, so I decided to post it here.
You must log in or register to comment.
Nano services are microservices after your company realizes monoliths are much easier to maintain and relabels their monoliths as microservices.
Unironically. I’d put a significant wager down on that being the source of this term.
This “article” was written by AI, wasn’t it? This is just throwing vague buzzwords around
deleted by creator
That intro and general structure (AI loves bulleted lists but then again so do I) sure sound like a lot of the responses I’ve gotten. As always, it’s hard to say for sure.
quantum services
take your source code and put each character in its own docker container
this gives you the absolute peak of scalability and agility as every quantum of your application is decoupled from the others and can be deployed or scaled independently
implementing, operating and debugging this architecture is left as an exercise for the reader
that will be $250,000 kthx
implementing, operating and debugging this architecture is left as an exercise for the reader
Challenge accepted by a reader using AI, what could go wrong? xD
Planck services
My services are so small that it is impossible to know just how fast they are running!
I am now offering Planck services for sale, at US$0.0001 per bit.
For an extra fee, you can even choose the value of the bit.
I was going to write that every function should be a service as sarcasm, then I realized that’s exactly what this article is proposing. Now I’m not even sure how to make a more ridiculous proposal than this.
It’s probably AI-supported slop.
Ah, you’re right
Yeah, I had been willing to give the author the benefit of the doubt that this was all part of a big joke, until I saw that the rest of their blog postings are also just like this one.
IaaS Instructions as a Service
Want to know if a value is odd? Boy have we got the API for you!
Why would your whole function be 1 service? That is bad for scalability! Your code is bad and the function will fail 50% of the time half way through anyway. By splitting up the your function in different services, you can scale the first half without having to scale the second half.
You know what they say: micro services, macro outages.
At least you can accurately point the finger at who’s responsible
Well during the never sev0 I’m sure the shareholders will be satisfied with that.
We already have nanoservices, they’re called functions. If you want a function run on another box, that’s called RPC.
What’s next? Femtofunctions
You only need two of them, one for
1and one for0
This is just distributed functions, right? This has been a thing for years. AWS Lambda, Azure Functions, GCP Cloud Functions, and so on. Not everything that uses these is built on a distributed functions model but a fuck ton of enterprises have been doing this for years.
Tech moved in cycles. We come back to the same half-baked ideas every so on, imagine we just discovered the idea and then build more and more technologies on top to try to fix the foundational problems with the concept until something else shiny comes along. A lot of tech work is “there was an old lady who swallowed a fly”.
I always keep saying " You cannot plan your way out of a system built on broken fundamentals." Microservices has it’s use case, but not every web app needs to be one. Too many buzzwords floating around in tech, that promise things that cannot be delivered.
Yep micro services are great, but monoliths are just as great and don’t let anyone tell you otherwise. It all depends on what the system requirements are.
Soooooo… Linux with extra steps.
brb deploying each bin from coreutils as a separate aws lambda function
Found the OpenAI employee 🤣
I work in government IT, and AWS is used there too. I prefer working with a team delivering a COBOL data cruncher service, though the build people have it easier when the job is just connecting a source to a sink in AWS
Neovimservices ftw
Poe’s law strikes again!
I can’t agree more!
I feel like this name addresses the problem of services claiming to be microservices when they’re not.
Does that even happen? cat is micro, sed is micro, systemd isn’t and doesn’t claim to be
gotta keep wirth’s law going strong
