Ts.ED VS sidewinder

Ts.ED - Controller-based (DI supporting) backend framework that seems to offer quite a lot (although I'm wary of it being quite close to Nest.js)

Take a look at ts.ed. They have some similar feature

has anyone looked at tsed.io

As a developer, it's always important to find ways to streamline the development process and save time. For the past two years, I've been using Ts.ED as the framework for all of my applications and it's been a game-changer. Not only has it allowed me to gain back lost development time, but it's also been the foundation for my open-source project HighScore.

I use Ts.ed as framework, go to this site to known more about this awesome framework.

Because of this, I decided to create a base template of a REST API created with NodeJS, using Ts.ED as the base framework and TypeScript as the programming language. This template tries to follow the principles of Domain Driven Design and implements a Clean Architecture/Hexagonal Architecture to try to rely as little as possible on the infrastructure and the framework while keeping in mind at all times the language and the needs of the business logic.

I love Ts.ED https://tsed.io

I'd also love to shout out Ts.ED which is another great Typescript framework that I've written production applications with. It's a natural fit for anyone who loves .NET applications, it's why I chose it.

I will check this out, but personally pretty happy with this on the backend: https://tsed.io/

You should probably really define what you need a bit better. I have a starter kit (https://stribny.github.io/sidewinder/) that has some good defaults out of the box (like using django-allauth). Pair it with e.g. https://github.com/paddle-python/dj-paddle for Paddle (or something similar for Stripe) and you have a good base.

And experimenting with switching it to use channels by default (https://github.com/stribny/sidewinder/compare/master...channels) so that websocket connections could work out of the box.

Check out https://stribny.github.io/sidewinder/, maybe that's what you next project will need :D

Working on a Django starter kit for indiehackers that has a deployment to VPS story included: https://stribny.github.io/sidewinder/

My first choice if the product is a good fit would be old school Django deployed to a single VPS (no docker). I am creating a public starter kit that does exactly that, including the deployment part: https://stribny.github.io/sidewinder/

However, there are lots of use cases that would call for additional SPA (Vue/Nuxt), or other tech. So in that case I'd add it or replace the tech stack entirely. I'd probably avoid specialized cloud services, might consider something like https://supabase.com tho if the app doesn't need a complex backend.