It's a python web framework, for those curious to know more before clicking through.
LigmaBaulls · 3m ago
thanks, saved me some time.
hariwb · 17m ago
Thanks for writing this. I have similar gripes about FastAPI having developed an application over the past few years; I'm also continually surprised at how prevalent the attitude is that FastAPI has excellent docs, given how divorced the tutorial / toy examples in the docs are from real-world development and measurement of an API.
ddejohn · 27m ago
Excellent post that actually gets into important details for real-world applications. I'm a huge fan of the design of Litestar.
> I also still think there are a lot of bad use cases for repositories and service layers that people should avoid, but that’s a digression which should probably become its own post
As a huge proponent of the repository pattern, I'll be looking forward to this post.
NeutralForest · 21m ago
Pretty cool post! I'm not sure how I feel about SQLAlchemy (not the star of the post but mentioned quite a bit); it's such a big ball of state that has so many surprises, I wonder if some people build entirely without it.
devjab · 8m ago
There is a rather big difference between traditional SQLAlchemy and Advanced Alchemy which is also made by Litestar. We've build with pure SQL and with SQLAlchemy in the past, but since we transitioned from django ninja to Litestar, we've not used SQLAlchemy and are slowly moving away from it. Well I guess Advanced Alchemy is still SQLAlchemy under the hood.
sambaumann · 4m ago
I recently built a personal project using peewee and it doesn't have a ton of bells and whistles but it works well for what it does do.
cbzbc · 12m ago
How do people deploy this framework typically - speaking for myself, I found NGINX Unit somewhat fiddly.
devjab · 4m ago
With uvicorn.
cr125rider · 36m ago
Litestar is awesome. It’s great it’s got more than a single maintainer too.
punnerud · 26m ago
Good to see it using port 8000 as default, and not Flasks 5000 (does not work on Mac anymore)
> I also still think there are a lot of bad use cases for repositories and service layers that people should avoid, but that’s a digression which should probably become its own post
As a huge proponent of the repository pattern, I'll be looking forward to this post.