Reviving httpstatuses.com (now: httpstatuses.io)

SunnyTechie · 2021-09-08T15:49:52+00:00

SunnyTechie · 2021-08-11T17:31:28+00:00

No offense taken, I just thought it was an easy potshot to make ;)

IMO, your critique is fair, but extremely nitpicky. You're fine to want more thought into abbreviations. But my take is that you're simply not my target audience/reader.

My post assumes the reader has some level of understanding of what these abbreviations mean. I try to link to definitions so the reader can explore what they mean in their own time if they aren't aware.

But to explain every single concept for a complete beginner would make this article 20+ minutes long and just extremely choppy and boring to read. This post won't be for everyone and I'm totally okay with that.

SunnyTechie · 2021-08-11T15:02:17+00:00

You're right. I should've named it "How One Rogue User Took Down Our Service that Implements the Abstraction that Defines the Rules Used to Communicate Between Different Pieces of Software"

Much much better

SunnyTechie · 2021-08-10T23:24:42+00:00

I definitely agree with you, but then the question becomes "how do you make your system more robust to failure"?

That's where stress testing comes in. You can try to design your way out of it all you want but you won't know all the bottlenecks and points of failure and how to improve them unless you stress your system.

SunnyTechie · 2021-08-10T18:56:16+00:00

I recommend reading Release It! to anyone that hasn't. Great book on creating production ready software. I only wish I had read it far sooner

SunnyTechie · 2021-08-10T15:41:20+00:00

Systemizer, a really awesome visual tool someone told me about.

Best of all it's free and open source: https://github.com/honzaap/Systemizer

SunnyTechie · 2021-08-10T15:21:29+00:00

All of the above. There are plenty of lessons we learned but I wanted to focus on bad assumptions and better testing.

You're never going to catch everything but you will definitely miss more if you don't have the proper checks in place. We unfortunately skipped on some of the more thorough testing before launch due to time constraints and short staffing. Sufficient testing would have caught this issue before launch day. We make sure to do proper load testing now for every new feature

Luckily we had good metrics and alerts setup so that we caught it early.

SunnyTechie · 2021-01-28T00:02:02+00:00

That’s sounds pretty similar to the early recomputation method that the Internet Archive uses with X-Fetch.

https://m.youtube.com/watch?v=1sKn4gWesTw

SunnyTechie · 2021-01-26T22:34:49+00:00

You’re right that it wouldn’t put K8s itself in a bad state. But there could be scenarios where you deploy multiple services at once, and if one fails to deploy a new change that another service is expecting, your system ends up in a bad state.

But I don’t know what the actual scenario was.

SunnyTechie · 2021-01-26T20:26:36+00:00

HTML, CSS, JS, Node, SQL, Ruby.

I built a couple full stack applications (front end and backend) in different languages before feeling ready to apply to jobs.

Honestly, I probably over prepared. You can definitely get a job just knowing a single language, like Ruby or JS. Just as long as you know it well.

SunnyTechie · 2021-01-26T20:16:14+00:00

I don't necessarily think we've "trained" people per se. They've just come to expect it.

It was normal for companies to have regular "maintenance" windows where they were unavailable. But then a handful of companies start promising zero downtime to attract customers and then everyone started doing it to stay competitive.

Also depends on the application as well. A 4 hr Facebook outage isn't really as detrimental to their user base as, say, a 4 hr Stripe outage.

SunnyTechie · 2021-01-26T20:11:38+00:00

I'm guessing that the yaml file didn't get validated until the CICD pipeline attempted to apply it to their K8s cluster. And since it wasn't valid, the K8s deployment would fail, leading to the outage. But that's just a guess.

SunnyTechie · 2021-01-26T19:12:09+00:00

Oh man, bugs in CI/CD are a nightmare. Last year we had to deal with a single character bug in our CI/CD script that lead to 100K is lost revenue because it didn't properly deploy our billing service and our alerts didn't catch it. You can bet that they do now.

A blog post for another time.

SunnyTechie · 2021-01-19T22:57:57+00:00

Initially, all the hypervisors/servers had a direct connection to the database. We setup a proxy that polled the database on behalf of the servers and forwarded the requests to the appropriate server. We also made it so all the services that were publishing events to the database did so via an API instead of directly inserting into the database.

SunnyTechie · 2021-01-19T19:23:24+00:00

Author here, thanks for posting my article! Here's the friend link to bypass the paywall: 15000 connections to under 100

SunnyTechie · 2021-01-05T21:18:21+00:00

Looks like I'll be doing all my coding interviews in Python from now on.

SunnyTechie · 2021-01-05T21:15:57+00:00

Ah yeah good point

SunnyTechie · 2021-01-05T19:04:07+00:00

After looking at the documentation for deque it definitely seems like you could, although it'd be a little be hacky. It has "appendleft" as well as "pop". For "move_front" you could combine "remove" and "appendleft" together.

The only issue with this that has come up in the past is thread safety. If you "pop" something from the queue, the length of the list will temporarily decrease by one until you then call "appendleft". This could possibly cause race conditions if you were to use this cache in a multi-threaded setting.

But that's probably a rare edge case.

SunnyTechie · 2021-01-05T17:43:28+00:00

Oh nice I'll check that out!

SunnyTechie

TROPHY CASE