Thanks. My project had an interruption, and I'm getting back to the code.
My code that needs a key-value store is simple, short, just uses two instances of a .NET collection class.
I need NAT (network address translation) to keep affinity of each user with their one execution instance of my code, but I suspect that is automatic with Microsoft's IIS (Iinternet Information Server) that the code uses.
For persistence, the code needs that only long enough for each user connection. And for performance, I don't need sharding across several servers acting like a cluster -- maybe that is some of what Redis supports.
It appears that .NET has more functionality and performance potential (user connections per minute) than my project needs, so I'm trying not to try to master everything Google, Facebook, Amazon, a big bank, Walmart, etc. might need! So far, I'm pleased with .NET.
My code that needs a key-value store is simple, short, just uses two instances of a .NET collection class.
I need NAT (network address translation) to keep affinity of each user with their one execution instance of my code, but I suspect that is automatic with Microsoft's IIS (Iinternet Information Server) that the code uses.
For persistence, the code needs that only long enough for each user connection. And for performance, I don't need sharding across several servers acting like a cluster -- maybe that is some of what Redis supports.
It appears that .NET has more functionality and performance potential (user connections per minute) than my project needs, so I'm trying not to try to master everything Google, Facebook, Amazon, a big bank, Walmart, etc. might need! So far, I'm pleased with .NET.