sgarland

27 ms·

421.
by sgarland 1y ago
Also, every time your cloud went down, the parent company begged you to reconsider, explaining that all they need you to do is remove the disturbingly large cobwebs so they can migrate it. You tell them that to do so would violate your stro
422.
by sgarland 1y ago
It depends on the outage. There was one a year or two ago (I think? They run together) that impacted EC2 such that as long as you weren’t trying to scale, or issue any commands, your service would continue to operate. The EKS clusters at my
423.
by sgarland 1y ago
us-east-2 does exist; it’s in Ohio. One major issue is a number of services have (had? Not sure if it’s still this way) a control plane in us-east-1, so if it goes down, so does a number of other services, regardless of their location.
424.
by sgarland 1y ago
Active-active RDBMS - which is really the only feasible way to do HA, unless you can tolerate losing consistency (or the latency hit of running a multi-region PC/EC system) - is significantly more difficult to reason about, and to ma
425.
by sgarland 1y ago
EDIT: TIL that there are cross-state ZIP codes.
426.
by sgarland 1y ago
If you include an ORDER BY, the DB _may_ continue searching. MySQL (and, I assume, MS SQL Server, since it also can cluster the PK) can stop early in some circumstances. But if you just have a LIMIT, then no - any RDBMS should stop as soon
427.
by sgarland 1y ago
Because a city/region/state can be uniquely identified with a postal code (hell, in Ireland, the entire address is encapsulated in the postal code), but the reverse is not true. At scale, repeated low-cardinality columns matter a
428.
by sgarland 1y ago
You’re not wrong, of course. It’s a natural consequence of the eschewing of DBAs, and the increasingly powerful compute available - even if someone did notice that the slowdown was due to the PK choice, they can often “fix” that by paying m
429.
by sgarland 1y ago
Who are these "experts?" I'm a DBRE, and also very security conscious, and think this is an absurd what-if for most companies. If it does matter for your application, then don't expose it - use an opaque id with someth
430.
by sgarland 1y ago
> Detecting V7 uuids in the API contract would probably require me to enforce a special key name (uuidv7 & uuid for v4) for easier audit. Unless I'm missing something, check it on receipt, and reject it if it doesn't match.
431.
by sgarland 1y ago
Many distributed databases have mechanisms to use an auto-increment, actually - often, generating large chunks at a time to hand out.
432.
by sgarland 1y ago
TFA states that they’re running on AWS Fargate. That said, as an example, an m8g.8xlarge gives you 32 vCPU / 128 GiB RAM for about $1000/month in us-east-1 for current on-demand pricing, and that drops to just under $700 if you ca
433.
by sgarland 1y ago
It’s that, and the fact that precious few people seem to understand fundamentals anymore, which is itself fed by the desire to outsource everything to 3rd parties. You can build an entire stack where the only thing you’ve actually made is t
434.
by sgarland 1y ago
Yes, though unless you’re provisioning your own EC2s for them to run on, you have no guarantee about the server generation, and IME AWS tends to provision older stuff for Fargate. This may or may not matter to you depending on your applicat
435.
by sgarland 1y ago
Sure, but there are some fundamentals about latency that any programmer should know [0] (absolute values outdated, but still useful as relative comparisons), like “network calls are multiple orders of magnitude slower than IPC.” I’m assumin
436.
by sgarland 1y ago
Bear in mind that SQLite is used in embedded systems, and I absolutely wouldn’t be surprised to learn it’s in space.
437.
by sgarland 1y ago
Was this Mozilla?
438.
by sgarland 1y ago
Nah, just run Puppet or similar. You’re welcome to run your command to validate what you already tested in stage, but if you don’t also push a PR that changes the IaC, it’s getting wiped out in a few minutes. I hate not having root access
439.
by sgarland 1y ago
> My pet theory about the real reason: the hyper-scalers hire all the engineers who have the skills to deploy-to-a-few-beefy-servers, and then charge a 10x multiplier for compute. This is also my pet theory, and it’s maddening. They’ve s
440.
by sgarland 1y ago
I have literally never met a dev who wanted to deal with any kind of infrastructure.
441.
by sgarland 1y ago
Yes, you need to write Ansible initially. But honestly, it’s not that much for your average application server. Turn on unattended-upgrades with anything critical to your application blacklisted, and you won’t have to touch it other than to
442.
by sgarland 1y ago
> have you ever seen a terrible db schema? I am a DBRE, so yes, unfortunately most days I see terrible schemata. > Having to suddenly iterate fast with a brittle codebase that doesnt really allow that ive seen bring teams to their kne
443.
by sgarland 1y ago
I watched in amusement as the architecture team at $JOB eagerly did a PoC of a distributed RDBMS, only to eventually conclude that the latency was too high. Gee… if only someone had told you that would happen when you mentioned the idea. Oh
444.
by sgarland 1y ago
A distributed monolith - which is what nearly all places claiming to run microservices actually have - has N^m uptime. Even if you do truly have a microservices architecture, you’ve also now introduced a great deal of complexity, and unless
445.
by sgarland 1y ago
And your cloud providers thank you for giving their executives a third yacht.
446.
by sgarland 1y ago
Legitimately asking, how? The only bottleneck should be the DB, and if you can saturate a 128-core DB, I want to see your queries and working set size. Not saying it can’t happen, but it’s rare that someone has actually maxed out MySQL or
447.
by sgarland 1y ago
I wouldn’t start with K8s, and I’ve administered it at multiple companies. Unless every one of your initial hires is a SWE turned SRE, you’re in for a bad time (and you don’t need it). I’d personally start with Linux services on some VMs, b
448.
by sgarland 1y ago
> Giving other teams the ability to develop their own service without needing to conform to your archaic grey beard architecture restrictions IME at many different SaaS companies, the only one that had serious reliability was the one tha
449.
by sgarland 1y ago
That’s a skill issue, not an indictment on the limitations of the architecture. You can spin up N servers and load-balance them, as TFA points out. If the server is a snowflake and has nothing in IaC, again, not an architectural issue, but
450.
by sgarland 1y ago
THANK YOU. People look at me like I’m insane when I tell them that their overly-complicated pipeline could be easily handled by a couple of beefy servers. Or at best, they’ll argue that “this way, they don’t have to manage infrastructure.”

More ›