5,344 karma · joined September 4, 2013
l@processout.com
TiDB has a similar architecture: https://www.pingcap.com/docs/architecture/
https://aws.amazon.com/blogs/database/amazon-aurora-under-th...
https://aws.amazon.com/blogs/database/amazon-aurora-under-th...
https://aws.amazon.com/blogs/database/amazon-aurora-under-th...
https://aws.amazon.com/blogs/database/amazon-aurora-under-th...
It’s fine with PCI DSS as long as it is not reversible.
I think this should be 10GB partitions.
By the way, maybe it’s worth mentioning adaptive capacity? https://aws.amazon.com/blogs/database/how-amazon-dynamodb-ad...
1: https://status.cloud.google.com/incident/cloud-networking/18...
2: https://status.cloud.google.com/incident/cloud-networking/18...
https://peter.bourgon.org/blog
https://engineering.linkedin.com/blog
http://blog.pentestbegins.com (seems down right now?)
http://blog.stephenwolfram.com
I guess I could go on forever…
plus an endless amount of newsletters…
Azure pulls the same trick. AWS seems fine.
Stripe/other gateways do abstract most of PCI DSS from you, and will not return card data via API calls, so that somewhat sidesteps the compliance issue.
Something I appreciate very much about running in the cloud is being able to use the control plane’s APIs to authenticate requesters (e.g. Kubernetes API + Service Accounts or AWS IAM + Instance Roles). Does EnvKey have anything in the way of that?
Regarding PCI compliance: if card data is encrypted, the scope of compliance simply moves over to the keys :-)
I don’t know how they deal with changes in routes.
They don’t seem to ship the actual items but random junk instead (to get a tracking number?).