this is great for prototyping and for lower traffic apps. but this cannot scale as well as typical microservice architecture does. plus it’s all written in haskell and uses wrap-web .. again .. this is okay .. but i have my doubts when it comes to scaling. but might be sufficient for small scale product offerings to a specific niche.. i m not a fan of the tight coupling either tbh .. what if i need to move to exadata ? architects, engineers, devops and product managers should know that if their product goes ‘viral’ they’ll probably quickly need to move over to something like Spring/Nginx or FastCGI/Nginx or boost/Nginx .. but this is great to get up and running. thanks for sharing.
![I.N "HALLUCINATION" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/n5B5q1Hwt_U/mqdefault.jpg)
Where did you made that elephant logo of your channel?
Wish the PostGREST in a new Tembo instance would connect to the 'app' database instead of the 'postgres' db which is now the default.
Woah I didn’t know it supported query parameters like SQL less than and greater than comparisons. Neat!
Woah and pagination out of the box
this is great for prototyping and for lower traffic apps. but this cannot scale as well as typical microservice architecture does. plus it’s all written in haskell and uses wrap-web .. again .. this is okay .. but i have my doubts when it comes to scaling.
but might be sufficient for small scale product offerings to a specific niche..
i m not a fan of the tight coupling either tbh .. what if i need to move to exadata ?
architects, engineers, devops and product managers should know that if their product goes ‘viral’ they’ll probably quickly need to move over to something like Spring/Nginx or FastCGI/Nginx or boost/Nginx ..
but this is great to get up and running. thanks for sharing.
I could be mistaken, but I believe supabase is primarily built on top of postgrest. They're CTO or CEO did an AMA a while ago and mentioned it.