grafbase VS assemblylift

Grafbase (GraphQL)

https://github.com/grafbase/grafbase/tree/main/examples/reso...

Founder of Grafbase here.

From a product perspective Grafbase offers a serverless, realtime GraphQL API deployed at the edge. Our goal is to provide a unified data layer on top of existing APIs and databases.

The Grafbase platform itself is built in Rust and deployed to the edge using WebAssembly. Every GraphQL endpoint is deployed to V8 isolates at the edge which translates to very low cold starts and extremely fast performance globally.

Our branching feature makes collaboration seamless with your team. Just created a Git branch and push it up to create an instant preview branch that is totally isolated from production.

The Grafbase CLI is open source and available on GitHub: https://github.com/grafbase/grafbase.

Check us out: https://grafbase.com/

We are Grafbase are making backends easy. Using the CLI, you can use the entire platform (including live queries) locally.

Grafbase was built to manage all of the above. You get a distributed GraphQL API at the edge by creating a single grafbase/schema.graphql file in your project.

The Grafbase CLI is written in Rust and open-sourced on GitHub.

AssemblyLift is an open platform for cloud-native application development. AssemblyLift provides a portable, function-oriented framework and WebAssembly-based runtime which can be deployed to AWS Lambda or Kubernetes. The AssemblyLift CLI generates HashiCorp Terraform infrastructure code from simple TOML definitions, and takes care of compiling and packaging functions and services for deployment. To make a clichéd comparison, think of it as Infrastructure on Rails 😛

Since our last post introducing the AssemblyLift v0.4-alpha series, we've had two new alpha releases which introduced some major additions & improvements!

Today we're making available the first alpha release of AssemblyLift v0.4. This initial release brings a few exiting improvements to AssemblyLift including

After nearly two years in part-time development, AssemblyLift has been through three major revisions, sitting now at v0.3.2.

In this guide we'll use AssemblyLift to deploy our Lambda function, and define our API and an authorizer. AssemblyLift is an open platform which allows you to quickly develop high-performance serverless applications. Service functions are written in the Rust programming language and compiled to WebAssembly. The AssemblyLift CLI takes care of compiling and deploying your code, as well as building and deploying all the needed infrastructure!

Normally what we've described above would be a pretty complicated set up (and a much longer article 😜). Luckily we can use AssemblyLift to do all the heavy work for us!

This article will walk through building and deploying a simple static site, served using AWS Lambda and API Gateway. To accomplish this we will use AssemblyLift, an open-source platform designed to quickly & easily accomplish such a task.

If you've never heard of it or just need a reminder, AssemblyLift is an open platform for developing cloud-native applications. At its core are the AssemblyLift Runtime and the AssemblyLift CLI. The runtime provides an environment for executing compiled WebAssembly (WASM) on infrastructure such as AWS Lambda, and is one of the more unique aspects of the platform which we'll dig into more below.

Service TOML definitions now support specifying authorizers by ID for each function. These map to API Gateway authorizers; currently only IAM and JWT are supported. See the pull request for examples.