3 ms·
It's definitely full stack; it has endpoints[1] which are just arbitrary API endpoints where you can implement any logic you want (talk to a database, perform c
by Ameo 5y ago
It's definitely full stack; it has endpoints[1] which are just arbitrary API endpoints where you can implement any logic you want (talk to a database, perform conditional logic, etc.).
It may not be a fully-loaded solution like rails, but minimalism can have its own benefits.
[1] https://kit.svelte.dev/docs#routing-endpoints https://kit.svelte.dev/docs#routing-endpoints
- mathnmusic 5y agoHow do you run background jobs (either schedule-based or one-off like sending emails)? How do you hold a websocket channel with the client to push real-time updates? IMHO, "Full stack" means a lot more than "can talk to the database".
- nicoburns 5y agoPerhaps it means something different to the Ruby community. But I've most commonly seen "full stack" used to simply mean "both frontend and backend". So if it's running code on the server and the client then it's full-stack.
- slantyyz 5y agoFor the background jobs, you can implement that in the hooks file using your node scheduling library of choice.
- xcambar 5y agoSvelteKit enables the BFF (backend for frontend) pattern nicely, meaning it can proxy and stitch together your actual API, exposing SPA-specific endpoints. In the other hand, I don't see how you could use it as a primary backend, it just does not support anything beyond routing. Which is nice, not every tool should do everything (on the contrary) but it is important that the developers are not mistaken with regards to what SvelteKit is fit for as a backend.