Question on ActorSelection in Remote actor system: Can akka.tcp protocol be used to communicate between client & server, while client is connected to internet without a static ip allocated? And is the case similar with peer to peer communication?
As I start exploring cluster/remote and getting Akka.NET running as a service (eg: Topshelf) I'll update as I go along. If others wish to contribute, let me know. Or if @Aaronontheweb and crew would like to maintain this in the main Akka.NET repo/wiki, I'm happy to contribute there instead.
@frasermolyneux no I haven't gotten that far. Right now it's just hooking up an API and using actors to do the work. Very MVP for now.
yeah, it'd be nice to use Resource Manager and/or something like Service Fabric to handle the lifecycle of everything with rolling upgrades, etc. For now I'm using classic Azure but would like to explore better ways... when I get there. :)
Not on Azure no - I have tried that sort of thing locally and spread across multiple machines on a business network. Ideally I would like a deployment pipeline that provisions the resources it needs from Azure or another cloud company
(Preferably Azure as I get the £95pm credits in my msdn subscription)
@frasermolyneux oh and when you say you've given up on Azure, does that mean you're still running Akka.NET for your app, but just managing the individual servers yourself via AWS or some other platform? If so, wouldn't that be the same as plain old Azure VMs?