3
9 Comments

Care about shipping products? Avoid these 5 AWS services

Team Zero Labs has been in business over 3 years, and we have not yet seen a client that managed to use these 5 AWS services correctly.

https://medium.com/teamzerolabs/5-aws-services-you-should-avoid-f45111cc10cd?source=friends_link&sk=c7ca61608a7ccb001c618df75e2bd89c

Read on if you care about time to market!
(Friend link and not paywalled)

on February 21, 2020
  1. 2

    It does make sense to have an actual AWS architect go over your technology choices before you commit to them. Errors are hard to correct later, as you correctly point out in your comments. And a Dev using AWS does not an AWS architect make.

  2. 2

    The kinesis thing seems more like they were just trying to use the wrong tool for what they wanted (which they mentioned sqs/sns at the end). My work heavily relies on kinesis with over 300k events/second running through it and it works like a charm cause we aren't trying to bend it into being a traditional queue.

    1. 1

      Yep, we joined the team half way, and by the time we measured the load and found out that we did not need kinesis, it was too late. Time has already been sank into making it work with python.

      Hindsight is 20/20!

  3. 2

    Cognito just uses JWT tokens anyway, it's not that hard to implement a JWT API for logging in using Node.js from scratch, and once developed it can be used for multiple projects. And gives more control over how the user interface is presented.

    Lambda, if you are using Claudia JS, is viable. You only have one lambda function if you use Claudia API builder and it takes care of all the setup. Super easy to implement a serverless API with.

    1. 1

      Right, unfortunately we were brought in at the middle of the project to clean things up, and then we realized the previous developer had put in lambda that called other lambdas and did all sort of crazy things...

      There are all kinds of powerful tools out there, with lambda newcomers need to be careful to not go overly complex with it!

  4. 2

    Thanks. Almost went down the ElasticCache route :)

  5. 2

    Thanks. Interesting perspective on Cognito. I took a good look at it, and it just seemed...unfinished. I assume AWS will fill in the gaps at some point.

  6. 2

    Interesting list, thanks for sharing. Lambda seems to be the one of these that people fall prey to most often. My impression is that it’s great for certain workload but that shoehorning too much into it can be very costly.

  7. 1

    TL;DR (or for anti medium):

    • Cognito
    • CloudFormation
    • ElasticCache
    • Kinesis
    • Lambda