I've been working on production-grade AWS deployments for over 10 years, so it's a bit hard to frame my experience/skill set. That being said, if you need help with almost anything AWS - architecture, infrastructure, performance, scale - feel free to reach out. Although versed in Well-Architected/multi-region/multi-account, I strive to supply the simplest solution for your particular scenario.
Location: US EST
I've been working on production-grade AWS deployments for over 10 years, so it's a bit hard to frame my experience/skill set. That being said, if you need help with almost anything AWS - architecture, infrastructure, performance, scale - feel free to reach out. Although versed in Well-Architected/multi-region/multi-account, I strive to supply the simplest solution for your particular scenario.
I've been working on production-grade AWS deployments for over 10 years, so it's a bit hard to frame my experience/skill set. That being said, if you need help with almost anything AWS - architecture, infrastructure, performance, scale - feel free to reach out. Although versed in Well-Architected/multi-region/multi-account, I strive to supply the simplest solution for your particular scenario.
- Low-cardinality partition key leading to hot keys, trashing capacity utilization.
- Bad key design means access patterns are off the table forever, as nobody wants to take on data migration with BatchWriteItem.
- Read/write spikes causing throttling errors. The capacity concept is difficult - people don't understand how capacity relates to partitions and object sizes, or wrongly assume "On-Demand Capacity" means throttling is impossible, or that Provisioned Capacity Autoscaling is instant.
- Multiple GSIs to cover multiple access patterns = "why is our bill so high?".
I've seen these issues over and over again while working with real organizations.
Of course it's impressive technology, it's just so littered with traps that I've stopped recommending it except in very specific cases.
I've been working on production-grade AWS deployments for over 10 years, so it's a bit hard to frame my experience/skill set. That being said, if you need help with almost anything AWS - architecture, infrastructure, performance, scale - feel free to reach out. Although versed in Well-Architected/multi-region/multi-account, I strive to supply the simplest solution for your particular scenario.
I've been working on production-grade AWS deployments for over 10 years, so it's a bit hard to frame my experience/skill set. That being said, if you need help with almost anything AWS - architecture, infrastructure, performance, scale - feel free to reach out. Although versed in Well-Architected/multi-region/multi-account, I strive to supply the simplest solution for your particular scenario.
I've been working on production-grade AWS deployments for over 10 years, so it's a bit hard to frame my experience/skill set. That being said, if you need help with almost anything AWS - architecture, infrastructure, performance, scale - feel free to reach out. Although versed in Well-Architected/multi-region/multi-account, I strive to supply the simplest solution for your particular scenario.
Remote: Only
Technologies: IAM, VPC, Cloudwatch, EC2/ASG/ELB, Lambda, API Gateway, RDS, Redshift, DynamoDB, CodeDeploy, Cognito, Athena, S3, Cloudfront, Kinesis, SQS, SNS, IoT Core, Sagemaker, ElastiCache, MediaConvert
Email: hn@cldcntrl.com