[tluyben2]

Is this really a problem? We don't have too many issues using currently (and older) technologies to make this work well enough for production systems. The focus on the frontend of things is nice though and we know how to make API's (fast), however, is someone fixing any of this for the data? So I want to make a React JS and after that React Native app, I want it to work (mostly) online and offline; it needs to have solid SEO for some pages and no SEO is needed at all for others (behind login). I want to store / sync data in our store and I need to call a bunch of API's and present and/or store locally and/or server the results. There are technologies enough; Parse server, Hoodie, Couch/Pouch, Meteor, Realm, REST API's, Websockets etc however they all only solve a (small) part; is anyone working on or is there something that would allow me to simply annotate connections specifying their behaviour (sync server->client, client<->server, client->server, what the sync behaviour is, how long data is valid, caching behaviour, how to resolve conflicts etc etc over different backends => our problem with picking any 'nosql' backend is that we really don't want to; we can just add a UUID in the REST api or give the synching code some 'hash' function of what 'unique' is etc) without having to do all that manually?

We can handle it fine manually but we notice we are basically doing everything all over again in a next project and putting that in libs now to be open sourced (maybe someone can use it), however that is for C# and I'm now wondering if there is something like it for JS already ; we cannot be the only ones having these deja vu's with every project?