{"id":5111,"date":"2016-01-20T08:15:43","date_gmt":"2016-01-20T08:15:43","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/dotnet\/2016\/01\/20\/the-week-in-net-1192016\/"},"modified":"2021-09-30T13:58:13","modified_gmt":"2021-09-30T20:58:13","slug":"the-week-in-net-1192016","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/dotnet\/the-week-in-net-1192016\/","title":{"rendered":"The week in .NET – 1\/19\/2016"},"content":{"rendered":"

To read last week’s post, see The week in .NET – 1\/12\/2016<\/a>.<\/p>\n

<\/a>On.NET<\/h2>\n

Last week, we had Jonathan Chambers on the show to talk about Unity<\/a>. This week, we’ll have Don Syme<\/a>, and we’ll talk about F#<\/a>.<\/p>\n

<\/a>Package of the week #1: NATS client<\/h2>\n

Microservices and IoT both require distributed architectures where a large number of endpoints communicate fast and reliably. NATS<\/a> is a popular high-performance cloud-based messaging system that is an excellent fit for such scenarios. The .NET client for NATS<\/a> can publish over 3 million messages per second (and that’s in a VM, on a developer laptop).<\/p>\n

Here’s how you’d send a simple object on the message bus, with a subject \u201cfoo\u201d:<\/p>\n