4 ms·

This opinion piece has too many inaccurate statements. - S3 for static assests - SQS V Kinesis - Lambda ('Small code that doesn't change....what). - ELB com

This opinion piece has too many inaccurate statements. - S3 for static assests - SQS V Kinesis - Lambda ('Small code that doesn't change....what). - ELB completely overlooked, if you need session persistence then you need an ELB so for more traditional software you've completely omitted that solution because it's "Legacy". Missing - No discussion on when to pick Lambda, Containers or EC2 - No Cloudfront addresses S3 and any API GW or ALB fronted Lambda. - Where is the use of SNS? - What if I want to Fan Out on a message/event? complete missed the why SQS V SNS V Kinesis and when to use which. - No RDS....so if i've got relational data are you advising i should put it in DynamoDB? - No container context in any way. Really poor quality of content and advisories needs an urgent update.

SideburnsOfDoom 7y ago
> Where is the use of SNS? Right, the SQS part is very misleading: "SQS has 1 consumer" is technically true (although it's actually one group of competing consumers), but in practice, you get fan-out to zero or more consumers easily, by wiring SNS and SQS together (one SNS topic, multiple attached SQS queues). > No RDS... Without also mentioning RDS with DynamoDB, you can't make meaningful choices between them. It also omits the one big benefit of DynamoDB: single-digit number of milliseconds to read a record by primary key, regardless of scale, due to sharding on that key.
intsunny 7y ago
> - ELB completely overlooked, if you need session persistence then you need an ELB so for more traditional software you've completely omitted that solution because it's "Legacy". Additionally the legacy ELB is great for when you want to do you own TLS/SSL termination with Lets Encrypt. (Especially with kubernetes, ingress, and cert-manager.) Also with the legacy feature, you can enable ProxyProtcol which passes on the public IP info after the NAT.

SideburnsOfDoom 7y ago

> Where is the use of SNS? Right, the SQS part is very misleading: "SQS has 1 consumer" is technically true (although it's actually one group of competing consumers), but in practice, you get fan-out to zero or more consumers easily, by wiring SNS and SQS together (one SNS topic, multiple attached SQS queues). > No RDS... Without also mentioning RDS with DynamoDB, you can't make meaningful choices between them. It also omits the one big benefit of DynamoDB: single-digit number of milliseconds to read a record by primary key, regardless of scale, due to sharding on that key.

intsunny 7y ago

> - ELB completely overlooked, if you need session persistence then you need an ELB so for more traditional software you've completely omitted that solution because it's "Legacy". Additionally the legacy ELB is great for when you want to do you own TLS/SSL termination with Lets Encrypt. (Especially with kubernetes, ingress, and cert-manager.) Also with the legacy feature, you can enable ProxyProtcol which passes on the public IP info after the NAT.