I don't think that windows service should be thought as the only deployment option for Lighthouse. For Azure worker role is a better fit. Appharbor has its own background workers. Not to mention Mono/Linux. The key item in Lighthouse is lighthouse actors subsystem which should be configured and run wherever it is deployed. So it's a perfect candidate to add either to a separate nuget package or as a part of Akka cluster.
Yes, but at the same time, creating a lighthouse service is literally 3 lines of code + a bit of config in its simplest form.. Petabridge Lighthouse does a little bit more, you can pass command line arguments and such to it..
But we also have to keep in mind the scope of the akka.net project, we are porting what exists in java Akka. everything else is pretty much out of scope and should be hosted elsewhere
@rogeralsing I see you point about leaving Akka.NET clear and following inherited Akka model. But 3 lines of code is potentially 3 bugs. So having reusable piece of code even such small piece of code won't hurt anyone I believe. It's possible to put discovery service to a separate package as @tstojecki mentioned and I think such package will appear in form of community contribs to the project.
@tstojecki senor @annymsMthd has. You have to bear in mind that a lot of the issues that come up with Akka.Cluster when you're initially launching it have to do with two nodes racing to connect with each other, dropping the connection attempt when they realize that two are occurring at once (which is illegal,) and then waiting at random intervals to attempt to connect again.
Cassandra, Riak, and other clustered DB systems run into the same issue
and it's something that comes up more often in dev and test than production
that being said, eliminating intermittent TCP connection errors is something that we're still working on
1.0.2 resolved a lot of that
but there's still a lot more work to do
I'm just about done with the R&D I had to do to develop Petabridge's training courses (gotta pay the bills,) shifting back to full-time R&D on Akka.Cluster and Helios next week
I've personally used Akka.Remote in production under what I would consider to be very heavy workloads