What if they ask you: and you? Are you actually building high quality software?
What are your quality gates? How many open bugs are there on production? How often you close bugs with resolution: won't fix(because of budget issues)? How often do you have production incidents? What is your testing strategy? How are you testing your requirements before assigning them to the developer for implementation? Do you hire external professionals for security testing?
Rabbit and most databases have their own failover strategy. Putting it all on k8s is fine for a toy app but idk why anyone would deploy a real system like that.
OK, I can only speak to my personal projects and 20+ years experience at work.
We run all of our stateful and stateless workloads on 10+ kubernetes clusters at work in multiple datacenters in multiple continents, and we serve 500 million users a month with it.
I wrote the first BORG version of DFP backend systems at Google, where we served billions of users billions of ads a day, and we used stateful infrastructure management on some of the first container runtime systems that inspired k8s during it's development.
Using rabbit and "most databases" native fallover strategy is fine for toy projects, but when you're operating at this scale, you need automated infrastructure provisioning and all of the automated tooling around it.
There are layers to this. At the simplest level, you only have K8s people (and aren't willing to use cloud services). So you install the RabbitMQ Helm chart, hope for the best, and fix any issues that come up.
Then you get a bit worried that the Postgres Helm chart, while good, doesn't do what you want. So you update to use a dedicated clustered Postgres, using some Postgres clustering tech.
Finally, you're at so much scale you can throw giant wads of advertising cash at the problem, and you can use anything you like and it'll work. You just need to choose the best thing for your particular problem.
They are cylindrical, grey, without apparent means of aerial propulsion, and prone to interfering with ultrasonic sensors...
Most dolphins are smaller than a compact car, but I bet they would break apart upon impact with a frozen sea after dropping out of the sky. This might be the correct answer.
With 1.5 fatalities per 100,000,000 miles[0], the benchmark to meet is 99.9999985% of the time it doesn't kill you. Injuries are going to be a lot higher, obviously. Still, I think most self-driving enthusiasts underestimate the bar that needs to be crossed wrt safety. And general vehicle safety isn't going to remain stagnant. I think it's going to be a cost vs injuries tradeoff for quite a while until we get human-level or better self-driving safety in all circumstances.
Captured the requests in a flash client used in a 6 hour defensive driving class to skip to the last page. Got my certificate. My friend did the same thing and the company reached out trying to figure out why they were getting all of these database errors...
The list is long. If you're familiar with c++ take a look at C#. Go and Java are safe bets as well. Beyond that there are a million backend languages out there.
