homepage
serverless-plugin-warmup
Our great sponsors
homepage | serverless-plugin-warmup | |
---|---|---|
16 | 1 | |
11 | 951 | |
- | - | |
7.2 | 8.0 | |
about 1 month ago | about 2 years ago | |
SCSS | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
homepage
-
Is Nestjs easy to understand for frontend developer who is good at Typescript, reactjs and familiar with express?
I highly recommend, with these types of credentials, go serverless and use https://sst.dev/ with https://nextjs.org/ . Stupid simple deployment, and SST’s (reasonably priced) paid arm, https://seed.run/, for ci/cd and deployment including great stage management, and nearly free logging and error observability.
-
Is anyone successfully using the CI/CD offering from serverless.com?
I've used seed.run with the Serverless Framework for 4-5 years. As I don't deploy to much I've stayed with the free tier and it all works perfectly. Try it out it won't disappoint.
-
How much vendor lock-in is there in the NextJS/Vercel ecosystem?
They have, at least SST, visit seed
-
What tech-stack to use for a solo dev that can prioritize product iteration and scale?
The backend is built with serverless.com (lambda, dynamodb, sqs, appsync). The good thing is that all the backend is stored in a file and you can deploy multiple stacks on the same account using seed.run . You don't really need EC2/Fargate when you have lambdas and you know that most of the time will be idle time. The same with cache I wouldn't think of it right now until you see the workload you are facing. Dynamodb once you understand it and have a proper design it's the fastest thing you can have. On my appsync calls I'm using Dynamodb as a cache because it's cheaper...
-
Do some developers actually, REALLY, have no local environment and run everything in AWS? Is the individual cloud dev environment a real alternative to having things running locally?
I run my personal project on AWS. I has been running for 4+ years now and I never had a local environment. I took the serverless route. That is appsync, lambda, dynamodb, sqs to build the stack. I'm using serverless.com to have all the resources defined in a yaml files which will deploy multiple stacks. I'm using seed.run to manage that part because it's much more simple than to do it manually.
-
Best managed graphql service for database + search?
How do you deploy your services on AWS? I'm a solo developer and have no issues with my backend. I use the Serverless framework so all services, lambdas, configurations is on a repository on git. I do all the deploys to a dev environment where I test my code and later on I deploy with a PR to my prod environment thanks to seed.run.
-
Structuring a Real-World Serverless App
Your repo setup can look different, but the general concept still holds true. You have to figure out if a file change affects an individual service, or if a file change affects all the services. The advantage of this strategy is that you know upfront which services can be skipped. This allows you to skip a portion of the entire build process, thus speeding up your builds. A shameless plug here, Seed supports this and the setup outlined in this post out of the box!
-
Working with Lambda Code
I use serverless.com framework with tests and deploy with seed.run. So I don't ever touch a Lambda in production. I also have 2 environments, one for testing and the other for production.
-
I have a serverless application with multiple services or stacks which behave as a microservice , I have a build.sh file which allows me to deploy specific service. Now , I want to automate my deployments using gitlab/github but only deploy specific stacks
I'd use seed.run . You can deploy multiple stacks on parallel or with dependencies. You can deploy from github ( 100% sure ) from gitlab I'm not sure. Worth checking it. I'm using the service for free and haven't had any issue.
-
What do you like/dislike about AWS services? What are the most common problems?
Building on top of it requires some knowledge but for me it has been worth it. I use serverless.com to manage all the infrastructure as a CF template. This has the benefit that I can deploy multiple test environments at will. I'm also using seed.run to do all the CI/CD ( also for free ) and doing all the monitoring with lumigo.io . And I build single pages applications that use Netlify.com to handle at that part. I do it to avoid less things to manage on AWS directly when the service is free (again) and really easy to use.
serverless-plugin-warmup
-
Structuring a Real-World Serverless App
We use the package.json at the project root to install the dependencies that will be shared across all the services. For example, if you are using serverless-bundle to optimally package the Lambda functions, or using the serverless-plugin-warmup to reduce cold starts, they should be installed at the root level. It doesn’t make sense to install them in each and every single service.
What are some alternatives?
LocalStack - 💻 A fully functional local AWS cloud stack. Develop and test your cloud & Serverless apps offline
serverless-python-requirements - ⚡️🐍📦 Serverless plugin to bundle Python packages
sst - Build modern full-stack applications on AWS
serverless-bundle - Optimized packages for ES6 and TypeScript Node.js Lambda functions without any configuration.
esbuild - An extremely fast bundler for the web
serverless-chrome - 🌐 Run headless Chrome/Chromium on AWS Lambda
Previous Serverless Version 0.5.x - ⚡ Serverless Framework – Use AWS Lambda and other managed cloud services to build apps that auto-scale, cost nothing when idle, and boast radically low maintenance.
serverless-plugin-warmup - Keep your lambdas warm during winter. ♨
lerna - :dragon: Lerna is a fast, modern build system for managing and publishing multiple JavaScript/TypeScript packages from the same repository.
Moto - A library that allows you to easily mock out tests based on AWS infrastructure.
Next.js - The React Framework