instead of having to use a vm to host service fabric services, have it as a service
i don't want to have a vm anywhere in the mix, just have a service where we can publish our service fabric services to.
thnx a lot
Manfred Linnert commented
had the same idea recently- and its not just about "not wanting to have a VM", in my oppinion it would fill a gap in scalability. currently the smallest usefull cluster is 3 to 5 servers.
i think people should get encouraged to write as much as possible (or almost everything) using technologies like statefull services and actors. with the need to have at least 5 servers plus a domain and a real certificate related to that domain just to get it secure,there is quite a barrier for someone starting new. i assume many wont consider it as an option because for their need having 5 servers is a total overkill, and the price to pay for them as well. so they start using traditional web-services and would need to redesign and rewrite considerably large parts of the project to switch to service fabric at a later point in time. if, like for web-services, there were a service-fabric-as-a-service, where you only register, then upload your project and it runs under some autogenerated URL, invisibly sharing the servers and resources with maybe dozens of other people and projects, many more might be encouraged to us this approach. even a student could start make his fun-projects using service-fabric. if his fun-project turns out a success he could just easily shift it to a full cluster without any changes required. also for testing new projects in early beta on the web this would be excellent. please consider this idea, i think it would drastically increase the number of people knowing,using,and loving service-fabric!