Building a Multi-Tier Serverless Application in AWS
The course is part of these learning pathsSee 2 more
In this course, we will create a multi-tier serverless architecture on AWS using Amazon API Gateway, AWS Lambda, AWS Step Functions, and Amazon Polly text to speech. This is a hands-on course where you will learn how to create serverless functions, data access, business logic, and integration layers on AWS. Also, you will learn how to create a presentation layer for your application using the client SDK generated by Amazon API Gateway. We will then host the application on Amazon S3.
By the end of this course, you will be able to recognize and implement an end to end workflow built in the Amazon Cloud using Serverless components.
This course is intended for developers or DevOps engineers who want to create serverless applications on AWS, or who may be considering migrating their existing web applications to AWS.
The GitHub repository for this course is available here: https://github.com/cloudacademy/advanced-api-gateway-resources.
- [Female AI] Tina Brown, thank you for your order. It will be ready for pickup in 15 minutes.
I hope you heard that response coming from the webpage. As you can see, there are some console logs from the webpage that are put in there for debugging. If I open the Network console, you can see all the methods that have been called. OPTIONS method is always called first to make sure we have access to other methods since we enabled calls earlier in our API. For POST, you can see the params that we sent and the response, which was received to here, the executionArn and startDate of the state machine. Then for the GET call, we pass the same executionArn that was returned by the POST call as a query string parameter and received back the current state of the state machine including all these properties, and output from which we get back our order status. The last GET call is by the webpage to S3 to get the orderstatus.mp3 file from S3 to play it back, and which was placed there by the lambda function in our state machine. Now if we look here at the Step Function Console, we can see the last execution initiated by the webpage and see how it took the success path and notified the user with custom lifelike speech notification. I'll go back to the webpage now and let's now change the credit card number and name to submit another order.
- [Female AI] Tom Brown, sorry, your payment didn't go through. Please, try again.
Okay, as you saw, this order failed and the user notified. If you go to the Step Functions Console, you can see the state machine execution of the last order and it's following the Cancel path. If anything were to go wrong, you can easily debug it through these step functions as it logs every step. Okay, now our presentation layer is complete and we have successfully built a multi-tier web application on AWS using Cerberus architecture. Hope you enjoyed it.
Tehreem is a Sr. Software Engineer with passion in Cloud Technologies, Big Data analytics, Software Testing and Automation. She has over 10 years of work experience comprising of her tenure at ServiceNow, Microsoft and Harmonic Inc. Most recently she has been developing learning content in-line with the emergence of Public Clouds and XaaS platforms with focus on AWS, Microsoft Azure and GCP. Tehreem resides in BayArea, CA with her family and when not working she enjoys nature/outdoors, movies and fine dining.