Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/parthpaghdal0/supabase-sveltekit-example
https://github.com/parthpaghdal0/supabase-sveltekit-example
Last synced: about 2 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/parthpaghdal0/supabase-sveltekit-example
- Owner: parthpaghdal0
- Created: 2024-03-11T10:07:15.000Z (10 months ago)
- Default Branch: main
- Last Pushed: 2024-03-11T10:10:14.000Z (10 months ago)
- Last Synced: 2024-04-22T15:05:46.446Z (9 months ago)
- Language: TypeScript
- Size: 87.9 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# SvelteKit and Supabase app
## Demo, testing, prototyping, etc. Mainly for learning.### Basic architecture
I have tried to separate client and server logic as much as possible. The basic idea is that the client should _never_ directly communicate with any endpoint (at all).
This shall be the responsibility of the "Services" (perhaps it would be more prudent to call them controllers, though)
So basically:
Client -> Service -> Endpoint -> Supabase.
# Why? #
The reason I do it this way is mainly because I want to see if it is possible to maintain this architecture as the project grows. I believe it will scale well when and if the application grows. It may seem to be over-engineered (and maybe it is) but I think that it will in the long run improve code readability and prevent "boilerplate code redundancy". Components/pages will all have common entry into the the "inner workings" of the application via the services, to ensure that every request will be processed identically.