91–100 of 117 posts
Seems like this is lacking a lot of crucial stuff. What happens when you want to run a background job?
Definitely would reach for remix before next, and I would go with a big cloud provider container app solution such as Azure container apps (if azure was better) or Google Cloud Run (good, but do you trust google?) before Vercel. Personally I think ORMs are mostly bad and Prisma is more of the same. Zapatos at least gives you typed SQL results without a lot of overhead.
As for the ORM / query building, did you also consider Drizzle and Kysely against Zapatos?
PocketBase + Go + HTMX
Could you recommend a stack please? * Testing - test runner, mocking * Database - Typesafe queries, ideally as little abstraction as possible, migrations * Web app framework * Dependency injections (or do you prefer doing it manually over using a library)
Definitely would reach for remix before next, and I would go with a big cloud provider container app solution such as Azure container apps (if azure was better) or Google Cloud Run (good, but do you trust google?) before Vercel. Personally I think ORMs are mostly bad and Prisma is more of the same. Zapatos at least gives you typed SQL results without a lot of overhead.
Why Remix over Next? As for the ORM / query building, did you also consider Drizzle and Kysely against Zapatos?
I haven't played with either Drizzle or Kysely, looking at the docs Drizzle in particular looks slimmer and more sql-like which is a plus, though in general I think having an environment like dbeaver or data grip that gives you completions for your queries and developing them there then copy/pasting the code and getting type safety on raw queries with zapatos is still superior for power users who know sql.
Earlier quoted context omitted.
Pocketbase is just superb. I am using pocketbase together with scalajs and svelte. It saved me so much time setting up the basics and you won't regret it once the project grows. Anything works with pocketbase but go or any js based stack has an easy onboarding.
Do you eventually have to move off pocketbase? Looks like it only supports SQLite, and therefor obviously can only run a single server instance. How do you plan to migrate off it in the case that you have higher availability or traffic needs?
https://github.com/pocketbase/pocketbase/discussions/395
Never happened to me. SQLite is faster than most people think. When you hit the limits of sqlite, chances are high that you can afford to use one of the scaling solutions mentioned above. Here are some benchmarks:
From all of this, the worst decision is to use Next. Vendor lock in, developed by one of the most shady companies right now, and full of problems.
PocketBase + Go + HTMX
Only backend developers like it. As soon as you have to do anything minimally complex it's just terrible.
Definitely would reach for remix before next, and I would go with a big cloud provider container app solution such as Azure container apps (if azure was better) or Google Cloud Run (good, but do you trust google?) before Vercel. Personally I think ORMs are mostly bad and Prisma is more of the same. Zapatos at least gives you typed SQL results without a lot of overhead.
We migrated our main application to Remix and couldn't be happier. The app router stuff is such a mess.
PocketBase + Go + HTMX
LOL. The HTMX hype is worse than every other fashionable framework. Only backend developers like it. As soon as you have to do anything minimally complex it's just terrible.