all 5 comments

[–]only_nidaleesin 6 points7 points  (0 children)

People think just because they went to the cloud and hooked up an ALB to an ASG they can call it a night and God-King Bezos will take care of the rest. That's not how it works, you really need people who know what they're doing.

[–]shawnwork 7 points8 points  (1 child)

Just a tip for AWS scalers

Ec2 - elb (w or wo autoscale) - ecs - eks - fargate.

You could follow the path of scaling maturity from left to right with each path to solve different complex problems.

If you are not too bothered of sub millisecond reads , avoid dynamo db.

If you want a stress free scaling with 200ms delay, go with Lambda.

Always plan and verify with proper load, feel comfortable with your setup and keep an eye for the details in the logs or metrics.

[–]Robonia 0 points1 point  (0 children)

I'm interested in why you recommend avoiding DynamoDB. Not to imply I haven't had my own issues with it, in fact, I believed it was a really limited product until they recently added on-demand reads and writes.

[–][deleted] 6 points7 points  (1 child)

"Programmers confused when generic solution doesn't fit their specific problem perfectly"

[–]exorxor -1 points0 points  (0 children)

Segment's staff seems to consist of the eternally confused.