Am Samstag, 14. Juni 2014 18:24:34 UTC+2 schrieb rkuhn:
13 jun 2014 kl. 08:27 skrev Carsten Saathoff car...@kodemaniak.de
javascript::
Am Freitag, 13. Juni 2014 07:39:15 UTC+2 schrieb Evan Chan:
On Wednesday, June 11, 2014 2:35:27 AM UTC-7, Carsten Saathoff wrote:
And there is another
Hi Evan,
10 jun 2014 kl. 02:26 skrev Evan Chan vel...@gmail.com:
Hi Roland,
Thanks for thoughts...
On Thursday, June 5, 2014 6:57:38 AM UTC-7, rkuhn wrote:
Data Flow Topology
- Akka is pretty good at this already, supporting many types of data flow.
The only concern I see is that
13 jun 2014 kl. 08:27 skrev Carsten Saathoff cars...@kodemaniak.de:
Hi Evan,
Am Freitag, 13. Juni 2014 07:39:15 UTC+2 schrieb Evan Chan:
On Wednesday, June 11, 2014 2:35:27 AM UTC-7, Carsten Saathoff wrote:
And there is another aspect. Especially for larger projects microservices are
IMO using CBOR[1] payloads inside CoAP[2] for device-uniservice comms
seems like a really good match.
It would also mesh well (read: be proxyable) with JSON payloads inside REST
over HTTP
This would also solve (in a standardized way) service discovery etc. On the
backend Akka Cluster paired with
Hi Carsten,
On Wednesday, June 11, 2014 2:35:27 AM UTC-7, Carsten Saathoff wrote:
And there is another aspect. Especially for larger projects microservices
are great to enforce a share nothing philosophy. Using akka
serialization, I either have to share the messages or use protobuf + code
Hi,
Am Donnerstag, 5. Juni 2014 15:57:38 UTC+2 schrieb rkuhn:
thanks for bringing this up! We have been discussing similar things at
Akka HQ, so far without the ability to dedicate resources to such an
effort. I agree with Thomas that Actors already cover the basics, I would
call the
It seems to me that service discovery could be well addressed by CRDTs,
maybe an OR-Set or MC-Set. In the spare time that I never seem to have, I
had thought about grabbing Patrik's CRDT lib and trying to implement
service discovery on it to learn more about CRDTs. Fingers crossed, one of
On Mon, Jun 9, 2014 at 2:58 PM, Brian sculldugg...@gmail.com wrote:
It seems to me that service discovery could be well addressed by CRDTs,
maybe an OR-Set or MC-Set. In the spare time that I never seem to have, I
had thought about grabbing Patrik's CRDT lib and trying to implement
service
Hi Brian,
You're thinking of the case where the nodes are not members of an Akka Cluster,
right? So you can keep track of any service.
How would you detect that a service is down? ZK has persistent nodes and
monitors it's connections (which has both up and downsides). If an expiry is
Hi Evan,
In my head it's similar to Netflix's Eureka project, the server component
would be the cluster and clients could be either cluster members or systems
that would use a ClusterClient under the covers to talk to the cluster.
This would then support any service hooked in to the cluster.
Hi Roland,
Thanks for thoughts...
On Thursday, June 5, 2014 6:57:38 AM UTC-7, rkuhn wrote:
*Data Flow Topology*
- Akka is pretty good at this already, supporting many types of data
flow. The only concern I see is that you have to define the flow via the
like of routers and such, which
Hey guys,
I would like to run an idea by the fine Akka community - which is to
discuss what it would take to turn Akka into a platform for building a
network of microservices: each one independently redeployable and easy to
change, yet through a common platform, take advantage of the
12 matches
Mail list logo
