标签：#communication

"Auto-provisioning" is one of those features that sounds boring on a spec sheet and turns out to be doing a surprising amount of work once you look underneath it. The pitch is simple: drop in a list of users and the system spins up hundreds of configured softphones across devices in minutes, no manual setup per user. The pitch is easy. The plumbing behind it is where the interesting problems live. I've been picking this apart lately and wanted to write down what actually has to happen for "provision 500 users in minutes" to be true. What manual provisioning looks like (so you can see what's being automated away) Setting up one softphone by hand is a checklist. You create the user on the platform, assign an extension and credentials, point the client at the right SIP server, configure the transport (TLS, ports), set codecs, wire up voicemail, maybe push notification tokens, contacts, feature flags. Then you do it on their device. For one user, fine, twenty minutes. For five hundred, that's a full-time job for a week, and every manual step is a chance to fat-finger a config and generate a support ticket later. Auto-provisioning exists to make that whole checklist happen without a human running it each time. The core problem: getting config to a device that isn't configured yet The central puzzle of provisioning is a chicken-and-egg one. You want to hand a device its configuration, but the device doesn't yet know who it is or where to get that config. So the whole flow is about bootstrapping identity and config onto a blank client safely. A few common approaches: Provisioning URL + credentials: The user (or an admin) enters a provisioning username/password, or the client is pointed at a provisioning server URL. The client authenticates, the server looks up who this is, and returns the full config bundle. Simple, works, but needs the initial credential to get entered somehow. QR / activation code: Instead of typing SIP settings, the user scans a code or enters a short a

Government ban on foreign-made robots may hinder instead of help US robotics.

When a new platform team set out on implementing their roadmap through forced workflows with poor documentation, developer experience declined. Success came from simplifying governance, prioritizing what matters, and rolling out compliance incrementally through prevention, detection, and communication. Empathy, focus, and shared purpose drove successful adoption. By Ben Linders

A lot of platform teams face a problem: they build a lot of really cool stuff, and then their developers don't use it. Be visible to management, talk to stakeholders and listen to their problems, make your value measurable with metrics like DORA, create narratives, and show the hidden pain to make it personal: these are lessons that Lucas Hornung and Christian Matthaei presented. By Ben Linders

This article is part of the Comprehensive Guide to Microservices Architecture in .NET Core, Cloud and Azure series. Asynchronous Messaging with Azure Service Bus Azure Service Bus provides enterprise-grade messaging infrastructure with advanced features for reliable message delivery, ordering guarantees, and complex routing scenarios. Service Bus vs Azure Queue Storage Azure Service Bus offers enterprise messaging capabilities including: Topics and subscriptions for pub/sub patterns Message sessions for ordered processing Transaction support across operations Dead-letter queues for failed messages Messages up to 100MB (premium tier) Advanced routing with filters and actions Azure Queue Storage provides: Simple FIFO queue operations Lower cost for basic scenarios Messages up to 64KB Best for simple point-to-point messaging When to Choose Service Bus Use Azure Service Bus when you need: Publish-subscribe patterns with multiple subscribers Guaranteed message ordering with sessions Transactional message processing Message size beyond 64KB Advanced routing and filtering Integration with hybrid or on-premises systems Implementation with .NET 9 .NET 9 introduces improved performance and simplified APIs for working with Azure Service Bus: // Producer using .NET 9 with improved performance public class OrderCreatedPublisher { private readonly ServiceBusSender _sender ; public OrderCreatedPublisher ( ServiceBusClient client ) { _sender = client . CreateSender ( "order-events" ); } public async Task PublishOrderCreatedAsync ( Order order , CancellationToken cancellationToken = default ) { var message = new ServiceBusMessage ( JsonSerializer . Serialize ( order )) { MessageId = order . OrderId . ToString (), Subject = "OrderCreated" , ContentType = "application/json" , // .NET 9: Better support for distributed tracing ApplicationProperties = { [ "CorrelationId" ] = Activity . Current ?. Id ?? Guid . NewGuid (). ToString (), [ "OrderDate" ] = order . CreatedAt . ToString ( "O" )

"I don’t know of a bigger question we can answer as humans."