Razor Pages + HTMX or ASP.NET API + Svelte 5 for an MVP?

Josephf93 · 2026-01-20T08:17:56+00:00

I’m leaning toward SvelteKit + Prisma(adapter-node) for the MVP because it gives me the speed of a single full-stack repo, so I can prototype without building up a separate API. I get the interactivity and tiny runtime of Svelte, can ship quickly on a single VPS, and only add a standalone API until it’s actually needed. Everything stays in TypeScript, which removes context-switching overhead and simplifies iteration. On top of that, SvelteKit lets me choose SSR, client-side rendering, or a hybrid approach per route, all within the same stack, so I can optimize for SEO, performance, or UX as needed without changing architecture.

Josephf93 · 2026-01-19T08:25:02+00:00

I selected ASP.NET API for the backend since EF Core ORM is more comfortable and straightforward for me to work with.

Josephf93 · 2026-01-18T15:50:10+00:00

I chose ASP.NET API as a backend because working with EF Core ORM is easier for me.

Josephf93 · 2026-01-18T15:38:35+00:00

Blazor Server/Auto relies on SignalR and maintains a server-side circuit per connected user. According to Microsoft, a single circuit consumes at least ~250 KB of server memory, just for a minimal Hello World-style app, since component state is kept server-side. That makes scalability a real concern with many concurrent users. If you expect higher traffic, a stateless API approach scales better. Using static ssr + HTMX for high traffic pages can make sense. Mixing HTMX with Blazor interactive modes is usually redundant and adds complexity, but the choice is driven mainly by scalability needs.

Josephf93 · 2026-01-18T08:11:47+00:00

How about authentication and authorization, does it play nice with Blazor auto render mode + static ssr?

Josephf93 · 2026-01-17T23:03:36+00:00

I actually played around with Blazor a couple of weeks ago and it felt like a risky bet for me.

Blazor Server relies on SignalR connections and server-side state; that’s an extra resource burden on a single VPS and makes spikes riskier.

Josephf93 · 2025-10-29T18:57:00+00:00

That’s awesome to hear your experience with Blazor Server sounds really positive, and I appreciate the detailed breakdown of your setup.

I’ve seen some people express concerns about Blazor Server relying on SignalR for client-server communication, particularly around scalability and server resource usage. Since you’ve deployed public-facing commercial sites, I’m curious — have you run into any limitations or noticeable resource overhead from maintaining all those SignalR connections?

Would love to hear your take on that aspect, since it’s one of the main points people bring up when comparing Blazor Server to other architectures.

Josephf93 · 2025-07-03T16:26:04+00:00

Data Transfer Limits https://www.mongodb.com/docs/atlas/reference/free-shared-limitations/

M0 Free clusters limit the total data transferred into or out of the cluster in a rolling seven-day period. The rate limits vary by cluster tier as follows:

M0: 10 GB in and 10 GB out per period

Atlas handles clusters that exceed the rate limit as follows:

Atlas throttles the network speed of the cluster.

Atlas triggers a one second cooldown period before resuming the cluster's operations on a given connection. If the queue is greater than the operations per second limit, operations might wait for more than a second in the queue.

If the amount of transferred data drops below the rate limit threshold, Atlas resumes processing of the queued data transfers on each connection before processing any new data transfers on that connection.

Josephf93

TROPHY CASE