|
|
|
|
|
by everforward
740 days ago
|
|
Is there a reason you can't do both? I.e. use PostgREST until you can't anymore (and hopefully get an MVP out of that), then create a backend that runs in parallel and implements whatever PostgREST can't? It's tech debt that will likely need to be cleaned up at some point, but endpoints could be migrated one at a time, as needed. It seems fairly clean as far as dealing with tech debt goes. |
|