3 ms·
Most likely this time A16z got invested in some bottom-of-the-heap Dev tools SAAS businesses. > And a giant hairball of queues and retry logic is too brittle.
by geodel 4y ago
Most likely this time A16z got invested in some bottom-of-the-heap Dev tools SAAS businesses.
> And a giant hairball of queues and retry logic is too brittle. To deal with this, we’ve seen, over the last few years, the emergence of new solutions that bring sanity back to transactional logic. They can be roughly categorized as either workflow-centric approaches or database-centric approaches.
Ok, using databases and queues is bad. So what is good then:
> we call this the application logic transactional platform (ALTP) approach because, ultimately, it extends OLTP transactions into the application
Really how much I will love to get few of my brain farts funded on being brilliant insights for typical enterprise application.
- Mandatum 4y agoLike GraphQL, we just moved the integration and interface design complexity to the clients. Just publish your fucking read-only SQL credentials at this point.
- theK 4y agoTo be fair, GraphQL manages to reign in the ludicrussness that is exporting a read only SQL connection to levels that are merely unpredictable instead of outright dangerous. Still probably not the tech one needs. EDIT: add last paragraph
- Kwpolska 4y agoGraphQL does not prevent you or the GraphQL→DB translation layer from doing stupid things. Depending on the capabilities exposed by the GraphQL schema and the implementation of the translation layer, you can write a GraphQL query that is translated to 20 JOINs or N+1 hell or other bad things.
- hackandthink 4y agoGraphQL flexibility is fine but you need some discipline. We have been using GraphQL for 4 years and limit ourselves to queries with simple or medium complexity (no load the world, no problems).
- amq 4y agoThe end game is normal credentials with row level security.
- rzzzt 4y agoThat's OData: http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html#_Toc453752288 http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/comp...
- deleted 4y ago[deleted]
- foosandbars 4y agoIt was too word soupy for me to read but I imagine here it is inventing something that is between event sourcing and DB journalling.
- arianvanp 4y agoAnd they list Supabase as an example which is just ... PostgreSQL?
- cies 4y agoAt least with AWS/RDS you have to pick the "Postgres" flavor.