The Tangle of APIs: Are We Over-Complicating Interactions?
Every action on a web application triggers a cascade of network calls. Take t...
For further actions, you may consider blocking this person and/or reporting abuse
What about data abstraction and aggregation, business logic validations, reporting, monitoring, logging, integration with other services and so on.
Will all this be on the client side as well.
This seems applicable only for very simple/prototype applications, I am not sure this can scale well ...
The title says goodbye CRUD APIs, not goodbye to "data abstraction and aggregation, business logic validations, reporting, monitoring, logging, integration with other services and so on"
The purpose here is not scaling up, but scaling down: utilizing simpler approaches for simpler problems.
Which seemed to be a forgotten art for a long time, and now finally back.
I think we are on same page that this works only for very simple solutions.
I am not against using simple solutions to simple problems, but I would prefer a solution that also gives flexibility to extend the application.
Otherwise the oversimplified solution will just be road block.
The new becomes old, the old becomes new again.
Direct SQL access, then rpc, then rest, then back to direct SQL access via this electricSQL. Have we learnt nothing?
Also, sounds like Meteor - what's different about this?
Apples and oranges - Meteor doesn't proactively/optimistically fetch and locally cache data changes - I think that's what sets this solution apart ... I just wonder how feasible this is and how well it works in reality.
Right
The history repeats itself 😊
:D
Interesting idea, in theory I can see this work - its practical viability depends on how well this has been implemented (i.e. all of its corner cases).
Found this interesting enough to bookmark it.
P.S. people who compare this with Meteor and say "what's new" have not read the article, or have missed the point: it proactively fetches and locally caches data changes to eliminate roundtrip "lag" ... just wondering how well this works in reality.
After HTMX, here ElectricSQL comes. There are always incredibly innovative engineers who are more than ready to put this industry into a loop.
Do we have anything like this for MongoDB
You probably want to look for MongoDB Change Stream
Maybe Realm + Atlas
mongodb.com/docs/realm/
If you're a Flutter user you might be better off opting for Powersync.
The security implications of this are hard to fathom. So i can just run some ecma in my console and create 1M comments on a site?