If you followed Microsoft’s coverage from the Build 2018 conference, you may have been as excited as we were about the new Visual Studio Live Share feature that allows instant, remote, peer-to-peer collaboration between Visual Studio users, no matter where they are. One developer could be sitting in a coffee shop and another on a plane with in-flight WiFi, and yet both can collaborate directly on code.
The “networking magic” that enables the Visual Studio team to offer this feature is the Azure Relay, which is a part of the messaging services family along with Azure Service Bus, Azure Event Hubs, and Azure Event Grid. The Relay is, indeed, the oldest of all Azure services, with the earliest public incubation having started exactly 12 years ago today, and it was amongst the handful of original services that launched with the Azure platform in January 2010.
In the meantime, the Relay has learned to speak a fully documented open protocol that can work with any WebSocket client stack, and allows any such client to become a listener for inbound connections from other clients, without needing inbound firewall rules, public IP addresses, or DNS registrations. Since all inbound communication terminates inside the
Last week, the Microsoft Build conference brought developers lots of innovation and was action packed with in-depth sessions. During the event, my discussions in the halls ranged from containers to dev tools, IoT to Azure Cosmos DB, and of course, AI. The pace of innovation available to developers is amazing. And, in case there was simply too much for you to digest, I wanted to pull together some key highlights and top sessions to watch, starting with a great video playlist with highlights from the keynotes.
Empowering developers through the best tools
Build is for devs, and all innovation in our industry starts with code! So, let’s start with dev tools. Day one of Build marked the introduction of .NET Core 2.1 release candidate. .NET Core 2.1 improves on previous releases with performance gains and many new features. Check out all the details in the release blog and this great session from Build showing what you can use today:
.NET Overview & Roadmap: In this session, Scott Hanselman and Scott Hunter talked about all things .NET, including new .NET Core 2.1 features made available at Build.
Scott Hanselman and Scott Hunter sharing new .NET Core 2.1.
With AI being top
Since we announced general availability of Azure Event Grid, we have seen great adoption and received good feedback on what else you want to do with your event-driven architectures. Today we are happy to announce public preview support for a host of new features aimed at improving your developer experience, expanding the list of Azure services that natively integrate with Event Grid, and embracing standards that allow cross cloud interop.
CloudEvents open standard support
Multi-cloud architectures for enterprise solutions had become a common trend, as customers are picking up best of breed tools and services from across multiple cloud vendors, and so they build their solutions spanning public cloud platforms and services from different vendors. We want to make sure our customers have the ability to integrate Azure services and resources on these multi-cloud solutions. As part of this effort to improve interoperability between public cloud platforms, SaaS companies and other vendors, we have been working with a number of other cloud providers on an open standard for events called CloudEvents. This project has been created in the Serverless Working Group of the Cloud Native Compute Foundation (CNCF), and we recently announced Azure being the first major public cloud to
Serverless technologies have hit a high level of maturity and awareness where several new customers from a diverse range of industries and geographies, are confidently going to production with it. While customer adoption rapidly increases (check out the stories on Stylelabs, direct.one, DEIF and NAVITIME going all serverless on Azure recently), a whole new set of scenarios is emerging where serverless is a great fit. Due to such trends, Azure serverless products are constantly innovating with new capabilities and taking existing ones to production-level, by making them generally available.
One particular area of focus for us is developer productivity, not only while writing code, but also when maintaining production apps. With this purpose, we have been working on new monitoring and diagnostics features, aiming on giving you all the resources to make your code more reliable and give you the ability to better identify and fix potential failures on your solution. Serverless is all about making developers life easier, and so are we!
In this post, I’m happy to share with you some significant advancements we made recently:
Durable Functions reach general availability
We always listen to our customers to find new ways to improve our services together, and something
As more and more serverless applications are developed, events are now the glue connecting all aspects of modern applications. These events can originate from microservices, from VMs, from the edge, or even from IoT devices. They can be fired for infrastructure automation, for application communication, as triggers from data platforms, or to connect complex analytics and AI services. The value of events is growing exponentially, there are a plethora of diverse sources and consumers of events across public clouds, private clouds, and even at the edge.
One of our major Azure innovations last year was the creation of an event-centric serverless platform, Azure Event Grid. To support the growing diversity of serverless applications, Event Grid was launched with support to use Azure’s native serverless platforms, like Azure Functions, and with support to use custom events, enabling applications to send and receive events whether on Azure or another platform.
We are now taking this open and diverse event approach further by being the first major public cloud to offer first-class support for CloudEvents as part of Event Grid. CloudEvents is a new open specification and standard for describing event data in a common and consistent way. Building on this standard will
You have heard the hype around serverless computing, read countless online articles about its benefits, and heard industry pundits find new adjectives to describe its pathbreaking nature on a frequent basis. Are you now ready to dig into what you can actually do with real code using serverless computing cloud services like Azure Functions? If so, you should download and read the free Azure Serverless Computing Cookbook that describes with rich code examples, how to solve common problems using serverless Azure Functions.
However, if you need a little more motivation, read on.
Let us get the basics out of the way first. Serverless computing enables:
Full abstraction of servers: Focusing on your application code, not on servers running the code. Instant event-driven scalability: Not worrying about scaling up infrastructure as traffic grows. Pay-per-use: Paying only for the time your code is running and the resources it consumes
However, as a developer there is so much more to it that you should care about.
Your cloud journey can start small
You don’t really have to bet your entire application portfolio on this new way of building software all at once. The good thing about the Functions-as-a-Service (FaaS) model provided
We are happy to share that Azure Service Bus is now able to send events to Azure Event Grid. The key scenario this feature enables is for Service Bus queues, topics, or subscriptions with low message volumes to not require a receiver to be polling for messages at all times. Service Bus will now send events to Azure Event Grid when there are messages in a queue if no receivers are present. You can create Azure Event Grid subscriptions for your Service Bus namespaces, listen to these events, and react to the events by starting a receiver. With this feature, Service Bus can be used in reactive programming models.
Today, Azure Service Bus sends events for two scenarios:
Active messages with no listeners available Deadletter messages available
Additionally, it uses the standard Azure Event Grid security and authentication mechanisms.
How often and how many events are emitted?
If you have multiple queues and topics/subscriptions in the namespace, you get at least one event per queue and subscription. The events are immediately emitted if there are no messages in the Service Bus entity and a new message arrives, or every two minutes unless Azure Service Bus detects an active receiver.
Are you building a new application which requires low latency at any scale? Or are you in the process of migrating your NoSQL databases to the cloud? Or looking for the right resources to help you get started with Azure Cosmos DB?
Join us for one or all of a seven-week Azure Cosmos DB technical training series, which explores the capabilities and potential of Azure Cosmos DB. Whether you’re brand new to Azure Cosmos DB or an experienced user, you’ll leave this series with a better understanding of database technology and have the practical skills necessary to get started.
Azure Cosmos DB is the world’s first globally distributed, multi-model database service with native NoSQL support. Designed for the cloud, Azure Cosmos DB enables you to build planet-scale applications that bring data to where your users are with SLA-guaranteed low latency, throughput, and 99.99% availability.
In this training series, you’ll learn everything necessary to get your cloud database up and running. In the first session, we covered a technical overview of Azure Cosmos DB, and, in the following weeks, we’ll progress into deeper topics like migrating Mongo DB applications to Azure Cosmos DB, building serverless applications, and enabling real-time analytics with