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.
-
Show this thread
-
Truly tho, data persistence is final boss in the cloud game. AppSync won't be the last thing to support hosted dbs. Pretty soon bet we'll see something from Azure. At that point Google will need something.. Prisma? ;) But seriously, do we finally have a path to db interop?
1 reply 0 retweets 1 likeShow this thread -
Replying to @brianleroux
Ideally all this stuff just goes away. Serverless = "here is code, scale it for my usage". Databaseless = "here is data, store it optimally for my usage". The next gen products will look at query patterns and figure out optimal storage and indexing
1 reply 0 retweets 1 like -
Replying to @southpolesteve
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'
1 reply 0 retweets 0 likes -
Replying to @brianleroux
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.
2 replies 0 retweets 0 likes -
Replying to @southpolesteve
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).
1 reply 0 retweets 1 like
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.
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.