Built a full-stack movie discovery platform with .NET 9 Web API, EF Core 9, Postgres, and SvelteKit — NoMoreCritics.com
Hi DotNetters!
I wanted to share a side project I’ve been working on called NoMoreCritics.com.
It was born out of job market frustration, frustration with movie critics/review sites, and pure boredom. I was out of work and needed a project to keep my C# skills from getting rusty.
I love movies, but I realized I rarely agree with critics. I wanted a site that cuts through the noise and focuses on what people actually like. To do that, people need a safe space to anonymously promote films they love without getting dragged in comment sections.
Instead of another aggregate review site, we aggregate rankings:
- No Reviews, Just Rankings: Avoids much of the BS with negative reviews and comments. You only rank movies you want to promote.
- Dynamic & Capped: Opinions change, so rankings are meant to be updated anytime. Lists are capped at 250 films so rankings actually mean something.
- Organic Global List: It’s a weighted system—the more you rank, the more your opinion counts. If you stop logging in, your list drops off, keeping the global rankings constantly changing.
- Built for Discovery: Includes private notes, custom watchlists, streaming availability filters (via TMDB/JustWatch APIs), and tailored recommendations based on your tastes.
Architecture & Tech Stack
I paired a robust C# backend with a lean SvelteKit frontend:
- Backend API: ASP.NET Core Web API (.NET 9)
- Frontend: Svelte / SvelteKit (chosen for its awesome DX, built-in reactivity, and the fact that it compiles down to lean, pure JS without React-style bloat)
- ORM: Entity Framework Core 9
- Database: PostgreSQL (chosen over SQL Server primarily for its robust built-in Full-Text Search; containerized in production)
- Infra: GitHub Actions CI/CD, Cloudflare for edge caching and SSL
Questions for the Community & Feedback
I’m the solo developer on this and had to learn a lot along the way. I spent the first half coding without AI to ensure I truly understood the underlying architecture before leaning into AI tools to finish it up.
I’d love your feedback on the site, API responsiveness, or overall feel. Also, for fellow .NET devs:
- PostgreSQL vs. SQL Server: For those who chose Postgres over SQL Server for .NET projects, what were your main deciding factors in production? Any tooling friction with pgAdmin/DBeaver or pleasant surprises with Npgsql? (I mostly switched for the native full-text search capabilities.)
- Upgrading to .NET 10 LTS: I built this on .NET 9, but with .NET 9 heading toward End of Support later this year, I'm planning my upgrade path to .NET 10 LTS. For those who bumped to .NET 10, were there any breaking changes in EF Core or ASP.NET Core Web API that caught you off guard?
- EF Core 9 Query Tuning: Have you noticed solid gains with LINQ query generation on complex joins in EF Core 9, or where do you typically drop down to raw SQL/Dapper?
Check it out at NoMoreCritics.comif you have a minute. Thanks for taking the time to read this!