Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 17:27
    Aaronontheweb commented #90
  • 17:26
    Aaronontheweb commented #90
  • 17:25
    Aaronontheweb assigned #90
  • 17:16

    Aaronontheweb on dev

    Provide static GetRoutees.Insta… (compare)

  • 17:16
    Aaronontheweb closed #3974
  • 17:16
    Aaronontheweb milestoned #3974
  • 16:05
    jackowild opened #90
  • 15:08
    Aaronontheweb commented #3974
  • 15:08
    Aaronontheweb commented #3974
  • Oct 13 14:40
    cptjazz synchronize #3974
  • Oct 13 14:07
    cptjazz opened #3974
  • Oct 13 08:30
    ismaelhamed commented #3937
  • Oct 12 15:50
    IrvinDominin opened #127
  • Oct 11 18:21
    Aaronontheweb commented #3973
  • Oct 11 18:20
    Aaronontheweb commented #3937
  • Oct 11 18:16
    Zetanova commented #3937
  • Oct 11 18:11
    Zetanova commented #3937
  • Oct 11 15:09
    Aaronontheweb commented #3937
  • Oct 11 15:08
    Aaronontheweb commented #3937
  • Oct 11 14:36
    Aaronontheweb commented #3973
Roger Johansson
@rogeralsing
Maybe they were invisible for 4 years?
Bartosz Sypytkowski
@Horusiath
I don't want to be arrogant or start a flamewar, but to be honest, Akka.NET is based on concepts from Akka, and in further line from Erlang, both of them are heavily battle-tested in hundreds of applications over the course of almost 30 years in total. Orleans (and now Bioware's Orbit) at least for now are both 1-project based, and their are not core part of their projects - neither Halo nor DA:I are multiplayer-based. And while they introduce some incredibly useful ideas, I think it's still not a fair comparison.
And I'm not an Orleans hater - I want to see this framework growing. Variety is good for everyone.
Aaron Stannard
@Aaronontheweb
@rogeralsing yeah I think you and I are saying the same thign
actors are actors - CAP theorem stuff only plays a role when you start distributing them across multiple processes
Roger Johansson
@rogeralsing
Exactly
If orleans removed the broken actor constraints and just exposed always available endpoints, i would love that.
Aaron Stannard
@Aaronontheweb
and TBH, I really wish people who talk about distributed systems stuff would stop pigeonholing on CAP - yes, for the love of god, we get it. Every system has trade offs that have to be picked carefully and deliberately. Not a fundamentally different exercise than making tradeoffs in any other software system (concurrent, embedded, etc...) - just yet another new domain where developers get their butts kicked by the laws of physics and economics over time.
Roger Johansson
@rogeralsing
And let devs decide what to expose on such endpoint
Aaron Stannard
@Aaronontheweb
to your point @Horusiath - Orleans has an in-house project for many years
was*
so it's "mature" from a wall clock time perspective
but not very "mature" from an odometer perspective
Orleans has one success story
so far, hopefully they have more!
Akka has tens of thousands
as it's been open and heavily used by lots of people who are not Typesafe for years
technically speaking, Akka.NET has been publicly available longer than Orleans
they have an interesting interpretation of the actor model, although what they do does not stick to the "actor model" as it's defined in the white paper
Akka.NET is ultimately an unbiased framework - you get the actor model as a single process, a couple of remote processes, a whole cluster of different processes, or clusters of processes that use persistence for greater consistency
and lots of other combinations
Orleans is a piece of off the shelf software built for specific types of distributed apps
and has powerful tools for doing that
but you give up a lot in order to get those tools
Roger Johansson
@rogeralsing
btw. offtopic, but can you take a crash course with me on our cluster supprt? thats the module I know the least about tbh.. I know how to start up clusters and do routers, but no more :P
Aaron Stannard
@Aaronontheweb
haha, sure thing
Roger Johansson
@rogeralsing
not now that is, some day
Aaron Stannard
@Aaronontheweb
I gotta head into the office and get some lunch (probably not in that order)
released Helios v1.4 this morning
has your Mono support
Bartosz Sypytkowski
@Horusiath
we need to distribute some more learning materials about cluster and persistence
Roger Johansson
@rogeralsing
nice :)
Aaron Stannard
@Aaronontheweb
going to send a PR that turns it on in Akka.Remote
@Horusiath yes we do
I took a look at the persistence bits for the first time last weekend
realized I need to learn more about how they work
and also, apparently JVM Akka.Persistence now depends on Akka Streaming for reads
Bartosz Sypytkowski
@Horusiath
Akka.Http also will be
reactive streams are a very universal concept, just like LINQ ;)
Greg Young sent me a disscussion about Query side of akka persistence and reasons for changing it
they concern a little how journals and persistent views may be implemented, but they shouldn't change a lot in persistent actors and at-least-once delivery
Roger Johansson
@rogeralsing
Btw , we had a talk with Roland yesterday . They will wait with persistence untill streams are completed
Bartosz Sypytkowski
@Horusiath
do you think we should manage some time for implementing akka streams from our side in near future?
Roger Johansson
@rogeralsing
Streams and io , but damn, we need a bit of rest after 1.0 :)
Bartosz Sypytkowski
@Horusiath
I think, that after 1.0 we should discuss and prepare some official road map for the next features
Roger Johansson
@rogeralsing
yes
Roman Golenok
@shersh
Hi all.
Guys, what about securing and encryption between client and backend? I see examples, such as Chat sample and what if we want to encrypt messages? (Not only text, maybe binary too). Is this custom logic only or it can be part of system (for example specify in config file property "encryption: RSA") ?
Roger Johansson
@rogeralsing
we also found out that akka v 3 has changed into a module ontop of akka 2.x.. so the new typed actorrefs and changes to how sender is handled are now just a plugin on their end
Aaron Stannard
@Aaronontheweb
@shersh right now we strongly recommend running your clusters inside a private network
because we don't have any out of the box security tools yet