proposals
serverless-graphql
proposals | serverless-graphql | |
---|---|---|
60 | 215 | |
63 | 2,708 | |
- | 0.1% | |
4.2 | 0.0 | |
5 days ago | over 1 year ago | |
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.
proposals
-
Is there an alternative for Airflow for running thousands of dynamic tasks?
Check out temporal.io open source project. It was built at Uber for large scale business-level processes. So any data pipelines are low-rate use cases by definition.
-
KuFlow as a Temporal.io-based Workflow Orchestrator
With KuFlow it is also possible to work with serverless workflows apart from Temporal.io, we explain it in this blog entry, but in summary, almost as a no-code tool, the correct use It would be a rather low-code tool; in just a matter of minutes with our drag-and-drop tool, you can have a workflow that interacts with one or more users of the organization.
-
How to handle background jobs in Rust?
Otherwise you may want to look into Kafka or Fluvio to ensure that task runs at least once. If you're doing something like batch operations as a background task, Temporal is another great option.
-
No-code or Workflow as code? Better both
The runtime is developed using Temporal, which is one of the main tools that we are currently using at KuFlow. Thanks to, all the workflow executions are robust: your application will be durable, reliable, and scalable.
-
Temporal Programming, a new name for an old paradigm
Hmmm I got confused by the name. I thought it's related to https://temporal.io/
-
Possible innovations in Event Sourcing frameworks.
Have you looked at temporal.io open source platform? It uses event sourcing as an implementation detail. But it greatly simplifies the user experience compared to "raw event sourcing."
-
After Airflow. Where next for DE?
Rewrite Airflow on top of temporal.io. This way, you get unlimited scalability and very high reliability out of the box and would be able to innovate on the features that matter for DE.
-
Show HN: Retool Workflows – Cronjobs, but better
Hi all, founder @ Retool here. Over the past year, we’ve been working on Retool Workflows; a fast way for engineers to automate tasks with code. We started building the product because we ourselves (as developers) were looking for something in-between writing cron jobs (which involves a lot of boilerplate) and Zapier (which oftentimes isn’t customizable enough, since it doesn’t _really_ support writing code).
Workflows is a code-first automation tool: you’re _expected_ to write code, but we handle all the boilerplate for you. For example: out-of-the-box integration with 80+ resources (you probably don’t want to be trying to figure out OAuth 2.0 with Salesforce!), monitoring and observability (so you can see the output of every run in the past, and immediately be notified if something goes wrong), and permissions (e.g. some Okta groups can see the outputs of Workflows, but can’t change the code itself).
Right now, the product is cloud-only, but we’re hard at work at an on-prem, self-hosted version (in a Docker image). If you’re interested in that version, feel free to email us at [email protected]. We aim to get it out in the next few weeks. Self-hosted Retool is responsible for a large portion of our usage today, and we’re excited to be supporting Workflows too.
All Retool plans now include 1GB of Workflows throughput, which we think is quite generous (80% of active Workflows users are below 1GB). We don’t bill by run at all, so you’re welcome to run as many workflows as you want.
We use a bunch of interesting technology for Workflows; we are, for example, using Temporal (https://temporal.io/) under the hood. That’s something we’re going to be writing a blog post about later. (We’ve been hard at work on the launch, hah.)
-
How KuFlow supports Temporal as a worfkows engine for our processes?
In such a diverse world, it would be boring to have a single way of doing things. That's why at KuFlow we support different ways to implement the logic of our processes and tasks. And in this post, we will talk about one of them, the orchestration through Temporal, which gives us a powerful way to manage our workflows.
- Library for manage tasks when make a workflow automation.
serverless-graphql
-
Testing AWS Lambda Functions (Serverless Framework) with OpenTelemetry and Tracetest
Since then, the ecosystem has changed. Using the Serverless Framework makes deployment simpler. We released the managed Tracetest App making any serverless-based systems simpler to instrument and test. You can now test public-facing apps with no infra overhead!
-
The 2024 Web Hosting Report
We see some great results from using these in conjunction with frameworks such as SST or Serverless, and also some real spaghetti from people who organically proliferate 100’s of functions over time and lose track of how they relate to each other or how to update them safely across time and service. Buyer beware!
-
Deploy app to AWS by using Serverless Framework
When we think about AWS serverless service, the first thing that comes to our mind is Lambda function. Yes, the quickest way to deploy this backend Express JS app to AWS is to deploy it as a Lambda function. The easiest way is using Serverless Framework.
-
Lambda Scheduling & Event Filtering with EventBridge using Serverless Framework
Serverless Framework: https://www.serverless.com/
-
The Top 10 GitHub Repositories Making Waves 🌊📊
Github | Website
-
Instrumenting AWS Lambda functions with OpenTelemetry SDKs
In this example, we're using the serverless framework to quickly set up the Lambda function along with an API gateway for the entry point. The lambda function is a simple Koa REST API with a few functional endpoints.
-
A Beginner's Guide to the Serverless Application Model (SAM)
Naturally, there are several options available to declare your cloud resources. The options with the most popularity are the CDK, AWS CloudFormation, SST, Serverless framework, Terraform, and AWS SAM. There are others, but when talking about Infrastructure as Code (IaC), these are the ones you hear about most often.
-
🥇 The Best Serverless Framework in 2023: A Data-Driven Showdown for AWS Projects
1 - Serverless + AWS CDK + Lift: An integration that amps up the traditional Serverless Framework with Lift's static frontend construct and CDK's robust infra definition.
-
Serverless Semantic Search, Free tier only
It's a bit easier in Python if you use tools like https://www.serverless.com/. I'm not sure if Rust has something similar yet.
-
Trace-based Testing AWS Lambda with Tracetest, ECS Fargate, and Terraform
Serverless
What are some alternatives?
conductor - Conductor is a microservices orchestration engine.
LocalStack - 💻 A fully functional local AWS cloud stack. Develop and test your cloud & Serverless apps offline
temporalite-archived - An experimental distribution of Temporal that runs as a single process
Serverless-Boilerplate-Express-TypeScript - 🚀🎉📚 Boilerplate and Starter for Serverless framework, ExpressJS, TypeScript, Prisma and MongoDB ⚡️ Made with developer experience first: Serverless framework + Live reload + Offline support + ExpressJS + TypeScript + ESLint + Prettier + Husky + Commitlint + Lint-Staged + Jest + Dotenv + esbuild + VSCode
zenml - ZenML 🙏: Build portable, production-ready MLOps pipelines. https://zenml.io.
copilot-cli - The AWS Copilot CLI is a tool for developers to build, release and operate production ready containerized applications on AWS App Runner or Amazon ECS on AWS Fargate.
seldon-core - An MLOps framework to package, deploy, monitor and manage thousands of production machine learning models
terraform - Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.
kubemq-community - KubeMQ is a Kubernetes native message queue broker
electrodb - A DynamoDB library to ease the use of modeling complex hierarchical relationships and implementing a Single Table Design while keeping your query code readable.
nextjs-cron - Cron jobs with Github Actions for Next.js apps on Vercel▲
chalice - Python Serverless Microframework for AWS