If we rewrite our backend for better performance, what will we use?
Basic
9
Ṁ394resolved Oct 6
ResolvedN/A
48%
Prisma
25%
Postgresql
9%Other
4%
GraphQL / Apollo server
2%
Vercel Serverless Functions
1.8%
Nest.js
1.4%
Planetscale
1.2%
Redis
1.2%
Firestore
1.1%
Supabase Database
Kind of a continuation of https://manifold.markets/Austin/what-database-will-manifold-be-prim . Conditional on us starting on a more performant (eg 2x speed improvement?) implementation of trading, what will that be built on?
If the condition is met, will resolve to my subjective assessment of how important each piece of the backend is. If I were to resolve it today, I'd put it at 60% Firestore, 30% Firebase Cloud Functions, 10% Vercel Serverless Functions (but happy to hear arguments for other weights)
Some context:
[James]
One thing Marshall and I were discussing last week was that we might want to migrate the trading system first to another DB and then run that side-by-side with firebase before migrating everything else
I still think we would prefer to prioritize getting the mechanisms right for our different market types, e.g. limit orders, numeric, fixed multiple choice and free response markets
But another idea would be to build the new Free Response directly on the other db
[Marshall]
so maybe 1. get limit orders in 2. say that binary markets are basically "done" and start prototyping binary markets on fast DB
[Austin]
incidentally, I would strongly want Backend v2 to support txns out-of-the-box
uh a globally queryable table of every movement of any token (M$, shares, NFTs, etc) between any two parties (users, smart contracts, charities, bank of manifold)
which is the ultimate source-of-truth and then also can be used to reconstruct the full history of Manifold
Jul 1, 2:37pm: Resolves to N/A if we haven't chosen a path forward by market close time
This question is managed and resolved by Manifold.
Get
1,000and
3.00
1,0003.00Sort by:
@JoyVoid +1 for graphql, I'm very used to it after working at Meta, and not having to create new endpoints for every little thing really speed things up.
React-like framework with nicer syntax/bindings for truly reactive code. No more useEffect dependencies! Solid : React :: Svelte : Vue.
https://www.youtube.com/watch?v=hw3Bx5vxKl0
Its metaframework (NextJS equivalent) is SolidStart https://docs.solidjs.com/start/getting-started/what-is-solidstart
Aims to be Ruby on Rails but for React (convention over configuration); prioritizes developer experience heavily; cuts out both Rest and GraphQL somehow.
Vercel : NextJS :: https://www.flightcontrol.dev/ :: Blitz
@Austin I've found it interfaces awesomely with Postgres. But it's mostly agnostic with respect to how you store data, it's basically another layer of API between backend and the database.
I've already praised the merits of GraphQL for backend API, so most of them also applies here :D ... Having a strong type system really is awesome
@JoyVoid This one is pretty interesting to me! Looking through https://www.prisma.io/blog/graphql-vs-firebase-496498546142 , which makes good arguments that Firebase isn't the best fit moving forward for us