The issue here is how easy it would be to swap a backend if any service is captured or down. I appreciate that at least with a DVM there should be a spec of the complex querying
Discussion
The current proposal for DVMs has all the right parts already. Whichever DVMs answer your event, which describes your query, are the ones up and running. If you find any of them suspect, you can filter either on client or user level. We just don’t have enough of them built yet.
Could be. But the DVM spec is absurdly complex for something like a query
I might be a little naive, thinking that anyone else might use a content search DVM I’m building for my own use, but I find the idea of interchangable microservices and cross-implementations fascinating.
Yes. It's very cool. Just my opinion that DVM spec too contrived for a synchronous API with no payment. Maybe could have a simpler one for those cases