Also Expensify's Bedrock, which powers their famous "Scaling SQLite to 4M QPS" article:

https://bedrockdb.com/

https://use.expensify.com/blog/scaling-sqlite-to-4m-qps-on-a...

Lots of things don't need failover, but if you do, you can use Bedrock, which is built on sqlite.

At first, I thought Amazon was launching their own SQLite hosted database.

BedrockDB is a SQLite based database with MySQL compatible drivers.

https://bedrockdb.com

Vapor[0] based on Swift. Advantage of this is that you don't have to evaluate multiple frameworks for Swift and suffer paralysis by analysis. All the Swift community is behind one framework.

The next is Actix[1] based on Rust. There are many frameworks in Rust and most of them have not reached 1.0 And which framework will survive becomes a question.

Other not so well-known is Wt[2] based on C++. This actually is created for programmers who are not web developers. The development experience is similar to desktop app development like Qt.

If that is not acceptable then Django[3], based on Python, is the one that will be good for you.

For the front-end I would recommend Flutter[4]. As much as I dislike getting tied to a single company for whom the framework is not their bread-and-butter, I don't see any other viable options to Flutter that will cover all web, mobile and desktop out of the box.

For databases, I would recommend BedrockDB[5], if you are not averse to SQLite. Or FoundationDB[6], if you want NoSQL. But if you are not concerned about horizontal scalability or okay with self-managing database availability, then PostgreSQL[7] is a very good option.

For push notifications, PushPin[8] is a good option.

[0] https://vapor.codes

[1] https://actix.rs

[2] https://webtoolkit.eu

[3] https://www.djangoproject.com

[4] https://flutter.dev

[5] https://bedrockdb.com

[6] https://www.foundationdb.org

[7] https://postgresql.org

[8] https://pushpin.org

Recently I stumbled upon BedrockDB[0] from Expensify. It is based on SQLite and has very interesting idea on HA and distributed DB.

[0] https://bedrockdb.com

This is not SQLite though, also the test is trivial compared to TPC: https://github.com/Expensify/Bedrock/blob/dbarrett_perftest/...

Don’t forget BedrockDB (built on SQLite) that’s used in production at Expensify.

How it scales as well.

https://bedrockdb.com/

https://blog.expensify.com/2018/01/08/scaling-sqlite-to-4m-q...

import { unstable_noStore as noStore } from "next/cache"; import Link from "next/link"; import { CreatePost } from "~/app/_components/create-post"; import { getServerAuthSession } from "~/server/auth"; import { api } from "~/trpc/server"; export default async function Home() { noStore(); const hello = await api.post.hello.query({ text: "from tRPC" }); const session = await getServerAuthSession(); return (

Create T3span> App h1>

First Steps →h3>

Just the basics - Everything you need to know to set up your database and authentication. div> Link>

Documentation →h3>

Learn more about Create T3 App, the libraries it uses, and how to deploy it.div> Link> div>

{hello ? hello.greeting : "Loading tRPC query..."}p>

{session && Logged in as {session.user?.email}span>} p> {session ? "Sign out" : "Sign in"} Link> div> div> div> main> ); } async function CrudShowcase() { const session = await getServerAuthSession(); if (!session?.user) return null; const latestPost = await api.post.getLatest.query(); return (

{latestPost ? (

Your most recent post: {latestPost.name}p> ) : (

You have no posts yet.p> )} div> ); }

I thought he was making stuff up - "t3 stack vs t4 stack". But about 2 minutes in, I realized that I'd heard of a few things that he's talking about so I looked it up and they're real!

I think it's possible everything he's saying is true, more or less. LOL

t3: https://create.t3.gg

t4: https://t4stack.com

We start with a project that was bootstrapped with create-t3-app. For internationalization we use next-intl and set it up as described in the getting started guide. With this initial project setup we can jump into implementing localized error messages.

I used create-t3-app to scaffold the Next.js app, with TypeScript, Prisma, and "app router" enabled in the options. You can also use create-next-app for the job and install Prisma manually.

I agree that the quantity of publicly available code isn't the most reliable indicator of someone's seniority.

My issue with this individual arises from the discrepancy between his public claims of significant expertise in the content he produces. He positions himself as a highly experienced developer, attracting a large following of junior developers who take his advice at face value.

I am trying to collect data points supporting his claims of seniority. For instance, his website prominently features a statement that he is the creator of the T3 Stack. However, a review of the contributor statistics for the T3 Stack (https://github.com/t3-oss/create-t3-app/graphs/contributors)... minimal contributions from him, which raises questions about the validity of his claims.

I would recommend - https://create.t3.gg/

It uses the following, which as of late are pretty well know and common, so you can punch in your problems to stackoverflow, google, or chatgpt and get some pretty good answers.

It uses:

Nextjs (React), typescript, trpc (typescript rpc), auth, tailwind, and Prisma (ORM)

Though of course these could go out of fashion tomorrow, but I don't think the essential idea behind these libs and frameworks are that wacky, unique or unordinary.

Prisma ORM, is a little opinionated, and you could swap it out for Drizzle, which is basically typescript side sugared SQL.

TRPC might be also be a little sticky because it is tied to typescript, this is the tradeoff for the buttery smooth coupling for the fullstack experience. I think there exists a typed-rest solution out there, but haven't used it.

Personal anecdata, I used this stack for a little hobby project and it was FUN.

Open SaaS was built with Typescript, and because it’s a full-stack app, type safety from the back-end to the front-end can be a real lifesaver. I mean, some opinionated stacks have gotten hugely popular on this basis.

Let's start by creating a Next.js application. We will use the T3 stack (TypeScript, TailwindCSS, and Prisma ORM) for this tutorial to skip installing and configuring all the dependencies which is out of the scope of this article. You can find more information about the T3 stack.

https://github.com/t3-oss/create-t3-app

You still would need to add Stripe but there are so many examples publicly available that it should be straight forward