4 ms·
Of course you need to define some play-rules first. You could also just give them access to a read-only replication/cache.
by DarkNova6 2y ago
Of course you need to define some play-rules first. You could also just give them access to a read-only replication/cache.
- Hamuko 2y agoI'd much rather have specifically designed API endpoints that I can both optimise and to also limit how much it can be accessed than rely on some other group of developers to not go overboard, especially if they're not familiar with database performance. Although if the data team owns the database, then they're free to break their own toy as far as I'm concerned.
- DarkNova6 2y agoThat was the idea. You give them a copy of your actual DB, which is held up-to-date on a best-effort basis. If they break it, or it is too slow, it's on them. When it comes to changes of the DB schema, you must inform them but they ultimately act as conformists rather than having a Consumer/Producer relationship (which is the only way GraphQL can work imho).