Hi all,

Novice full-stack dev here. I need your opinion regarding the tech stack + deployment of a greenfield, multi-tenant web app for which I have 2 interested customers (payment plan pending) whose pain points are resolved, with hope to have many in the future but not more than 10k users globally.

My initial impulse is to have zero deployment costs, with a dockerized monolith backend (hosted on an always-free Oracle cloud VM), an Angular frontend hosted per Netlight / Cloudflare, and database hosted on Supabase. The reasoning is that “if” I’ll have an increased demand, I’ll simply scale these services vertically, and maybe even go cloud-native in the future.

Competing with this thought are my AWS cloud skills from work, which push me to going completely serverless and using managed services to speed up development and not think about infra scaling and security down the line. However, if I do it right, with API GW, WAF, etc. I’ll incur costs from the get go (even with free tier) without having seen a single payment from the customer(s).

In your experience, which option would you recommend in such scenarios? Would you recommend I disregard the minimal costs from AWS and go cloud-first to prevent future headaches when I’m focusing on delivering features / adapting business logic, or should I experiment with all-free services to wait until I have enough customers that support putting in effort/costs to go cloud-native (given that all code needs to be refactored / changed anyway)?

The application needs a REST API to perform CRUD operations on multiple related tables in a PostgreSQL DB, and start many task queue operations per user.

https://www.reddit.com/r/cloudnativeworkshops/s/dmvYXltHzW

I'm planning to use serverless for one of api service which built using Javascript and I have chosen AWS. Need suggestions for the framework? I'm planning to use AWS serverless framework. Is there any better alternatives?

Hey I'm having trouble getting Serverless to install my packages. This tutorial mandates using Docker:

https://www.serverless.com/blog/serverless-python-packaging

But that seems complex. Is there a workaround and is Docker very important for Serverless?
Thanks

I am big fan of serverless infrastructure, from Lambda, DynamoDB to Redshift serverless for ad-hoc data analysis. Recently in my work, I found it difficult to do JOIN across DynamoDB tables for daily report generation. So I digged a few options and want to share my two cents.

Sharing an infra that I am recently using to move multiple DynamoDB tables to Redshift, for daily JOIN and Data Analysis.

At first, I was using `COPY`, but it was difficult to handle nested maps. Then I changed to use AWS Glue Workflow. It could export data into S3 for archiving, and also opens the door for using Data Frame for complex data manipulation in the data streaming.

Feel free to comment and share your ideas. https://medium.com/@zizhao/using-aws-glue-to-stream-dynamodb-to-redshift-serverless-d339f79c34ff

I’m working on a new project and am thinking of using several of Scaleway’s serverless services. I can’t seem to find much on the internet about people’s experience with it. Therefore I wanted to ask if anyone here uses them or perhaps evaluated them and decided against it.

I've been digging into some research on serverless performance, and two issues stand out that I'd love to get this community's insights on:

1. Memory Allocation: The "Serverless in the Wild" study found that 95% of serverless function executions use less than 10% of allocated memory. In your experience, how accurate is this? Are we over-provisioning out of caution, or is this a limitation of current serverless platforms?

2. Cold Starts: Especially critical for low-traffic functions or those using less common runtimes. How are you balancing the trade-offs between cost and performance when dealing with cold starts?

I'm particularly interested in:

• Your strategies for right-sizing function memory. Are you using any specific tools or methodologies?
• Techniques you've found effective for mitigating cold starts. Provisioned concurrency, keep-warm pings, or something more novel?
• Your thoughts on how different cloud providers handle these issues. Have you seen significant differences between AWS Lambda, Azure Functions, Google Cloud Functions, etc.?
• For those working on larger serverless projects, how do these issues scale? Are there unique challenges or solutions at scale?

We are using `serverless-webpack` at my company, and we're planning to upgrade from Serverless Framework v3.39 to v4.4.6. The motivation for this upgrade is outside the scope of this question.

According to the Serverless website, v4 includes native TypeScript support with ESBuild, and plugins that bundle code, such as `serverless-webpack`, need to be disabled unless we opt out of the default build process. The relevant documentation can be found [here](https://www.serverless.com/framework/docs/providers/aws/guide/building).

I want to continue using the `serverless-webpack` plugin by opting out of the default build process, but when I try to install the plugin with Serverless v4, I receive an error indicating compatibility issues:

npm install serverless-webpack u/latest
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: ingest@1.0.0
npm ERR! Found: serverless@4.4.6
npm ERR! node_modules/serverless
npm ERR!   serverless@"^4.4.6" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer serverless@"1 || 2 || 3" from serverless-webpack@5.14.2
npm ERR! node_modules/serverless-webpack
npm ERR!   dev serverless-webpack@"^5.14.2" from the root project

I've reviewed the plugin page on npm (https://www.npmjs.com/package/serverless-webpack), but I don't see any clear indications that the plugin is incompatible with Serverless v4. I also tried using `--force` and `--legacy-peer-deps` flags during installation, but while this was successful I don;t feel confident in the resiliency of this solution.

Question:

• Is serverless-webpack no longer compatible with Serverless v4?
• If so, what would be the recommended workaround for keeping Webpack as our bundler in Serverless v4?
• Have you done the conversation from V3 to V4?
• Should I move my whole solution to Esbuild instead of trying to brute force Serverless V4+ and Serverless-webpack

Any help would be appreciated!