At DataStax, I focus on enabling developers to succeed with Apache Cassandra, Apache Pulsar, Stargate and K8ssandra. Formerly @SpringCentral and @ElasticCloud.
In using something like blitz.js, I'd be concerned about coupling frontend directly to databases -- the model, view, controller pattern MVC was created years ago to avoid this and the brittleless that ensues in terms of maintaining the code / application.
Yeah it is a concern, but it is not as bad as before if implemented correctly, for example the react components can be designed in such a way that their interface with the data is abstracted so as far as the components are concerned the data can come from REST/GraphQL or the database. If decoupled and designed this way then it is just the case of swapping those adaptors in the future if needed.
In using something like blitz.js, I'd be concerned about coupling frontend directly to databases -- the model, view, controller pattern MVC was created years ago to avoid this and the brittleless that ensues in terms of maintaining the code / application.
Yeah it is a concern, but it is not as bad as before if implemented correctly, for example the react components can be designed in such a way that their interface with the data is abstracted so as far as the components are concerned the data can come from REST/GraphQL or the database. If decoupled and designed this way then it is just the case of swapping those adaptors in the future if needed.
"If implemented correctly" is doing a lot of work there. That is way too rare a beast to depend on.
ETA: And the abstraction you're describing is... MVC.
The answer if we are coming full circle is likely yes then 😅