> Ok! Wait, what? Joyce allows you to ingest data from (almost) any source and expose the ingested data as standard APIs (REST, event notification) automatically. In order to specify to Joyce which data we want to pick from the incoming data stream and how APIs will look like you need to describe the expected behaviour with a DSL based on json-schema.
got it, what will you suggest to do something like that? a simple RPC with a good async framework I've read,
like what? an RPC service on top of Twisted for python, similar things in other languages?
In case (c) or (d) how can a layer leverage the distributed facilities that FDB gives?
I mean if I have clients that connect to a "layer service" that is the one who talks to FDB, I have to manage "layer service" scalabily, fault tolerance etc... by myself.
I cannot agree more.
bored of those nonsense terms distinction if you see on linkedin or the likes everyone has his own software architect, wargods of the mighty developing...
loving it, definitely
I was playing with these sort of things these months and eventually I was ending with something similar, but that is far away what I was doing.
I think I will contribute to this lib if i can instead of continuing my shit :)
Great article really!
I develop mobile application and you don't know how your software is indispensable for me :) i use it quite everyday
really appreciated
i liked it besides the name. It's a nice try of standardization of home made solution on top of WS.
the name though is bad, but it seems he has registered it :P