tly_alex

Just curious, how do you like Changsha? Most people on hacker-news are from the tech industry, Changsha was more famous for its TV/media entertainment industry.

It's surprsing that in 2020 that a bookstore would like to walk away from where most customers would go and buy their product. I hope they find it would be able to serve their customer better with their own online bookstore and less cost to run their own infrastructure.

It's extraordinary to see an once open and welcoming governement to become xenophobic and ruleless. In the last 10 years, when things like this happen in other country, you would hear POTUS or media condemn this kind of action by referring to an once sacred word like "law" and "due process".

Just like the double standard on delaying the election, it's ok to delay election due to COVID in US, but it's perfectly fine to condemn other places for doing the same.

It would be very interesting to see how how ppl or historian view this 10 years later.

"The F-150 carries a base price of $28,495, which is below average for a full-size pickup truck." This is just a quick search from Google. I think ppl might have different opinion of the word "luxury". But generally I would personally not categorize things that's widely sold like F-150 or iPhone as luxury.

Same here.

And the choice of black arrow on top of an almost black background... I am not a designer but that's just killing my eyes here.

The write-up is not very clear in my opinion. The graph seems to show that there're 3 API calls (maybe there're more API calls in reality?).

And if I understand this correctly, the issue is in the first API call, where the server does not validate whether the requester owns the Email address in the request.

What confuses me are where're the "decoded JWT’s payload" comes from. Is it coming from a different API call or it's somewhere in the response?

> The SRE teams which used Rightscale at my last job used to have "buttons to press for things", which roughly translated to "If the primary node fails, first promote the secondary, then get a new EC2 box, format it, install software, setup certificates, assign an elastic IP, configure it to be exactly like the previous secondary, then tie together replication and notify the consistent hashing."

If I understand this correctly, all of the things could have been automated in AWS fairly easily .

"If the primary node fails" Health check from EC2 or ELB.

"get a new EC2 box" ASG will replace host if it fails health check.

"format it" The AMI should do it.

"install software, setup certificates" Userdata, or Cloud-init.

"assign an elastic IP, configure it to be exactly like the previous secondary, then tie together replication and notify the consistent hashing" This could be orchestrated by some kind of SWF workflow if it takes a long time or just some lambda function if it's within a few mins.

AWS and other cloud provider provides far more reliable and simpler features/toolkings than k8s. For teams that's serious about building services on the cloud, having k8s to take over certain area of orchestration make sense, but the "operating system" K8s provides is just a tiny peace of the overall infrastructure.

Console is suppose to just be a web UI to quickly make a change or explore the feature. Any high quality engineering team should avoid make changes through console because it's not testable and repeatable. For code change, use codedeploy or container through ECS. For configuration and infrastructure changes, CloudFormation should be the right tool.

Migration on resources taking live traffic is not an easy thing. Before migrating the traffic over to a different end-point, the time and the engineering work to make sure the new endpoints works is money and cost. Also there could be statefull data in the original account and to do a live migration of data with new data coming in at X tps is absolutely hard work.

Make sense. This is a classic example of bad operation management leads to unexpected outcome. Could have be solved much easier with proper configuration management.

+1 ECS is very very simple to use. And it has good integration with other AWS services like load balancing and logging

DNS doesn't resolve somehow. works now.