sst-start-demo VS cloud

https://docs.serverless-stack.com and https://www.serverless.com/ can support next. However serverless-stack is too new and serverless framework looks promising but it uses an old version of serverless plugin.

I'm new to serverless and I've recently discovered frameworks like the Serverless Framework and SST. I've seen examples of Lambda functions where people interact with DBs like DynamoDB, authenticating users with Cognito and using API Gateway to map routes (these are all AWS-specific terms), which seems to me like you can pretty much build a CRUD API on top of this. However, I've also seen examples like this one where you can deploy a backend framework such as Nest.js as a single lambda function.

Hey all, recently I've been learning a lot about serverless APIs and I discovered frameworks like Serverless and SST which look great. I then also discovered that you can apparently deploy a Nest.js backend as a lambda handler -- here is a relevant article. Has anyone tried this? If you are looking to start working on a new project, is it a good idea to combine these together, or would you be better off just writing individual lambda handlers without a framework like Nest?

Hosting NextJS apps on AWS I would recommend https://docs.serverless-stack.com/ which has an inbuilt CDK pre-configured NextJS setup or https://registry.terraform.io/modules/dealmore/next-js/aws/latest

I highly recommend serverless SST. https://docs.serverless-stack.com/

> The ability to move between the frontend, backend, and infrastructure code without having to learn a different language is invaluable to every member of the team.

I'm actually quite skeptical of this claim. Learning a new language isn't really a big deal unless you are using relatively "esoteric" stuff like clojure or elixir which really require an experienced consultant to train your team.

With AWS Chalice, we've been able to ship production scale code (for govcloud) in Python without any one of us breaking the environment by simply using separate staging. We were able to get PHP/Javascript developers to use it with barely any downtime. In fact it was more or less appreciated from the clean and simple nature of Python right from the get go.

This feels like way too much engineering from the get go. Here's my workflow with AWS Chalice and its super basic (I'm open to improvements here).

- checkout code from github

- run localhost and test endpoints written in python (exactly like Flask)

- push to development stage API gateway

- verify it is working as intended and this is when we catch missing IAM roles, we document them. if something is wrong with our AWS setup (we dont use CDK just simply use the AWS console to set everything up once like VPC and RDS)

- push to production stage API gateway

All this shimming, typescript (rule of thumb is ~40% more code for 20% improvement through less documentation and type errors, only really valid in large teams) separate AWS developer accounts seems overkill.

The one benefit I see from all this extra compartmentalization is if you are working in large teams for a large company since you are going to discover missing IAM roles and permissions anyways and is part of being an implicit "human AWS compiler trying different stackoverflow answers".

Some positives I see are CDK but if you are deploying your infrastructure once, I really don't see the need for it, unless you have many infrastructures that can benefit from boilerplate generation.

Happy to hear from all ends of the spectrum, serverless-stack could be something I explore this weekend but there's just so much going on and I'm getting lot of marketing department vibes from reading the website (like idea to ipo and typescript for all) and to top it off

going to https://docs.serverless-stack.com/ triggers an antivirus warning about some netlify url ( nostalgic-brahmgupta09582d1.netlify.app) what is going on here???

documentation which is top notch

On a related note, shout out to https://docs.serverless-stack.com/ which is kinda like Serverless Framework except build on the CDK. Much more solid IMHO

ServerlessStack framework

You can use Serverless Cloud. See an example project here: https://github.com/serverless/cloud/tree/main/examples/with-nextjs

To show you how easy it is to use Serverless Cloud and Vercel together, let’s setup and deploy our CloudPics example application. It’s a React application built with Next.js that lets you upload photos which are stored in Serverless Storage, resized, and indexed in Serverless Data. The home page is visible to both authenticated and non-authenticated users, and it uses server-side rendering to improve SEO and performance for end users.

This will return a new app url that is completely separate from your personal development instance. Unless you’re testing, we recommend that you use that production stage url in your frontend so that any future changes you make to your api won’t break your app. We will leave the frontend piece as an exercise for you since it’s no different from any other frontend app you’ve worked with. For reference, you can take a look at the docs, and how that might look like in the examples directory.

Putting it all together, we’ve seen how you can easily add signup and login functionality to your app using JSON Web Tokens, and how to verify these tokens to protect your private endpoints. I hope this was a helpful introduction to how authentication works at a high level, and how it fits within Serverless Cloud. For more advanced use cases such as integrating with third party providers like Google, Twitter and Github, you may want to take a look at Passport.js or similar libraries that make it easier to authenticate your users. You can take a look at the complete example application here, and if you ever get stuck, visit our documentation.

In this article, you’ve seen how easy it is to use Serverless Cloud with MongoDB. You’ve learned how to create a Serverless Cloud app, how to create a MongoDB database using MongoDB Atlas, and how to connect your Serverless Cloud app to your MongoDB database securely using Parameters. The complete example app can be found in the examples repo, and more information about Serverless Cloud can be found in the docs. If you have any questions, feel free to reach out on Twitter.

GitHub repository

Serverless App Platforms And Feature Ceilings (Paul Swail, Serverless First) — An interesting topic in the cloud industry today… as cloud services get more complicated, will we see more Platform-as-a-Service abstractions built around them to make them simpler? Serverless Inc clearly thinks so, as they’re building their own Serverless platform now. But Paul notes the biggest downside to these platforms, what if you need to “break out”? What if you need more functionality than these services provide? I also recently put out a short Twitter thread on this same topic.