If the request data is larger than the limit it doesn’t get processed by the Cloudflare system. By increasing buffer size they process (and therefore protect) more requests.
When I worked for a company who worked with big banks / financial institutions we used to run disaster recovery tests. Effectively a simulated outage where the company would try to run off their backup sites. They ran everything from those sites, it was impressive.
Once in a while we'd have a real outage that matched the test we ran as recently as the weekend before.
I was helping a bank switch over to the DR site(s) one day during such a real outage and I left my mic open when someone asked me what the commotion was on the upper floors of our HQ. I said "super happy fun surprise disaster recovery test for company X".
VP of BIG bank was on the line monitoring and laughed "I'm using that one on the executive call in 15, thanks!" Supposedly it got picked up at the bank internally after the VP made the joke and was an unofficial code for such an outage for a long time.
In most BIG banks, "Vice President" is almost an entry-level title. Easily have 1000s of them. For example, this article points out that Goldman Sachs had ~12K VPs out of more than 30K employees: https://web.archive.org/web/20150311012855/https://www.wsj.c...
Just like all Sales folks have heavily inflated titles, no customer wants to think they're dealing with a junior salesperson/loan officer when you're about to hand over your money.
It seems like every vendor sales team I work with is an "executive" or "director of sales" even though in reality they're just regular old salespeople.
VP at Goldman is equivalent to Senior SWE according to levels.fyi and their entry level is Analyst. I'm surprised by the compensation though. I would have thought people working at a place with gold in the name would be making more. Also apparently Morgan Stanley pays their VPs $67k/year.
In fairness to the fly.io folks (who are extremely serious hackers), they’re standing up a whole cloud provider and they’ve priced it attractively and they’re much customer-friendlier than most alternatives.
I don’t envy the difficulty of doing this, but I’m quite confident they’ll iron the bugs out.
I don’t always agree with @tptacek on social/political issues, and I don’t always agree with @xe on the direction of Nix, but these are legends on the technical side of things. And they’re trying to build an equitable relationship between the user of cloud services and the provider, not fund a private space program.
If I were in the market for cloud services I’d highly prize a long-term relationship on mutual benefit and fair dealings over a short-term nuisance of being an early adopter.
I strongly suspect your investment in fly is going to pay off.
I'm several steps removed from day-to-day engineering at this point; the team working on this is much better than I am. It's just a very hard problem; biting it off is something you can certainly blame me for, though.
I may be the minority on this view, but I think that it's possible to be both a recognized expert aka legend and loud ("visible" might be a kinder word).
When you talk technology, I listen, and I doubt I'm alone in that. Keep up the good work with fly.io!
I want to believe, but in the meantime they’re killing the product I’ve been working hard to build trust with my own customers though. There is a limit to my idealism, and it’s well and truly in the past.
I suspect that making a cloud service provider run reliably requires tons of grunt work more than it requires technical heroism from a small number of highly talented individuals.
(Neon employee) We auto-upgrade minor versions as long as they can be done autonomously. For major versions, you're right it's still manual but we're working on improving that. Here is our version policy: https://neon.tech/docs/postgresql/postgres-version-policy
I didn't know that was decided, and was just catching up on it now. This was a fun read:
> Mr Walker and other high-level executives from Iceland (the supermarket), took an emergency delegation to Iceland (the country), where they were met with a cold shoulder.
Jetbrains only “did it right” because there was huge community outcry about their move to pure subscription so they moved to the “if you subscribe for X amount of time you get to keep the last version you had when you stop subscribing”.
Props to them for listening to the community but question whether they should be the gold standard given it is still a compromise position.
Got trapped by the same thing. Usage based billing is a huge pain point for us we were really excited by lago but dont want to self host infra if we can outsource it.
We ended up talking to about 5 different usage based billing API providers and basically no one is interested in servicing the sub $1000 per month market which is where we will realistically be for the next year as we grow.
Additionally lago and other providers advertise "no revenue cut" and then always quote pricing as a percentage of revenue (which is technical not a revenue cut except your fee scales pretty linarly with revenue).
Take a look at https://revenium.io (full disclosure: I'm co-founder/cto.) We are a fully hosted solution with a free/developer tier and plans that start at $19/month. We also have a self-hosted option.
This is actually a space I’m exploring. Would love to chat about your use case if you’re interested. Shoot me an email at chris. Domain name revenuehq.com.
We are billing more than $1000 a month :). The providers didn’t want our business for less than $1000 per month (at a heavily discounted time limited price).
We talked to this many providers because it’s a huge pain point for us and the thing we hacked together was inadequate for tracking usage.
