News for hackers. Stuff that matters.
Re:I'm Going to Scale My Foot Up Your Ass (2008) by wrldos on Sunday February 05, 2023 @04:39AM (#34663382)
Pretty accurate. Everything I've seen that doesn't scale only doesn't because it was written by idiots who read lots of blog posts about scalability.

I'm still convinced we could run our entire software platform off 5 EC2 instances and an S3 bucket. But the last 10 years of technical mismanagement turned this into a microservices shit show. Splunk gets more traffic than our clients do.

Re:I'm Going to Scale My Foot Up Your Ass (2008) by hkt on Sunday February 05, 2023 @05:40AM (#34663718)
Similar situation where I've arrived recently: a big public sector org where the biggest expense each month is cloudwatch.
Re:I'm Going to Scale My Foot Up Your Ass (2008) by durnygbur on Sunday February 05, 2023 @06:13AM (#34663888)
Try to say "no" or even "but" to the logging and monitoring request ticket... do you like having monthly income or not?
Re:I'm Going to Scale My Foot Up Your Ass (2008) by smitty1e on Sunday February 05, 2023 @06:14AM (#34663901)
But we loves us some info porn.
Re:I'm Going to Scale My Foot Up Your Ass (2008) by wrldos on Sunday February 05, 2023 @06:16AM (#34663914)
Data lake after 2 years = data cesspit.
Re:I'm Going to Scale My Foot Up Your Ass (2008) by durnygbur on Sunday February 05, 2023 @06:22AM (#34663959)
Soon consultant will be selling wastedata treatment systems.
Re:I'm Going to Scale My Foot Up Your Ass (2008) by wrldos on Sunday February 05, 2023 @06:38AM (#34664048)
That's a brilliant idea. /dev/null as a service. Charge per byte.
Re:I'm Going to Scale My Foot Up Your Ass (2008) by MikeDelta on Sunday February 05, 2023 @06:49AM (#34664120)
> Charge per byte

of unzipped data

Re:I'm Going to Scale My Foot Up Your Ass (2008) by iso1631 on Sunday February 05, 2023 @07:27AM (#34664366)
I'd couldn't afford my backups then!
Re:I'm Going to Scale My Foot Up Your Ass (2008) by wrldos on Sunday February 05, 2023 @08:41AM (#34664804)
I guarantee we will not be upselling AWS egress fees to you though so think of the cost savings on recovery!
Re:I'm Going to Scale My Foot Up Your Ass (2008) by exikyut on Sunday February 05, 2023 @09:20AM (#34665089)
Re:I'm Going to Scale My Foot Up Your Ass (2008) by jbverschoor on Sunday February 05, 2023 @06:26AM (#34663984)
Or just 1 or 2 physical machines?
Re:I'm Going to Scale My Foot Up Your Ass (2008) by wrldos on Sunday February 05, 2023 @06:37AM (#34664043)
Well we still need to handle AWS losing a region and hardware replacement. Does happen quite regularly.
Re:I'm Going to Scale My Foot Up Your Ass (2008) by imwillofficial on Sunday February 05, 2023 @08:35AM (#34664768)
But do you?

Do you really need those 5 nines?

If my bank can go down every week for patching, you probably can too.

Re:I'm Going to Scale My Foot Up Your Ass (2008) by wrldos on Sunday February 05, 2023 @08:40AM (#34664797)
Our customers can't operate at all if our systems are down, so yes we do.
Re:I'm Going to Scale My Foot Up Your Ass (2008) by mechanical_bear on Sunday February 05, 2023 @09:45AM (#34665283)
I’m sure your customers can go down for a minute every other week.
Re:I'm Going to Scale My Foot Up Your Ass (2008) by pixl97 on Sunday February 05, 2023 @10:20AM (#34665561)
It doesn't matter if they can or cannot. This is what happens when you think like an engineer and not like a salesperson.

What matters if they will pay someone else for that reliability they don't need.

Re:I'm Going to Scale My Foot Up Your Ass (2008) by itsmeste on Sunday February 05, 2023 @07:24AM (#34664346)
The last 5 years I found myself developing for companies having a bunch of nonsense "microservices" with totally ridiculous separation, which added more to their problems than solving them.

The common denominator of those companies is they all had no significant traffic, had their initial codebase developed by (unmanaged) amateurs, and were later managed by people inexperienced in software.

Due to the heavy resistance in all cases, I eventually became tired of proposing simpler solutions and the endless discussions around it, and accepted premature microservice architectures to be part of my infinite source of income.

