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.
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.
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
I’m trying to understand how this is different than a concept I learned in computer science in the late 80s/early 90s called RPCs (remote procedure calls). My senior project in college used these. Yes I’m old and this was 35 years ago.
It’s basically the same concept, just implemented with a k8s cluster so you have scale-to-zero capabilities I guess
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
What’s next? Femtofunctions
You only need two of them, one for
1and one for0
Announcing FemtoServices™ - One Packet at a Time!
In an era of bloated bandwidth and endless data streams, today we proudly unveil a groundbreaking approach to networking: FemtoServices™ – Connectivity, one Ethernet packet at a time!
(Not to be confused with our premium product, ParticleServices, which just shoot neutrinos around one by one.)
Cant wait to set up a docker container for a service which takes a string input and transforms it into a number as the output. Full logging, its own certificate for encryption of course, 5 page config options and of course documentation. Now, you want to add two numbers together? You got the addition service set up right?
It’s a modern day enterprise fizzbuzz: https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpriseEdition
Oh yeah, this is the stuff business dreams are made of.
Poe’s law strikes again!
I can’t agree more!
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.
Metaservices.
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.
someone at my work didn’t get the message.
2000+ line function with 3157 node packages.
is that nano enough?
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.
We already have nanoservices, they’re called functions. If you want a function run on another box, that’s called RPC.
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.
This is just the Linux way but with… Rest? Seems slow.
