Answer the question
In order to leave comments, you need to log in
How to build the right architecture on AWS for web applications?
Hello. The serverless hole turned out to be very deep, 200+ Amazon services are confusing.
Goal: Deploy an AWS application written in Vue3 (plus native SSR or nuxt), execute "backend" functions in Lambda, and also use one of the Amazon services as a database. Thus it would be desirable to have adequate CI/CD.
Options I have found:
S3, CloudFront. Easy, all the tutorials and diagrams talk about this. I uploaded my build, everything works. However, after each commit, you do not want to do manual work on the deployment. Either Amazon code delivery services or AWS Amplify come to the rescue here. But is it worth it?
There are also options with EC2, AWS VPC, thousands of them.
How to find the best solution of all? Again, you just need to build a front that uses SSR, and this front, in turn, will work with other Amazon services. I want to do it quickly, safely and inexpensively (if possible). Now the eyes run wide, in which direction to look at all, a lot of material, a lot of services, a lot of opinions and the same number of absolutely non-obvious moments.
For the test, I want to make a serverless SSR version of the blog, which is visited by 5 people a month (haha), there will be no special load, but the experience is interesting. The blog will be rendered on the server, I want to receive data using API Gateway, Lambda and DocumentDB.
I would be grateful for any help, the topic is very interesting.
Answer the question
In order to leave comments, you need to log in
This can be viewed from two points of view - practical and educational. If the goal is to learn something new, then start slowly. I would start in frontend, it's easier to deploy it in S3 than to learn serverless. Will work - add Cloudfront. It will work - add CI / CD, the easiest way is based on GitHub.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question