Re:I'm Going to Scale My Foot Up Your Ass (2008) by grahamlee on Sunday February 05, 2023 @10:11AM (#34665487)
Kubernetes: from the Ancient Greek word for “more pods than customers”.
Re:I'm Going to Scale My Foot Up Your Ass (2008) by Sinidir on Sunday February 05, 2023 @12:52PM (#34666985)
Thats pretty funny.
Re:I'm Going to Scale My Foot Up Your Ass (2008) by rippercushions on Sunday February 05, 2023 @07:36AM (#34664429)
My favorite microservices pattern is having lots of separate little services, so you get that sweet overhead and complicated debugging, with a shared database, so you can still enjoy systemwide single points of failure and obscure side effects on data.
Re:I'm Going to Scale My Foot Up Your Ass (2008) by itsmeste on Sunday February 05, 2023 @07:45AM (#34664482)
Have those microservices use different patterns (language, framework, infra, etc), and outnumber your devs by a magnitude so everybody gets a piece of that sweet context switching, multiple times a day.
Re:I'm Going to Scale My Foot Up Your Ass (2008) by dopidopHN on Sunday February 05, 2023 @09:32AM (#34665186)
* * *
Re:I'm Going to Scale My Foot Up Your Ass (2008) by wrldos on Sunday February 05, 2023 @08:38AM (#34664787)
Ah I am gorging myself financially on exactly that form of sweet misery.
Re:I'm Going to Scale My Foot Up Your Ass (2008) by majormajor on Sunday February 05, 2023 @10:23AM (#34665594)
I was complaining recently to a manager at another company about a half-assed "microservice breakout" project in a previous job where some teams moved from one big service + one big DB to many big services + single DB and introduced fun new DB connection + perf issues... and was dismayed to learn that this other manager didn't even think "a bunch of services all talking to the same giant DB" seemed like best practices.
Re:I'm Going to Scale My Foot Up Your Ass (2008) by mypastself on Sunday February 05, 2023 @10:37AM (#34665712)
Add to that an existing monolith that’s only been partly migrated to microservices and brother, you’ve got a stew going.
Re:I'm Going to Scale My Foot Up Your Ass (2008) by Scubabear68 on Sunday February 05, 2023 @11:20AM (#34666085)
Yep.

Have also seen this coupled with the microservices pattern of having all the microservices share a large common library, with all microservices built together and deployed together all the time. All the pain of shared code across teams plus the pain of shared DB plus the pain of debugging across completely arbitrary process boundaries.

Re:I'm Going to Scale My Foot Up Your Ass (2008) by karmakaze on Sunday February 05, 2023 @01:20PM (#34667269)
Sounds like a cargo-culted monorepo.
Re:I'm Going to Scale My Foot Up Your Ass (2008) by layer8 on Sunday February 05, 2023 @01:39PM (#34667488)
This can actually make sense when you have loosely coupled services that mostly talk to the database and external systems, and not directly to each other, that have a common domain model (due to the shared database) and common helper libraries, and that you want to be restartable separately, and/or be distributed over several hosts. Of course, the process boundaries should be well-chosen and not arbitrary.
Re:I'm Going to Scale My Foot Up Your Ass (2008) by neilv on Sunday February 05, 2023 @10:36AM (#34665709)
One time, I had to put together an architecture diagram for a big investor presentation (diagram of an unusual bespoke many-servers system).

Basically, get boxes on the diagram for each aspect the exec might want to talk about or answer questions about. So that they'd have something to point to, and investors would have some level of understanding, as well as confidence that we thought of and were doing something about that. (This is a bit different than the views we were using to discuss and build it internally.)

So I mention to a colleague that I "just know", if a room of tech investors see the Web facet of this (even though that's the easiest technical part of the system), and this one part is all going through only one server (which is all it would ever need), someone is gonna be concerned that we might not know what we're doing about scalability, and I bet the exec doesn't want to get derailed debating that with them.

Colleague advised we go full "System Design Interview!", so I spewed all the unnecessary vapid things we could do, that some semi-technical person might be tuned to look for. Trying to modify the spew to be sensible enough (if encumbering overkill) that, if investors happened to have a hardcore veteran techie vetting (like one of the people who built AWS or Google from nuts and bolts), that they wouldn't become enraged with disgust, and kill me where I stand. The meeting seemed to go well.

In a different (real, internal) diagram, for networking architecture, I also broke out out some logical functions into distinct physical servers (some fixed, some variable) in an information/control flow compartment. Then I added a comment on the diagram, something about that these might be combined into a single server for efficiency, for smaller deployments, like customer on-prem. And, I didn't add, if our own data center suddenly needed to host a hugely-popular service for others, and we had suddenly enough hardware for that, the software would be ready (but we'd still only need one server in that one spot that a System Design Interview book-prepped person would think needed a load balancer and workers).

Re:I'm Going to Scale My Foot Up Your Ass (2008) by toxik on Sunday February 05, 2023 @11:40AM (#34666283)
Anyway, so I tied an onion to my belt, which was the style at the time.
Re:I'm Going to Scale My Foot Up Your Ass (2008) by jjgreen on Sunday February 05, 2023 @11:52AM (#34666406)
White or yellow?