11:30 to be honest, even if some backend or frontend developer doesn't know about this dev ops stuff, I would still highly encourage them to learn it. Knowing how some of this stuff works make you realize what problems these managed services solve and help you decide if you need to use them or not. It also makes you realize not every app needs to be deployed into fancy serverless behind CDN setups with agressive caching etc. There are many apps like private dashboard apps that need a simple deploy to a VM because you don't have to worry about CDN, scaling or anything like that. You can also get a lot more performance for the same price if you go for a VM instead of a managed service, but of course you have to do everything yourself. That part might be fun for some people, but tedious for others. Learning all of this stuff really helped me advance beyond just frontend development and it's nice to sometimes step outside of my regular frontend work. It's another set of skills that can help me advance my career.
When I search for something on yt and I see that you have a video covering it. it's kind of a certainty I'm clicking on that video! You have a way of presenting concepts, problems and their solutions in a way I have yet to find the words to describe. Thank you for amazing content. Your effort is truly appreciated!
It's crazy how building stuff still can be such a pain in the ass with all these technologies and tools available. Thanks for the honest and down to earth videos, I have been learning from your journey.
Awesome video!! really like these sst vs amplify videos and you breaking it all down, can't wait for the next one. I'm gonna make the switch to SST. Even though it looks hard and will require a lot of learning, it'll be worth it long-term. I hate the idea of not knowing if you'll face a bug in the future that you can't fix because it's a managed service. Having the freedom to be able to fix your own bugs is so important.
As always a great video ! I would love to see you explore more SST. For example trying to deploy a full stack ( Database/backend/front/bucket/ses/...) through SST, to see how sturdy the stack is and also how to understand Infrastructure as code more :)
I find it so interesting to see your message on every video of Web Dev Cody. Later, I got to know about you. It's a great appreciation, just a shout out from me regarding your efforts. Cody is giving great contents and you are cheering him up is great motivation.
Hey man, i been following your videos, and it brings joy whenever i see new uploads, i learned something new. Thank you for the effort. Looking forward for new videos.
It is still possible to use aws amplify but without their opinionated / locked-in devops infra. We will still be using aws amplify but we will be deploying on vercel with nextjs
Great video! I have a dev ops background but was holding off on sst for a while. Glad to know it works well. I'll try it out tonight and get offa vercel
Verify the policies manually if you care about least privilege. I saw in the docs that binding a S3 bucket gives the wildcard permission to that lambda. So way more lax by default than for example cdk.
Very impressive! I’m using vercel free tier but deploying to AWS is fascinating. Would you consider making a video of what AWS tech to learn to understand enough to maintain SST? If not then that’s fine. It’s been couple weeks and curious to know the cost. Thanks!
Thank you for the awesome video. I took your course before and amplify used to work. I recently revisit the course and tried to use amplify again with nextjs 13.4 but it seems amplify isn't working to build and deploy. Do you still recommend using SST? SST dev site seems to be getting away from CDK soon.
Interested to know why you don't use digitalocean instead of aws with the benefits you mentioned. I'm in the same position trying to get a cheap scalable solution for many small side projects that will ideally scale easily and currently using DO as it is so much easier.
Because I use other aws services such as s3, ses, cloudwatch on my project and I’d rather not have to log into multiple dashboards to manage a single application if possible
Appreciated, you kind of answered also later on in the video. I've been following along carefully with this project deployment because you clearly know your stuff, appreciate the content.
is there a recommended load balancer for use like at 10:18? i know how to get nginx to do this on a local machine, but i don't know how to translate that to a modern stack - i figure another aws intermediary
Super useful to see. Do you know how quickly sst meet feature parity with vercel? PPR looks particularly interesting to me. As a side note, what's the reasoning behind using prisma? It looks like it caused issues because of that weird custom binary thing. Something like drizzle or typeorm make more sense to me as they are just executing plain sql queries. I see almost every nextjs example online uses prisma, but it just doesn't seem right to me.
It looks pretty good and I like the idea. Which AWS service do you have to integrate this with, S3? All the docs say just run these commands, but don't say which AWS tier/product you need.
Amplify builds your next app using a Linux container for you, similar to all of these hosted services, so the binaries were correct. I will say I’m not sure why I needed to modify the prisma schema generator… maybe that wasn’t needed after all?
@Hi,I need to know whether the logs for lambda are stored in log groups or not.I have deployed my NextJS application through sst ,but when I examining the lambda function created log groups in cloudwatch it is not created and there is no logs created by that lambda
Serverless framework is a thin wrapper behind cloudformation, but sst is an extension on top of cdk. I think sst gives a better dev experience for sure because cdk is all in typescript which gives the nice autocomplete, it’s just a bit more to learn maybe?
3:18 That is worry some to me. Because that means that the Amplify abstraction isn't doing a good enough job of hiding the actual resources used. And since you cant manage/see them in your regular AWS console, that is a problem. Curious, how did you find out it was a naming conflict? Or is it just your domain name? Because that would make sense.
database is free for right now (planetscale), infra costs is like $2 a month or less, and openai is $0.02 image generated (I charge $0.05 per image). so hosting is cheap. stripe is 3.5% of transactions plus a $0.50 fee.
![[Full] 4 ต่อ 4 Celebrity EP.910 | 22 ก.ย. 67 | one31](http://i.ytimg.com/vi/4TR3MVpOiw8/mqdefault.jpg)
11:30 to be honest, even if some backend or frontend developer doesn't know about this dev ops stuff, I would still highly encourage them to learn it. Knowing how some of this stuff works make you realize what problems these managed services solve and help you decide if you need to use them or not. It also makes you realize not every app needs to be deployed into fancy serverless behind CDN setups with agressive caching etc. There are many apps like private dashboard apps that need a simple deploy to a VM because you don't have to worry about CDN, scaling or anything like that. You can also get a lot more performance for the same price if you go for a VM instead of a managed service, but of course you have to do everything yourself. That part might be fun for some people, but tedious for others.
Learning all of this stuff really helped me advance beyond just frontend development and it's nice to sometimes step outside of my regular frontend work. It's another set of skills that can help me advance my career.
When I search for something on yt and I see that you have a video covering it. it's kind of a certainty I'm clicking on that video!
You have a way of presenting concepts, problems and their solutions in a way I have yet to find the words to describe.
Thank you for amazing content. Your effort is truly appreciated!
It's crazy how building stuff still can be such a pain in the ass with all these technologies and tools available. Thanks for the honest and down to earth videos, I have been learning from your journey.
Awesome video!! really like these sst vs amplify videos and you breaking it all down, can't wait for the next one. I'm gonna make the switch to SST. Even though it looks hard and will require a lot of learning, it'll be worth it long-term. I hate the idea of not knowing if you'll face a bug in the future that you can't fix because it's a managed service. Having the freedom to be able to fix your own bugs is so important.
As always a great video ! I would love to see you explore more SST. For example trying to deploy a full stack ( Database/backend/front/bucket/ses/...) through SST, to see how sturdy the stack is and also how to understand Infrastructure as code more :)
Amazing job babe. Super helpful.
Lmaoooooooo I think we should all refer to him as babe now
You better back off before someone I know comes at you
@@WebDevCody Hey now.. Didn't want to start any trouble or nothin.. Just appreciating what you contribute to the community!
@@WebDevCody shhhhhh 🤫 you’re OUR babe now, just let it happen 😂
Great job babe!! I'd like to see a follow-up video to see if it finally works for you.
Eyyyyyy!!!! he is OUR Code Babe now 😂 I love it!
Dude, another great video! You're really saving me time, again!
Thank you and keep up the good work 💪
Thanks man!
Good job babe!!! You’re doing great!
I find it so interesting to see your message on every video of Web Dev Cody. Later, I got to know about you. It's a great appreciation, just a shout out from me regarding your efforts. Cody is giving great contents and you are cheering him up is great motivation.
@@tempaccount8256 you sure it's not his gf?
@@SamOween yes she's his wife
@@tempaccount8256 awwww thank you so much! I appreciate this.
@@SamOween I am his wife :)
Hey man, i been following your videos, and it brings joy whenever i see new uploads, i learned something new. Thank you for the effort. Looking forward for new videos.
It is still possible to use aws amplify but without their opinionated / locked-in devops infra. We will still be using aws amplify but we will be deploying on vercel with nextjs
Great video! I have a dev ops background but was holding off on sst for a while. Glad to know it works well. I'll try it out tonight and get offa vercel
Verify the policies manually if you care about least privilege. I saw in the docs that binding a S3 bucket gives the wildcard permission to that lambda. So way more lax by default than for example cdk.
nice to see DigitalOcean here. what do you think about hosting a NextJS app on DigitalOcean instead of AWS?
Very impressive! I’m using vercel free tier but deploying to AWS is fascinating. Would you consider making a video of what AWS tech to learn to understand enough to maintain SST? If not then that’s fine. It’s been couple weeks and curious to know the cost. Thanks!
Loving these videos on deployments! Out of curiosity which database are you using?
planetscale
@@WebDevCody thank you
Thank you for the awesome video. I took your course before and amplify used to work. I recently revisit the course and tried to use amplify again with nextjs 13.4 but it seems amplify isn't working to build and deploy. Do you still recommend using SST? SST dev site seems to be getting away from CDK soon.
Interested to know why you don't use digitalocean instead of aws with the benefits you mentioned.
I'm in the same position trying to get a cheap scalable solution for many small side projects that will ideally scale easily and currently using DO as it is so much easier.
Because I use other aws services such as s3, ses, cloudwatch on my project and I’d rather not have to log into multiple dashboards to manage a single application if possible
Appreciated, you kind of answered also later on in the video. I've been following along carefully with this project deployment because you clearly know your stuff, appreciate the content.
Awesome video!
is there a recommended load balancer for use like at 10:18?
i know how to get nginx to do this on a local machine, but i don't know how to translate that to a modern stack - i figure another aws intermediary
Just curious, it’s possible to use SST to develop a multi tenant application?
Super useful to see. Do you know how quickly sst meet feature parity with vercel? PPR looks particularly interesting to me.
As a side note, what's the reasoning behind using prisma? It looks like it caused issues because of that weird custom binary thing. Something like drizzle or typeorm make more sense to me as they are just executing plain sql queries. I see almost every nextjs example online uses prisma, but it just doesn't seem right to me.
I'm starting to look into using drizzle ORM instead of prisma due to all this rust stuff honestly
13:02 can you please show us the updated billing and how much cost reduction happened
Thank you
Would love to use Vercel but what do you do if your database is in an AWS VPC? Seems like there is no secure DB option to use Vercel (or even Amplify)
It looks pretty good and I like the idea. Which AWS service do you have to integrate this with, S3? All the docs say just run these commands, but don't say which AWS tier/product you need.
the OpenNextJs for sst will spin up cloudfront and lambdas, probably some other random things under the hood.
Why did the prisma bug not occur in amplify, in terms of the target?
Amplify builds your next app using a Linux container for you, similar to all of these hosted services, so the binaries were correct. I will say I’m not sure why I needed to modify the prisma schema generator… maybe that wasn’t needed after all?
@Hi,I need to know whether the logs for lambda are stored in log groups or not.I have deployed my NextJS application through sst ,but when I examining the lambda function created log groups in cloudwatch it is not created and there is no logs created by that lambda
Yes there is a log group for the server lambda functions
Rerouting and caching is simpler on Cloudflare, compared to the Cloudfront + Digital Ocean setup.
do you recommend buying a course on devops or just get my hands dirty trying stuff out?
Both might work well.
question, did you consider serverless framework before going with SST?
I find myself in this spot atm and not sure which one to go for.
Serverless framework is a thin wrapper behind cloudformation, but sst is an extension on top of cdk. I think sst gives a better dev experience for sure because cdk is all in typescript which gives the nice autocomplete, it’s just a bit more to learn maybe?
Can you show the exception message from cloudwatch ?
3:18 That is worry some to me. Because that means that the Amplify abstraction isn't doing a good enough job of hiding the actual resources used. And since you cant manage/see them in your regular AWS console, that is a problem. Curious, how did you find out it was a naming conflict?
Or is it just your domain name? Because that would make sense.
Domain name, but even so if I had a separate aws account, the domain would be fine
@@WebDevCody Aha, well in that case my original comment stands.
Cool!
how much does it cost to run your sass monthly since you deploy it in terms of database and openAI??
database is free for right now (planetscale), infra costs is like $2 a month or less, and openai is $0.02 image generated (I charge $0.05 per image). so hosting is cheap. stripe is 3.5% of transactions plus a $0.50 fee.
Why not just run on Digital Ocean?
I purcchased the course.
too bad that api routes not working after deploying with sst, what makes this way kinda useless.
You sure they don’t work? What version of next are you on?
I am curious about the cost of bandwidth costs with this!