rick1290

Interesting about the files vs db approach. I have been going back and fourth. I landed on db as well.

I'm still not sure. Would love thoguhts on this.. but in this new ai world we are in... is it better to go fullstack typescript? or go with proven mature frameworks? .net, ruby, django, etc? Seems TS is moving fast but maybe its time to not reach for the shiny object and stick with proven tech? or in 5 years will we regret it?

Is django the best backend batteries included framework at the moment?

is rill open source?

Agreed. When I watch the llm start to explore the db - it really does impress me.

Can you expand on this:

You can even incrementalize the schema description process itself by way of the system tables. Intentionally not providing a schema description tool/document/prompt seems to perform better with the latest models than the other way around.

Not quite sold on this. I'm going to stick with pydantic ai and dbos/temporal/celery. I do not want to be vendor locked into one of these players. I want to work with absoluately any llm I want... I think we need to keep pushing for best in class open source orchestrtion and not get sucked into this platforms.

cool

seems interesting. whos the target demo for this though?

When is MCP the right choice though? For example - letting internal users ask questions on top of datasets? Is it better to just offer the api openapi specs and let claude run wild? or provide an MCP with instructions?

love it

Agreed

So basically dont use django and vibe code your own framework?

Would love to see this.

Django just makes life 1000x easier. Can architect an app with data models, api, openapi, etc. within an hour.

I like mikro orm - cool to see you use that. I do prefer django however.

I see express as the backend. Why not nestjs? And are you using openapi at all for generating your frontend client?

What i've discovered is - any backend + orm should expose an openapi spec'd backend... and your frontend can autogen your client for you. Allows you to move extremely quick with the help of ai.

whats your defacto now?

looks great

you mention hasura - is that open source? you are leaning on a product for migrations that are not open source is my main concern with the above comments.

Are you saying you'd start a new project with alembic/sqlalchemy nowadays?

What about for the db? Prisma? Postgres?

Are you able to share some of the tech stack choices behind the scenes? React, fastapi, django, go, pydantic ai, ag-ui, firecrawl, vertex ai, etc. Would love to see the tools and frameworks others are deploying with.

awesome!

Which pages are django?

How does this compare to Django? I see you have quite a bit of Django content. How would you decide to use Litestar vs Django on a new greenfield project?

whats your setup for the frontend? do you autogen your queries from DRF? do you prefer react headless over django templates?

Why? Isn't this easier to screw up the prod db?

Yeah, that is a bit disheartening. It’s a reminder of how vital it is to support open source tools, especially when they’re going up against massive, well-funded competitors. These projects often power the backbone of the internet and tech ecosystems, but they can’t survive on goodwill alone.

If we want innovation, transparency, and community-driven development to thrive, we have to step up — whether it’s donating, spreading the word, or helping out however we can.

Agreed

Django, however, is wonderful for internal tooling, or anything where you need to plug in Python libraries. GIS is a clear win for Django, as well as custom BI work or data analytics

Can you share more here? Would you go the route of django templates for internal tooling?

Love django. Whats the consensus on best way to use django in 2025? I've been going the headless route. Django for the backend and using vite or nextjs on the frontend with openapi specs auto-generated.

Love django. Its my go-to as well.

I have gone django, drf, heyapi + vite/react.

I do like templates for simple pages - but with ai now. Its pretty fast to build out your api completely with drf. Then autogen the api in vite. Once you have all of your types and queries auto created. You can pretty much 'vibe' code your UI how you see fit. Then leave django to handle everything data/backend.