For full text search please use the '?' prefix. e.g. ? Onboarding

Tools

Collections

  • Dragonfly is a modern in-memory datastore, fully compatible with Redis and Memcached APIs. Dragonfly implements novel algorithms and data structures on top of a multi-threaded, shared-nothing architecture. As a result, Dragonfly reaches x25 performance compared to Redis and supports millions of QPS on a single instance.
  • mkcert is a simple tool for making locally-trusted development certificates. It requires no configuration.
  • Hono is a small, simple, and ultrafast web framework for the Edges. It works on any JavaScript runtime: Cloudflare Workers, Fastly Compute, Deno, Bun, Vercel, AWS Lambda, Lambda@Edge, and Node.js.
  • Teo is schema-driven web server framework. The server side API is native to Rust, Node.js and Python.

API

  • Insomnia - Build APIs that work.
  • Learn Apollo - Learn Apollo - A hands-on tutorial for Apollo GraphQL Client (created by Graphcool)
  • Mock Service Worker (MSW) - Seamless REST/GraphQL API mocking library for browser and Node.js.
  • MeCallApi
  • API Platform - Create REST and GraphQL APIs, scaffold Jamstack webapps, stream changes in real-time.
  • directus - Open-Source Data Platform 🐰 — Directus wraps any SQL database with a real-time GraphQL+REST API and an intuitive app for non-technical users.
  • API Hub - Free Public & Open Rest APIs - Discover and connect to thousands of APIs
  • PostgREST serves a fully RESTful API from any existing PostgreSQL database. It provides a cleaner, more standards-compliant, faster API than you are likely to write from scratch.
  • mitmproxy2swagger - A tool for automatically converting mitmproxy captures to OpenAPI 3.0 specifications. This means that you can automatically reverse-engineer REST APIs by just running the apps and capturing the traffic.
  • tRPC allows you to easily build & consume fully typesafe APIs, without schemas or code generation.
  • A Poor Man’s API
    • PostgREST is a standalone web server that turns your PostgreSQL database directly into a RESTful API. The structural constraints and permissions in the database determine the API endpoints and operations.
  • numverify - Global Phone Number Validation & Lookup JSON API: Real-time REST API supporting 232 countries
  • https://www.freepublicapis.com/ - A collection of Free Public APIs for Students and Developers. - Tested every single day.

Low code

Framework

  • PocketBase is an open source Go backend, consisting of:
    • embedded database (SQLite) with realtime subscriptions
    • built-in files and users management
    • convenient Admin dashboard UI
    • and simple REST-ish API
  • Hono is a small, simple, and ultrafast web framework for the Edges. It works on any JavaScript runtime: Cloudflare Workers, Fastly Compute, Deno, Bun, Vercel, AWS Lambda, Lambda@Edge, and Node.js.

Service

Why we’re moving away from Firebase

We’ve developed a few small projects on Supabase recently as a part of our prospecting process. The developer experience has been delightful, particular Row Level Security, the more powerful analog to Firestore Rules. That Supabase is betting on Deno for their serverless function suite indicates to us that they are serious about great technology.

We love PostgreSQL which Supabase utilizes. We plan to do more research on scalability, since SQL databases can’t grow as big as their NoSQL counterparts. Nonetheless, Supabase came at the right time.

Hacker news

It's from Google, they deprecate things every 6 months including APIs your app is using, if you don't follow your app will be down pretty quickly. AWS nearly never do breaking changes.

jamest

[Firebase founder]

I no longer work at Firebase / Google, but two points:

  1. There may be issues with the GCP integrations & UX/DX, but GCP integration is good for many customers and necessary for the future of the business.

    One of the common failure modes for the 2011-2014 crop of Backend-as-a-Service offerings was their inability to technically support large customers. The economics of developer tooling are a super-power-law. So, if you hope to pay your employees you'll need to grow with your biggest customers.

    Eventually, as they become TheNextBigThing, your biggest customers end up wanting the bells and whistles that only a Big Cloud Platform provide.

    This was a part of the reason we chose to join Google, and why the Firebase team really really really pushed hard to integrate with GCP at a project, billing, and product level (philosophy: Firebase exposed the product from the client, GCP from the server) despite all the organizational/political overhead.

  2. I'm excited to see the current crop of app platforms emerge. It has been 10 years since we launched and there are now some great innovations in the space. I like the way Supabase has exposed Postgres and InstantDB graphdb+realtime is really promising.