3 ms·
I have always avoided its VS project extension. If you do only `guest executable`, it is super intuitive and you can simply create any kind of exe with any lang
by qrli 8y ago
I have always avoided its VS project extension. If you do only `guest executable`, it is super intuitive and you can simply create any kind of exe with any language/stack. The package can be created by a few lines of PowerShell scripts, which is much simpler and more stable than its VS extension.
Of course, the stateful service feature is lost. But k8s does not have that feature either.
Till now, I see its `guest executable` solution a good balance.
- algorithmmonkey 8y ago> Of course, the stateful service feature is lost. But k8s does not have that feature either. Persistent Volume Claims go a long way toward the stateful service "feature". To go another step further on stateful services, SF's stateful services are only supported in a couple languages. Where mounting a volume in K8s which will follow your container is pretty darn accessible to any language.