This a simple chat app created using Next.js 13 for educational purposes. User can login using Google Login API and send messages or chats.

NestJs Wrapper for Upstash Redis

Quack - just like Twitter, but worse (in every way)

Practice clone app meta messenger with Next.js V.13

A Full Stack NEXT Application, build on ReactJS, with Google Authentication, Advanced caching, Infinite scrolling, React-Query, Search, Comments, Voting, Prisma, hosted on Versel and PlanetScaleDB Cloud

Software as a Service (SaaS) platform leveraging the capabilities of GPT (Generative Pre-trained Transformer) technology. Upload image and generate the metadata/description and response to the validity of picture.

Gallery application

wip: モノレポで最小限＆スケーラブルなアプリケーション開発をするためのテンプレートレポジトリです

Next js 13 practice with Upstash, Typescript, Redis, Next Auth, Pusher, SWR

This app lets you send messages to other people. Sign in with your facebook account.

Unofficial Rust SDK for Upstash QStash

Welcome to Messenger, a real-time messaging application built with Next.js 13 that brings the joy of seamless communication to a whole new level. This project enables users to chat with each other and user-friendly interface.

Streamlined backend with Express.js, Firebase, and Qstash (Headless Cron) for appointment scheduling. Qstash handles cron jobs seamlessly, retrying on failure, and allowing easy monitoring.

Modern Analytics Dashboard with Next.js 14, React, Tailwind CSS, Upstash, Serverless Data Platform

Spotify APIのレスポンスをUpstash RedisにキャッシュしtRPCで取得してNext.jsで表示する例

Redis geosearch demo

Let’s build META Messenger 2.0 with Next.js 13 (Upstash, TypeScript, Redis, Tailwind, NextAuth)

App capaz de capturar informações do client através de um middleware e "cachear" esses dados utilizando o serviço do Upstash. Também é apresenta os mesmos logs consumindo a API no server side.

A repo to learn how to use T3 Stack and how it works.

This project features client-serverless data fetching with a worker. The input fields set concurrency requests limit and requests per second limit. Server responds with an index from the passed worker's POST request. If over 50 requests/sec, server returns 429 error. Client displays responses with every index number with user limits.