|
|
|
|
|
|
by nycdotnet
2557 days ago
|
|
|
We use .NET Core at Namely and we are generally super happy with it. About half of our new services are in C# with .NET core using protobufs/gRPC in Linux Docker containers on Kubernetes talking to Postgres, Redis, and Kafka; the other half are Go but otherwise same stack. That’s all free/open source stuff. .NET Core is super fast and has a generally pretty small memory footprint. It works great with our ELK stack monitoring tools, our perf analytics tools - all the same stuff our other apps running on Linux containers/k8s use - because it’s also running on Linux in Docker on k8s. Most of our .NET devs use Windows desktops because we support some legacy .NET apps too, but several of our .NET devs use Macs and either VS Code or vim to work on our .NET Core services; as far as I know, this works well for them. They certainly are fast with implementing stuff when asked. Why isn’t it more popular if it’s super fast and works great on Linux? Well, I think it is true that there are some memories of startups wanting to avoid Microsoft tech; I think that cousins TypeScript and VS Code are in the vanguard here. But the fact is that there are still a handful of lego pieces that are still not around yet that would really help; for example, Kafka streams only works with JVM languages. MS just released an open source Spark client for .NET which
had a JVM bridge layer. It would be really interesting if that were extended to allow arbitrary interoperability with the JVM. Other than that, I think it’s getting there and it might take a few more years for things to sink in to common knowledge. .NET has only been fully open source and running on Linux for a very short time, relatively speaking, and I find it’s still common for people to be surprised when they hear it. |
|
|