fastapi-fullstack-boilerplate VS full-stack-svelte-prototype

Monolith looks awesome! I love the name -- I too am embracing and championing the "monolith-first" approach.

You've given me some inspiration for my own starter-kit built on FastAPI (trying to capture the magic of Django): https://github.com/tmkontra/fastapi-fullstack-boilerplate

I hope to follow along with your progress and perhaps share ideas/compare notes! Cheers.

Even for stateful apps, I reach for FastAPI now. It's just so expressive. For the "full stack bits" there are plenty of libraries, it's just a little work to stitch them together.

This is my boilerplate: https://github.com/ttymck/fastapi-fullstack-boilerplate

> They all look complicated and require lots of configs and plumbing to get started.

I felt the same way so I made my own full-stack "framework" just for me centered around the Svelte component library which I love:

https://github.com/Glench/full-stack-svelte-prototype/

Been using it in production and really really happy with it. Obviously kind of stinks to not have community support but so far it hasn't been a huge issue.

It basically sets up all the crap that I don't want to have to think about while keeping a tight coupling between the front-end and back-end (which is how I develop) — clear separation of code that runs on the server vs the client (with code splitting and CSS generation), rendering pages on server and hydrating client components, communicating between the server and client, re-rendering components when new data arrives. It really fits my needs well.