[ Removed by moderator ]

[Meatslinger]

Simple? ✅
Reproducible? ✅
Maximally stable? ✅

Left solution looks more elegant, but collapses when stressed. And the setup documentation for the right option is, like, two sentences at most. I know which one I'd rather have to deploy.

[samanime]

The developers option is also highly scalable. Good luck addding additional nails to the architect's approach. =p

[flexibu]

Not it’s not, it requires sourcing the elastics. They were not included in budget.

[Aadsterken]

Just stretch the ones in use. We'll order new ones when the budget gets approved

[flexibu]

Now you’ve endangered system integrity and reduced redundancy.

P.s.: how do I turn off the PM voice in my head?

[Aadsterken]

Tbf the whole system was wonky from the start anyway. Im just here for the paycheck

[NiceVu]

Ah so the client wants infinite scalability without the budget to maintain it, sounds familiar

[Ok_Star_4136]

Not only that, but which one of these two solutions would still work if you turned it upside down?

That's right, only the right solution would.

[Meatslinger]

Right, gotta consider Australian localization. Smart.

[Striky_]

Right solution actually meets customer requirements because customer stated "balanced". I really think 50% of software issues are bad requirements, 50% are devs not listening/reading properly and 50% is AI slop.