SST in 100 seconds
ฝัง
- เผยแพร่เมื่อ 1 ต.ค. 2024
- SST serverless stack is an open-source infrastructure-as-code tool for building on AWS with TypeScript. Learn how to easily manage resources on AWS and handle deployments for JS frameworks like Next.js, Astro, Svelte, and more.
#webdevelopment #javascript #100secondsofcode
💬 Chat with Me on Discord
/ discord
🔗 Resources
SST on GitHub github.com/ser...
SST Docs sst.dev
50 AWS services explained • Top 50+ AWS Services E...
Serverless was a mistake • Serverless was a big m...
🔥 Get More Content - Upgrade to PRO
Upgrade at fireship.io/pro
Use code YT25 for 25% off PRO access
🎨 My Editor Settings
- Atom One Dark
- vscode-icons
- Fira Code Font
🔖 Topics Covered
- How to build serverless apps on AWS
- What is Amazon Web Services?
- What is IaC infrastructure-as-code
- Deploying Next.js to AWS lambda
- Deploying SvelteKit to AWS lambda
- SST quickstart tutorial
How to accidentally spend your life savings on Cloud Infrastructure in 100 seconds.
The same is true for all other infra as code solutions. You have too much power on a single file :)
Totally
lmaooo
Pretty fun comment 😅
My biggest fear!
That's actually pretty awesome. Will we get a beyond 100s or something on this?
Likely on beyond fireship if anywhere
@@wizard-pirateno he has done beyond 100 seconds in his own 100 seconds videos
Pulumi is even better 😂
@@uziboozy45401:31
A full-stack app tutorial I made last year using SST: th-cam.com/video/-845vxcf3dA/w-d-xo.html
Perfect! I was looking for a faster way to lose all my money!
AWS already takes care of that pretty well 😂
Be careful about the AWS bills :)
yeah, let's add another framework and abstraction over the absurdly over engineered and tedious SDKs of amazon...
While it seems nice, I would prefer to use AWS CDK before I use this. Don't know why I should use another abstraction layer... CDK already has some drawbacks where escape hatchets are needed to do everything Cloudformation could do. SST will probably be a nightmare if you want to do something that is not supported.
And to be honest if CDK is too hard for you, you should probably not deploy to AWS... It is important to know what is deployed and how it is configured to not wake up to bills beyond your imagination.
You can import any cdk native construct into a SST stack. I have lots of custom cdk constructs baked right into my SST stacks. So when sst doesn’t support something you can just revert to cdk. Also In my opinion the development experience is way better using SST which was my main reason for moving some of my projects over to sst.
SST is faster, you use live lambda development to run your lambas locally with 10ms updates. You can bind resources to make the IAM policies connect without having to write all the boilerplate and you can always drop down to the CDK level whenever you want. CDK is made for deploying your infrastructure in the cloud, SST lets you do that PLUS makes it easier to build a full stack app (connect your front end and back end etc)
I was using SST before, moved to CDK since they have level 2.
I’m surprised this framework still exists.
Sst can use any cdk constructs with no problems, it only adds stuff over cdk that makes it even better
I am impressed with how well these tools can abstract the architecture. It's what AWS SAM fell short of. It's funny how almost all are JS based, as Serverless-Framework, despite that Go and Python SDK for AWS are also very robust.
Full-stack devs eating good when they don't have to write and manage code in anything other than JS/TS
A large part of it is purely due to TypeScript having good support for static analysis + the pre-existing ecosystem. Python does finally have real type hint support since a few versions ago, but it's still years behind in capabilities.
go sucks, go with rust
@@amogus3023 python devs think that types are evil
@@Miles-co5xm agree
If you’re not (just) into AWS, Pulumi is pretty cool too. Although I prefer Terraform myself
I was also going to mention this. I'm not sure why I would use SST over Pulumi if it is more generalistic and more flexible
I really like crossplane, because then I can manage everything in kubernetes
@@Jonathan1234000 why would you want to manage everything in Kubernetes? 😂😂😂
The things I learn from the comments section...
@@uziboozy4540 To a man with a hammer, everything looks like a nail...🤦😀
Last time I was this early, react was actually useful
Wait, so I shouldn't learn React?
@@orvvrodon’t let anyone on the internet change your mind bro
@@orvvro React was great in its time, and has been the backbone and inspiration for many new and better frameworks/librairies, but today many people consider it a shitshow that should be avoided if possible for something better.
You can still learn it, it's still useful, but there are definitely better alternatives out there now
@@wisdomelueFuck but I need a job and react is still popular
@@orvvro yes learn react it’s still popular and strong but you should also learn next.
You mean awful web services?
The easier something is to spin up the more magic happens behind the scenes and the greater chance it will become a headache
Yeah with raw AWS it takes ages to correctly set something up and by that time you're used the headache.
@@BboyKeny
This isn't true.
Amazing, my least favorite part of AWS going on AWS so glad we can skip that part.
Sad its just for aws.
Pretty cool option if you're only using AWS. Personally, we use Pulumi at my company since it also allows us to write our Kubernetes infrastructure in addition to AWS pretty easily. And it's also capable of working with other cloud services as well. Maybe a future video on Pulumi? 👀
I just recently started using Pulumi and I love it.
Nitric is similar to SST, but built on Pulumi and with support for multiple languages and clouds. I'd be curious on your oppinions if you have time to check it out
Oh this looks so nice. I was thinking of using terraform but it seems like pulumi is more light weighted and easier to use than terraform.
@@sungjuyea4627 For writing your own IaC packages to self manage, yes. You won't get all the off-the-shelf modules that exist in the Terraform community.
Doesn't AWS CDK do this exact thing? I've tried SST and I see it as a layer over CDK.
Let's get him to 3M, he deserves it!
Used SST like 3 years ago for some cron jobs and it made my life so easy! Love it
its from 2022, you liar
Started using SST a week ago, absolutely loved their full stack guide, caught me up on everything I needed to know. Now building my website and SST makes it so much easier and faster to work with your AWS resources and get the front and backend to connect together. Highly recommend!
What are your cost predictions? IaC tends to add a lot unnecessary costs for a minimal solution.
@@liamlouw4643 IaC just spins up resources, you just pay for what you use as usual. I've still paid $0, comletely within the free tier right now while developing.
yup, i only spent 0.5$ because of the custom domain thing needed to use aws hosted zone in Route 53, my lambda, s3, etc for the backend and fronted is still on their free tier. people seems to be scared off using sst, but they just never tried it
how is it different from aws cdk? what does it bring to the table?
@@amackzie
aws cdk is just infrastructure as code for aws, whereas SST is IAC and also helps connect your frontend and backend. It's a powerhouse, letting you build a full stack app in AWS with the entire flow covered.
also it has live lambda development - you can test your lambdas locally form your PC so you're not charged for the whole runtime in aws, it connects your aws account and your local environment so you're still making requests to/from aws but the code runs locally so you still test it with the iam policies etc. Better than SAM as it was 10 ms updates for those lambas instead of 1-2 seconds to upload to lambda.
So.. a JavaScript "framework" to simplify deploying JavaScript frameworks (onto AWS).
javascript to describe infarastructure for javascript full stack blog app about javascript)))
Guys.... don't forget... it support LOOPS and RECURSION :)
I love how there is a framework for everything, you have to learn new way to do stuff for every small functionnality. And that in the end you may need another framework to help to blend two distinct framework together as not any of them do everything but is a mess to use
Yep
Before SST: "Shit... This bug has cost me my entire day"
After SST: "Shit... This bug has cost me 200K in AWS bills"
I’ve been using SST for years now. Very dependable (thanks to CDK) and incredibly fun to use!
Do you need AWS knowledge?
Isn't this what terraform is designed to do? It feels like reinventing the wheel using a different language. No problem with it though as it makes the entry barrier lower
wow this looks a lot easier than dealing with the clusterfuck of inconsistency that is cloudformation
Would love to see a full svelte build in a longer form video
Reinventing the wheel... AWS has something called CDK which works exactly the same way. I'm sure that CDK has more services supported and can be written in different languages. And what about more complex solutions where you need adjust the settings for VPC, load-balancer etc?
SST is literally powered under the hood by CDK 0:42. Also, if a Construct is missing in SST, you can use the ones from CDK where needed. As a CDK user, I think SST can have some very interesting use case if you are dealing with Web Apps whereas CDK is better if you are dealing with Step Functions, Batch Jobs and the like (think ML which is what we are doing the most)
@@timvauchersorry, somehow I missed this fact (0:42). So, in short recap: SST is simplifier of CDK, which is simplifier of CloudFormation, which is simplifier of AWS API? 🤔
@@lukcicPLI think your recap is perfect.
It’s not a replacement, but adds quality of life & still allows you to access what lies beneath.. decent compromise
I really like all these systems for personal or smaller projects, but when I try to use them at work we almost ALWAYS revert back to terraform/cloudformation because those systems are not powerful enough or there are some small important things missing
That's correct. Even serverless framework falls short. Everytime we try to use these tools we always resort to Sam + cdk in the end.
Atleast with this tool it's just an abstraction layer on top of CDK so you are able to write raw CDK code aswell.
Next video idea: JDSL in 100 seconds
At this point I'm just amazed/sad/losing my mind - how often we make something simple become very complex so we need to simplify the complex again...which we then make complex again.
It's literally never ending.
With time there always is a fix for the fix for the fix for the... It's literally IT inception.
Like damn. Remember when we got annoyed for using tables to design websites? Ha.
You should do OCaml next!
I'm gonna stuck with CDK
This is super cool. We have our own mono repo that uses CDK but it has been difficult to maintain and the developer experience has been terrible really. This solves all of that, I love it.
SST is amazing, one of my favorite tools!
We use sst at our place of work and we're in love with it!
After AWS SAM and Amplify, I’m not holding my breath. Terraform CDK and AWS CDK are pretty nice though. Pulumi is too brittle in my experience.
This is such a vendor lock, what if you decide to move away from Amazon if they kick you out for example (say your app doesn't comply with their terms or something), then your app is RIP.
This is really interesting
I don't even know what this is but I am watching it.
Been a huge fan of this project since I found it almost a year ago! If the maintainers are reading this, great work and thank you!
What's the advantage of SST over AWS CDK?
still not enough to make me touch aws again. render, railway, and others are still much more dev friendly.
As a cdk developer myself i love this approach and cannot wait to try it out with sveltekit
I was here before Dax
Awesome!
Finally a web service that I’ll actually use 😂
Moving from Serverless Framework to SST is a game changer for me.
My main concern with serverless framework is the amount of needed permissions. Does SST fix that?
@@marcelsantee1809 I made an SPA with Lambda, DynamoDB, ApiGateway, S3 and CloudFront in SST, and I never have to touch IAM. But I think if you start making something more complex than that setup, then eventually you'll have to handle IAM, especially for the AWS services that are not directly supported by SST's abstractions.
Very good idea since we have Terraform CDK available, we can create this kind of beautiful frameworks using TS/JS, Python and many more... and not only for AWS
Just we have to keep in mind TF CDK is not production ready and still not GA, But Pulumi seems to be a good alternative to achieve this too :)
Next on the code report: large groups of developers enter indentured servitude at Amazon after racking up five figure AWS bills.
God I'm glad I'm not a webdev so I don't have to deal with any of this
Soooooo much better than working with Cloud Formation, and I can see how this is an evolution of working with AWS's CDK. Ability to view logs locally is a game changer.
Is there anything like this for GCP?
How is it better than the normal CDK code?
When is the video in JDSL?
Meanwhile AWS CDK: Am i a joke for u. But seriously why? It's just an abstraction on aws cdk which is already an iac tool?
Yeah I dont get it, it looks exactly like CDK...
So SST is a layer over CDK which is a layer over CloudFormation which is a layer over AWS Infrastructure.. Nice..
F in the chat who thought he meant space simulation toolkit
First
Simply awesome. I very well understand that it takes more efforts to explain concept in less time than making full explanation video
Clojure next
Looks better than Pulumi
So, Terraform, basically ?
next video Fireship in 100 seconds
CDK natively supports hot reload and streaming of relevant cloud watch logs. I like CDK a lot so excited to try SST. Damn good 100 seconds
Why not just use CDK directly? This doesn't look any more abstracted than CDK.
I'm actually using SST over CDK since this is the only “IaaC” that supports NextJs 13. And I am avoiding amplify since that comes with a lot of overhead.
So basically Pulumi, but limited to AWS and TypeScript?
Oh. Too bad I use GCP… which I like to think of a the AWS that makes some kinda sense instead of being a cluster of random web services.
Blender in 100 seconds please?
There's also Pulumi, an Infrastructure as Code framework written in TypeScript.
So you can write IaC code without learning Terraform.
Haven't tried it out yet though.
Fire ship can you cover wing please, they are making a really cool product that is similar to SST but allows you to test applications locally.
Is there anything similar for azure? ;-;
Claim your “here within an hour” ticket right here🏆
bot
Yeah, definitely I need an extended version of this
SST?
SOCIAL STUDIES?
NICE!
I cannot imaging you explain everything in 100s; superb!!
AWS WTF no thank you
Social Studies 😅
Full tutorial!
I like how I can understand 6% of what is being said and yet enjoy it
He has definitely mastered the art of making things seem easy, even when you don’t understand what he is saying 😂
Yup, am very new to web dev and just starting to learn React. All of what was said in this video flew completely over my head lol
That sounds interest...
*"AWS"*
... well I guess that's a nope for me.
Do Convex next
rip Vercel
Man what about cost?
If you push every local dev build to AWS, then AWS cost a lot. Or they will not charge for dev run?
Seems to be pretty perfect for quick prototyping and SaaS Development. Nice!
Why would you use SST over Terraform though?
There's a good idea for a future video: SST vs. Terraform. 😂
Why would you use Terraform over Pulumi?😂
Hcl has limitations as a declarative language tha some people have recognized to make tools such as pulami to create infrastructure through a coding language instead. Things like if statements, for loops, testing etc are more difficult to perform on terraform or have workarounds that aren't native to the solution, a tool such at SST or pulami does have those native options but obviously are not as battle tested as terraform.
at least for this tool, the more interesting video would be comparing this to pulami, as I don't see the use for it other than it seems specifically to target front-end devs that use tools like vercel to deploy out infrastructure.
Use SST at work and love it ❤
0:31 - hey wait a second, why does it say "SONY" on the AWS console?? Is this some kind of conspiracy?
Ahh classic Serverless Script Tunnel
Truly my favourite
What AWS Amplify tried to be 😂
Errors in the console on 'Amplify push' was not fun!!!
Bro pullin straight nerd content while bringing everybody to laugh
isn't this jus terraform, cloudformation, AWS CDK? nothing new
Nice. Is there an SST for Azure?
you should do "spwn in 100 seconds" because that language is really unique
Sounds like a 1 click button to decimate your bank account.
I'm in 😊
Within 40 seconds I was like "SHUT UP AND TAKE MY MONEY"
While this is interesting, I'm always wary of these layers-upon-layers of magical abstractions. All cost concerns aside, which can easily be controlled and aren't the boogyman man of the comments might suggest; you're not learning enough about the underlying infrastructure you're maniuplating. All abstractions come with this cost. Even with CDK, which I've adopted and started using because you need *some* sort of IaC tool for automation, you've got to understand what's happening under your code. To me, if you're strictly AWS, CDK is the way to go, and adding another layer on top of that might be easier, but you learn and understand less of the consequences of what you're executing.
All that being said, we're mired in frameworks, built atop frameworks, embedded with endless layers of abstraction and configuration. There's a shiny new toy every-other-day. You can chase your tail around for years and never settle on "THE stack"...and all of these toys achieve the same thing, in the end. At what point do you select "the best" tools and stick to them for more than a few months, or even a few years?
As neat as this is, I prefer to stay as close to the "bare metal" as possible, while accepting that the market will push you into certain things that you have no choice in adopting. Keep it as simple as possible, even if it's more difficult and requires a little more code and understanding. These frameworks come and go, seemingly overnight. If you stick to strong fundamentals and as few abstractions as possible, you'll waste less time and build more stable environments.
SST -> CDK -> Cloudformation Template -> AWS provision resources 🤣 time will mess this up per version release
Can you do a 100s fireship video for Objectbox NoSqlite DB ?