us-east-1 the worst region for availability

Totally biased opinion, but I think you should check out https://github.com/mokies/ratelimitj if you are Java based.

Afterpay (http://www.afterpay.com) | Backend Java | Decisioning Rules/ML | Melbourne, Australia | ONSITE

We are a deferred payment service undergoing significant growth. I'm looking for Australian based engineers to assist with global expansion plans.

SOFWARE ENGINEER - BACKEND JAVA - https://www.touchcorp.com/our-people/careers/sofware-enginee...

LEAD SOFTWARE ENGINEER - RISK DECISSIONING - https://www.touchcorp.com/our-people/careers/lead-software-e...

https://www.touchcorp.com/careers TECHNICAL BUSINESS ANALYST - DATA - https://www.touchcorp.com/our-people/careers/technical-busin...

SOFTWARE ENGINEER - PERFORMANCE & OBSERVABILITY - I need to write up this job spec today!

Interview process: phone screen, code exercise, onsite technical then behavioural interview (we try to make it fun!)

Great article that I expect will assist many teams that are facing scaling issues.

I thought it appropriate to plug my java based rate limiting library that implements the token bucket algorithm as mentioned in the article

https://github.com/mokies/ratelimitj

Keep is Google's Moonshot for Notes

It will take these organisation years and lots of money to rebuild their reputations when their security malpractices catch up with them.

I would love this to be true, since it would basically double my net worth, but it's very rare for a security incident to kill a company. Target is the exception, and just required two human sacrifices.

I understand that HTTP/2.0 needs to address both scalability and security, but the proposed "trusted" proxies smells really bad. Knowing what we know today, in that the current level of security offered by HTTP/1.1 is barely adequate to protect web citizens from real and present threats, shouldn't we be radically rethinking HTTP security.