Can We Improve How Lyft Handled Service Discovery on AWS In 2016? (Reaction) @marknca
Can We Improve How Lyft Handled Service Discovery on AWS In 2016? (Reaction)  @marknca
Uploaded October 2021 | Updated September 2026, 1 week ago
In late 2016, Lyft did an AWS "This is My Architecture" video. It was one of the first. In the video they explained how they tackled the problem of discovering what microservices were available and healthy in their environment.

Now, a few years later, I react to that video and see what's stood the test of time, what could be done simpler given today's technology, and generally critique the design against the AWS Well-Architected Framework in a mini AWS Well-Architected Review.

The original video: youtu.be/sjpP2ynkCbo

More on the AWS Well-Architected Framework is at aws.amazon.com/architecture/well-architected

Follow me on Twitter at twitter.com/marknca

Read my AWS Hero bio at aws.amazon.com/developer/community/heroes/mark-nunnikhoven

Learn more about the AWS Well-Architected Framework in my course on A Cloud Guru at markn.ca/courses/#mastering-the-well-architected-framework

Index:
- [00:00] Series intro
- [00:41] Problem statement
- [02:59] Service discovery intro
- [05:01] Request flow
- [06:46] Discovery service
- [08:45] Inter-service comms
- [11:45] Resiliency
- [14:10] Datastore choice
- [16:23] Review
- [16:55] Can we improve?
Can We Improve How Lyft Handled Service Discovery on AWS In 2016? (Reaction)Setting Up 2019Serverless Is An Ops ModelTwitter Shows Slow MFA Adoption, Is Security Unusable? #shortsCan We Improve How CorpInfo handled IoT Events in 2017? (Reaction)How To Pick A Serverless Database For Your Project In 30 Minutes or LessWarrant CanariesRoad to AWS re:Invent 2019 // Amazon Athena and QuicksightYou Cant Blame EmUnexpected LessonsStop Your Password From Opening The Door To HackersLaw and The Internet
marknca |

Can We Improve How Lyft Handled Service Discovery on AWS In 2016? (Reaction)

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER