HN

Comments (15)

• Menu

  pyrolistical
  It’s like next.js but for backend.Personally not for me. These are very productive once you learn the shape they expect.But the wheel needs to be reinvented on how to do everything.I ran have straight forward verbose code with no hidden control flow
• Menu

  rgbrgb
  I’ve been curious about trying the Supabase type of RLS model for an app but haven’t yet. I like the idea of the db defined api like postgraphile and hasura but had trouble with testing and ergonomics. This looks pretty nice though, it’s cool that you’re thinking about ergonomics for working with coding agents. I feel like a hard thing with that rn is that everyone is kind of figuring out different workflows for AI coding right now so it’s hard to optimize DX. Can you talk a little about your personal agent workflow and how this fits it?
• Menu

  phren0logy
  I love the (well-disclosed) fake testimonials. Hilarious!
• catlifeonmars
  What, in your opinion, is this not a good fit for?
• desireco42
  I was about the ask a question but you just answered how it is built. I guess I will try it out, it sounds really good.I love your approach, fake testemonials and all.
• xixixao
  Very cool!Note that you can run Convex on top of your own Postgres, and we do this for our internal apps, with very nice performance (plenty for our internal use cases).
• bosky101
  very cool. though the deploy wasnt clear if i can just run migration on some pg url. and it wasnt clear if i can bind some middleware into my existing app server (like express)
• ramon156
  Fake reviews are a hard no-no imo. Really weird addition, but I suppose it wasn't you who got the idea.Looks an awful lot like a orpc, just built on top of drizzle instead of raw queries. I'm sure some people want this, but it seems like gross duct tape that will bite you in three years
• scrollaway
  Scratching my head a little bit here, I'm not sure how this differs from NextJS (or Vite) with a layer of drizzle & better-auth.Not that that layer isn't important. We ended up building something like this at Ingram, nextkit: https://github.com/ingram-technologies/nextkit - but we distribute it as a set of micro libraries that work well together rather than a unified framework. (Auth is nk-auth, built on top of betterauth, and sql is nk-db, built on top of drizzle)You got to pretty much the same conclusions we did though regarding the "why".
• Menu

  SifatAhmed
  This looks great. Question specifically on the Cloudflare Workers target: when you deploy there, does Typebase use D1 for the DB, or does the Postgres/Neon backend stay the same regardless of which server target you pick (Vercel/Workers/Deno) - i.e. is the DB layer decoupled from the server runtime, or does choosing Workers also mean choosing D1? I ask because I've shipped a small Workers+D1 service and the main friction I've hit isn't the server code, it's Workers' constraints around D1 (no long-running connections, HTTP-based driver quirks) - curious whether Typebase abstracts that away or whether you still feel it at the DB layer when targeting Workers specifically.
• mermadicsolutio
  [dead]