AWS bills are un-auditable. I'm convinced every org is being over-charged for bugs in their billing and tracking software. I've asked on multiple occasions where charges randomly started appearing (despite no infra changes), which weren't there the month before, and no one was able to answer on the AWS support side.
Can you expand on "you know, the "official experiment" that suddenly got discarded to the surprise of its developers" and where that announcement was made?
After several hurricanes - you should treat them as 4 way stops, however a large chunk of people just run through them (most recent example is from Irma)
I was testing table loads with a few millions rows and kept running into issues with deleting the data and consistent performance (compared to postgres). Postgres won the performance over view and after finding out DELETE would lock the entire DB process (you should use DROP instead) - I moved on.
> The only way to succeed in a micro services architecture is with a strong focus on quality inside each service and consumer driven contract testing between.
Do you have any examples from other large companies that do micro-services at Netflixs' scale?
Continuing work on adding more OS support for https://sysward.com - patch management and security notifications for a range of linux OSs ( Ubuntu, Debian, RHEL, CentOS, SUSE, OpenSUSE )