Definitely compelled by GraphQL for queries and, as things are starting to mature, warming up to how GraphQL models writes (or 'mutations'). https://www.opencrud.org Still super early days! Straight up DynamoDB.DocumentClient is good enough for most purposes.
-
-
Seems to be walking in this direction. Query flexibility anyhow. Writes are so tricky here and really constrain the reads side. Idk if we can automate tradeoffs there away but fuck ya that would be 'the last DB'
-
Truth. Writes are usually where the complex business logic lives. It is common to expose a simple write call that does complex things under the hood. All of these BaaS offerings have always struggled with that. GraphQL doesn't fix the problem.
-
Ya my vibe precisely. Still dig for the reads tho! Right up until custom resolver logic is required (wherein I begin to question the proposed value again).
-
I've seen the value prob there. Tying into legacy DBs and APIs was extremely helpful in Bustle's move to serverless and eventually off those legacy systems.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.