- Serverless Design Patterns and Best Practices
- Brian Zambrano
- 211字
- 2021-08-27 19:12:07
Viewing the deployed web application
With everything in place, we can now upload our frontend assets to S3. We won't review the actual frontend React code, but if you're curious, you can take a look at that UI code in the GitHub repository at https://github.com/brianz/serverless-design-patterns/tree/master/ch2/ui.
Using the preceding aws s3 cp command, a final production build of the frontend code is uploaded to S3 and ultimately serves the content as requested by the CloudFront CDN. When the first page is rendered, a request is made to our serverless backend to get a listing of all coffee cupping sessions:
A very common issue, and one that people often forget about, is cross-origin resource sharing, which is a security measure put in place by browsers. Our serverless backend was set up to sidestep this issue, making development much quicker. For a real production system, it's best to only allow CORS for your own domain or, better yet, run the serverless backend on your own domain rather than the autogenerated domain from API Gateway. Running the serverless API on your own custom domain is possible using AWS API Gateway, but this is out of the scope of this chapter.
Clicking on a single row, the detail page for the particular session is loaded:
