Me talking to people worried about scaling:
"You're right, we're gonna need a 2nd generation FitBit w/an external drive to handle that kinda load."
Me talking to people worried about scaling:
"You're right, we're gonna need a 2nd generation FitBit w/an external drive to handle that kinda load."
@binford2k @GeePawHill My techblog uses a CGI that runs a giant Python program (with some efficiency hacks some of the time), on a shared VM that has a total of 4 GB of RAM and a not that modern CPU. It has repeatedly made the front page of that orange site and a few other places, and basically no one has noticed.
It isn't the machines that are slow, it's the software. (And my other rant is "you don't need static HTML to stand up to loads", although static HTML makes it much, much easier.)
The number of teams I've met who are doing AWS and/or k8s for a service mesh to handle loads a single 1985 PC could deliver, smdh.
25k users, 100 transactions each a day.
Baby, *any* monolith could deliver that, if your team doesn't start with the assumption that http is free.
@GeePawHill my LUG webserver at university got slashdotted, hit Reddit, and hacker news at the same time in 2008 or so. Oh, and k5 too, RIP. It was a bog standard off the shelf PC tucked away in an office, running drupal on postgresql. We consumed 99.9% of the university’s traffic and got a nice little visit from IT the next day.
And the machine did indeed slow down a little bit. I mean, if you were looking for it.
I think about that experience a lot these days when people talk about scale.
"5000 users at 5 transactions a day!?!? Do you have a 'smart' refrigerator?"
"Well, to be honest, the single 8gb VPS w/the 2tb disk *is* gonna run you. You're looking at maybe $50/month."
I know it's a very unpopular old-school stance -- I'm 64yo, and I'm aging out -- but I think you maybe should make some money off your first 25k users hitting a monolith on a VPS before you start paying AWS bills.
The powerless I speak this truth to, almost uniformly, give me the old-man-yells-at-cloud look.
@GeePawHill in 2001 or 2002 a colleague of mine showed our proprietary VoIP PBX software running on a Toshiba Libretto (486 iirc running Windows 2000) and the rest of the company never understood the power of that, because servers are 19” pizza boxes with quad Itanium processors and 256 MByte RAM…
@GeePawHill yeah, a conversation I have quite frequently
"okay roughly how many transactions per second are we talking?"
"we don't know."
"okay let's work that out so we can plan ..."
"we don't need to because we will implement on k8s using cutting edge caching technologies and service network architectures and therefore everything will be web scale"
"... okay I come up with 5 tps so allowing for ... wait, what?"
@GeePawHill Definitely a big fan of small monoliths and SQLite and single VMs. Admittedly in AWS because it's been easy, but I am using almost no features of EC2 other than "a small VM please".
@GeePawHill is performance/load the main argument why they use k8s? My impression is that the value comes with more flexibility in the development, eg I can easily automate pipelines for any number of feature branches etc. That used to be tricky without a good container platform/cloud.
@GeePawHill Is performance why they're doing it though? I'd do it because a mostly idle pod is cheaper than a VM is cheaper than any kind of physical space, plus how easy it is to have a proper deployment pipeline and zero downtime on redeployment.
Not simpler, far more complex and lots of moving parts. But easier.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.