C# vs Netty: What are the differences?
What is Netty? Asynchronous event-driven network application framework. Netty is a NIO client server framework which enables quick and easy development of network applications such as protocol servers and clients. It greatly simplifies and streamlines network programming such as TCP and UDP socket server.
C# can be classified as a tool in the "Languages" category, while Netty is grouped under "Concurrency Frameworks".
"Cool syntax" is the top reason why over 280 developers like C#, while over 2 developers mention "High Performance" as the leading cause for choosing Netty.
Netty is an open source tool with 19.7K GitHub stars and 8.92K GitHub forks. Here's a link to Netty's open source repository on GitHub.
According to the StackShare community, C# has a broader approval, being mentioned in 684 company stacks & 1118 developers stacks; compared to Netty, which is listed in 11 company stacks and 14 developer stacks.
Hello, I am trying to network so that I can find a business partner that knows how to code a game/ new social media site that can be on any platform like PlayStation, web, Xbox, PC, Mac, Apple IOS, Android and so forth. If anyone is interested to hear my pich, please let me know! Thank you! Haley Kirchner
In 2015 as Xelex Digital was paving a new technology path, moving from ASP.NET web services and web applications, we knew that we wanted to move to a more modular decoupled base of applications centered around REST APIs.
To that end we spent several months studying API design patterns and decided to use our own adaptation of CRUD, specifically a SCRUD pattern that elevates query params to a more central role via the Search action.
Once we nailed down the API design pattern it was time to decide what language(s) our new APIs would be built upon. Our team has always been driven by the right tool for the job rather than what we know best. That said, in balancing practicality we chose to focus on 3 options that our team had deep experience with and knew the pros and cons of.
That left us with two options. We went a very unconventional route for deciding between the two. We built MVP APIs on both. The interfaces were identical and interchangeable. What we found was easily quantifiable differences.
We were able to iterate on our Node based APIs much more rapidly than we were our C# APIs. For us this was owed to the community coupled with the extremely dynamic nature of JS. There were tradeoffs we considered, latency was (acceptably) higher on requests to our Node APIs. No strong types to protect us from ourselves, but we've rarely found that to be an issue.
As such we decided to commit resources to our Node APIs and push it out as the core brain of our new system. We haven't looked back since. It has consistently met our needs, scaling with us, getting better with time as continually pour into and expand our capabilities.
C# and .Net were obvious choices for us at LiveTiles given our investment in the Microsoft ecosystem. It enabled us to harness of the .Net framework to build ASP.Net MVC, WebAPI, and Serverless applications very easily. Coupled with the high productivity of Visual Studio, it's the native tongue of Microsoft technology.