> 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.
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.
Yes, and that's the main advantage of choosing (a) or (b). But it's not quite as hard as it sounds; since all your state is safely in fdb you "just" have to worry about load balancing a stateless service.
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?
According to the person who is actually leaking this pictures to popular forums, he acquired many of the pictures either by trading or buying them from the -real- hackers on one of those shady online marketplaces.
He claims the hackers got them from iCloud hacks, and other more social engineering hacks.
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...
