Let's write a Microservice using AWS Lambda (or maybe not).

Ғылым және технология

This video is an extended version of my AWS Re:Invent Dev Chat. In this video, you will learn how to design a microservice using AWS Lambda (and Lambda Layers) and the pros and cons if you chose to do so.
Link to sample code in the video:
github.com/chaotictoejam/aws-...
0:00 - Introduction
1:47 - The Problem & Quick Review
6:44 - Designing the Microservice
12:41 - Implementing the Microservice
19:20 - Pros
20:30 - Cons
28:47 - Takeaways

Пікірлер: 6

  • @nwachukwuchibuike42
    @nwachukwuchibuike42 Жыл бұрын

    Nice explanation of the serverless approach to creating microservices.

  • @DrJoanneSkiles

    @DrJoanneSkiles

    Жыл бұрын

    Thank you

  • @softcodemx1109
    @softcodemx1109 Жыл бұрын

    quite interesting your points of view, I would only add as an extra point that in the case of access to a file system is also charged separately, since access to temporary folders is limited and in case of exceeding the space is charged for the space.

  • @DrJoanneSkiles

    @DrJoanneSkiles

    Жыл бұрын

    Great point!

  • @marknielsen4494
    @marknielsen4494 Жыл бұрын

    Love your videos and practical insight. Thank you for all your efforts! Question... You have said in several videos that step debugging isn't available with Lambda. I'm confused by your statements because there are several ways to do lambda debugging. Could you explain please?

  • @DrJoanneSkiles

    @DrJoanneSkiles

    Жыл бұрын

    Thank you! You are right there are several ways to do lambda debugging, I may have said it poorly but what I meant was that the "traditional" step debugging that most developers know for walking through a bug/issue does not exist in an easily attainable way. One of Lambdas main strength is the tight integration with other AWS services this becomes the biggest pain when it comes to debugging, because on a local machine stepping through the process is almost impossible (without setting up emulators or other tools). Developers mindsets therefore need to change - we shouldn't think about local development the same way when working with serverless solutions instead we need to think "in the cloud". We should invest more on monitoring/logging so we can ensure we have appropriate visibility into our running AWS Lambda function.

Келесі