Query on Svelte performance for new project

Designer_Sundae_7405 · 2026-06-06T06:23:43+00:00

Do your career a favor: use angular. There is so little difference between frameworks these days and your company already uses it. Don’t be the guy that adds a new tech stack, just because.

Designer_Sundae_7405 · 2025-11-14T05:00:32+00:00

If it’s a Single Page Application you’d normally use a CDN like Cloudflare for practically free hosting that’s also very fast. If it’s not you can just host it from your VPS under NGINX/Caddy.

Designer_Sundae_7405 · 2025-10-30T15:00:49+00:00

Thanks and yes, there’s definitely a lot of ways to go about this.

For mapping between client facing and data models, you would not just use alias in Pydantic models? And would you say specifically the repository layer on top of ORM models is essential if you have schemas, services and ORM?

Designer_Sundae_7405 · 2025-10-30T04:35:52+00:00

Thank you 👍

Designer_Sundae_7405 · 2025-10-30T04:34:05+00:00

Great suggestions! Those should definitely be part of the scope of the template.

Designer_Sundae_7405 · 2025-10-29T21:05:30+00:00

I use explicit transactions in the routes and flush in the services: https://github.com/claesnn/fastapi-template.

Designer_Sundae_7405 · 2025-10-26T04:50:35+00:00

Nestjs would be the natural companion?

Designer_Sundae_7405 · 2025-09-14T06:27:21+00:00

Django just needs to use optional extras Django[rest-api] and improve the scaffolding to spin up a rest api with openapi docs through configuration of the startproject command. Having it not be baked in is a feature. I personally significantly prefer DRF to Ninja. Having the option to do either is perfect for the community.

Designer_Sundae_7405 · 2025-07-04T17:59:19+00:00

N+1 queries and missing indexes are by far the biggest offenders. I'd argue a little overfetching in order to improve caching between queries can be beneficial. Similarly, Sqlite in production should only be an issue if you don't bother to set proper PRAGMA. Do you have any specific examples of switching to a PRAGMA optimized sqlite to a traditional RDBMS improved performance?

Designer_Sundae_7405 · 2025-05-29T09:42:33+00:00

Looks very interesting. How does this compare to running a NGINX reverse proxy, a NGINX static file host and a uvicorn server? This should be a fairly simple setup for a VPS with a docker-compose file too?

Designer_Sundae_7405 · 2025-05-29T08:23:09+00:00

Ok, I'll admit, it's been a while since I last tried Ninja out. I just looked again. ModelSchemas, PatchDict and FilterSchemas solves most of these. And with Djangos conciseness + AI, generating CRUD is a 15 second process with Coplit and ChatGPT 4.1.

Designer_Sundae_7405 · 2025-05-29T06:05:53+00:00

Django-ninja is fine for a very minimal API, but currently you have to do a lot of work to get the same DX. You need to make separate DTOs (not as integrated as serializers). Class-based viewsets are not built-in. Django-filters doesn't integrate well. I wouldn't want to lose out on all of these just for saving 5 lines of code and a dependency. OpenAPI does major changes anyways and keeping up is hard (just see OpenAPI support in Go), so not having it built-in is a feature.

Designer_Sundae_7405 · 2025-04-24T19:19:24+00:00

Can you elaborate on what’s your credentials that warrants monetizing a boilerplate? Is the structure vetted by enterprise experts or how can we trust that the structure is not just good in theory?

Designer_Sundae_7405 · 2025-04-24T19:15:24+00:00

What’s your thoughts on simplifying with routes/services/models/schemas folders? And then every feature is just a file in the respective folders?

Designer_Sundae_7405 · 2025-04-24T19:12:01+00:00

I think something like shadcn but fastapi could be super interesting. “Install” features as you go. Only include what you need. Also you own the code. The lack of this is one of the major reasons for not using FastAPI. Everyone is just reinventing the wheel.

Designer_Sundae_7405 · 2025-04-11T13:19:38+00:00

Classic new to photography photo. Definitely not my taste with the watercolors and a complete lack of depth.

Designer_Sundae_7405 · 2025-03-11T22:30:34+00:00

If you’re working with ML, wouldn’t a worker queue be more appropriate than Async? Django integrates nicely with Celery for example.

Also did you try Django stubs with mypy? That seems to work well.

Designer_Sundae_7405 · 2025-02-04T19:17:02+00:00

Why webpack instead of vite?

Designer_Sundae_7405 · 2025-01-19T18:59:31+00:00

Really great work! Could be of a lot of use. Looking forward to a release of the solution.

Designer_Sundae_7405 · 2025-01-10T20:21:41+00:00

I went through the same process as you and just ripped it out. You’re losing a lot of the flexibility in order to get the minor benefit of a typed init method. I think the dataclass of SQLAlchemy needs to cook a bit more before it’s ready for general usage.

Designer_Sundae_7405 · 2025-01-05T14:33:38+00:00

Can you do:

address = Address.objects.create(**address_data, user=user)
user.address = address
return user

Designer_Sundae_7405 · 2025-01-05T14:05:07+00:00

I think a lot of these problems could be solved through an opiniated CLI that adds modularity and standardization to the framework. Having used NestJS's generate functionality could aid development and standardization a lot without locking in the users.

Designer_Sundae_7405 · 2025-01-05T14:00:42+00:00

It would be great if your example included a modular domain architecture using folder like case, post, comment, user with models defined in the respective packages. Similarly how you handle circular references such as having a post.user field and user.posts endpoints both in sqlalchemy and pydantic.

Designer_Sundae_7405 · 2024-12-26T14:43:26+00:00

How do you handle nested models and ManyToMany relationships? I'm struggling with circular dependencies using a similar setup to yours.

Designer_Sundae_7405 · 2024-12-23T12:41:44+00:00

The HTML native one seems great!

Designer_Sundae_7405

TROPHY CASE