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.
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.
I'm curious what things you're trying to do that requires you to overload xunit classes? We use xunit for everything and haven't found any gaps so far.
Because the API is a REST API and you don't want your frontend to have to make 100 calls to render a screen. Each frontend may be a completely different app so they all need the data in their own format. And each team may control their app so you don't want all of the teams roadblocked by the API team.
You're going to think you have it figured out and then they and you are going to get sick. I'm 3 months in and the lack of sleep is tough. Hobbies are on hold. Just try not to think about it too much and focus on taking care of your kiddo, your SO and your job. There might be enough energy to do most of that.
When I see a job posting with no salary all I think is what are they scared of? Must be low. A 4 hour project for a senior? For DevOps? I could spend those 4 hours pinging people in my network and probably have interviews scheduled.
How does returning it to the river solve the problem of their isn't enough groundwater? That water goes back into the ocean where it's stuck if it never rains.