What is SQLAlchemy?
Who uses SQLAlchemy?
Here are some stack decisions, common use cases and reviews by companies and developers who chose SQLAlchemy in their tech stack.
Hello everybody! I want to create an easy to use website (and simplified) builder. Users create a site, add their domain and edit Pages inside an Admin Area inside predefined "Blocks" like with Wagtail.
There should be several default templates/themes and layouts. Choosing a different theme might change both the layout and styling. And I'm looking for SSR or SSG with a focus on the end-user's Page performance.
GraphQL for the dynamic part (for example data to Pricing might not be required on the homepage, or images might go into gallery in one theme, and on the homepage in another theme)
FastAPI and SQLAlchemy to store Data. I have prior experience with Wagtail and Django and want to stay with Python and learn Fastapi
NGINX to handle domain-specific things (the how is not yet refined)
I want a scalable architecture and especially a fast frontend. I'm tending to use SvelteKit, but I'm afraid that the dynamic part won't make me happy after having hundreds of sites, as the bundler cannot load themes dynamically. sveltekit - dynamic import
I want to handle the scenario: Admin-User chooses a theme and other options for the site (domain) and the End-User Frontend/Session/Cookie will have to fetch and store data about the theme and load subsequent calls to prerendered sites.
Also the "hundreds of sites" might not be all covered by 5 Themes, because users may purchase a custom-made theme, and I would have to manage one big project having lots of different Styleguides and flows. I even thought of statically building the site whenever the user makes a change, maybe using Hugo (or VitePress?). Then I would have to take more care with the page recreation and it would be easily routable instead of nesting every component with logic in the frontend... I think. But this I haven't thought through yet.
Can anyone please help?
I'm considering moving from Flask to Quart, does anyone have some experience with this migration?
I expect possible problems with connexion which we use as OpenAPI specification.
Would be good if someone can point downsides of moving to the Quart framework so I can double-check if my plan is worth doing.
Other libs and tools used in the project: SQLAlchemy, alembic, PostgreSQL, Datadog
cons for now:
- Refactoring uncertainty (not sure how big of a task is it)
- Connexion might not work with Quart (moving to another library)