LEAP DAY 1: Azure Messaging

January 26, 2018 by rdagumampan

**Cross Platform - open source commitment **
Scott Hunter, Director

Scott shared the many different things at Microsoft that are open source. Primarily the vNext features of .NET Core and ASP.NET Core. Core promises to work on both Windows and Linux platforms. There is strong push right now to make .NET Core applications to be microservice ready. That is, small, faster to build, containerized, monitoring-built in.

.NET Core 2.0

  • faster build
  • GDPR
  • microservices and azure
  • faster internal engineering system

.NET Core 2.1 (vNext)

  • Span<T>
  • Tensor<T>
  • Sockets
  • Smaller install size
  • 10x client performance

ASP.NET Core 2.1 (vNext)

  • SignalR
  • HTTPS by default
  • GDPR
  • IHttpClientFactory (caching, retry logic)
  • 6x throughput on in-proc hosting
  • Identity
  • Webhooks

Action Items

  • Try out .NET Core 2.1 + SQL Server + Windows Container + Service Fabric

References

Azure Messaging
Dan Rosanova

It was late and quite heavy so I hardly capture much out of this session. But the key takeway here is that choosing the right messaging architecture must be drive by these three questions:

  • What are you doing
  • What you care about
  • What are you willing to give up to get it

It make perfect sense. It you want ultra-low latency then you may have to give-up atomicity or absolute consistency. The consistency requirements for financial transaction is different from telemetry, log or data streaming. Again, it’s what we care about and what are we willing to give up.

Dan shared interesting stats from Azure, pretty impressive

  • 1.2 trillion requests/day
  • 2 million topics in prod
  • 99.9998% success rate
  • > 30 PB monthly data volume
  • 42 regions
  • 750 billion messages on Azuer Service Bus

References

© 2017 | About | Contact | Follow me on Twitter | Powerered by Hucore & Hugo