The 2 billion email address stealer log breach I talk about this week is almost ready to go at the time of writing. It's been massively time-consuming, massively expensive (we turned the cloud up to 11) and enormously frustrating. I've written about why in the draft blog post, but once you get to the point of inserting billions of records into a system with lots of billions of records, most of the usual way we'd do things totally goes out the window. I think we're looking at Wednesday morning Europe time to get that out (oh, also, hi from Oslo!) so definitely stay for that one. Next week, I'll talk about how much subsequent support pain this breach is going to cause us 😭
References
- Sponsored by: Report URI: Guarding you from rogue JavaScript! Don’t get pwned; get real-time alerts & prevent breaches #SecureYourSite
- The bad guys have the Qantas data and the good guys have it too, despite the injunction (just not us good guys 🤷♂️)
- I'm almost ready to pull the trigger on the next PC build! (it's a hefty spec with a heft price, but it'll really pay off next time we procss data like Synthient's)
