[フレーム]
BT

InfoQ Software Architects' Newsletter

A monthly overview of things you need to know as an architect or aspiring architect.

View an example

We protect your privacy.

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Unlock the full InfoQ experience

Unlock the full InfoQ experience by logging in! Stay updated with your favorite authors and topics, engage with content, and download exclusive resources.

Log In
or

Don't have an InfoQ account?

Register
  • Stay updated on topics and peers that matter to youReceive instant alerts on the latest insights and trends.
  • Quickly access free resources for continuous learningMinibooks, videos with transcripts, and training materials.
  • Save articles and read at anytimeBookmark articles to read whenever youre ready.

Topics

Choose your language

InfoQ Homepage News Azure Durable Functions Now Supports Storage Backends Microsoft Netherite and MSSQL

Azure Durable Functions Now Supports Storage Backends Microsoft Netherite and MSSQL

Feb 08, 2023 1 min read

Write for InfoQ

Feed your curiosity. Help 550k+ global
senior developers
each month stay ahead.
Get in touch

Microsoft recently announced that Azure Durable Functions support for the new storage providers, Netherite and Microsoft SQL Server (MSSQL), is generally available.

With Azure Durable Functions, developers can write long-running, reliable, event-driven, and stateful logic on the serverless Azure Functions platform. In addition, these functions can have several storage providers, also called "backends," for storing orchestration and entity runtime states. By default, new projects are configured to use the Azure Storage provider; however, a developer can choose another backend, including the now generally available Netherite and MSSQL.

Earlier, the company previewed the storage backends Netherite and MSSQL as new storage options allowing developers to run durable functions at a larger scale, with greater price-performance efficiency and more portability than the default Azure Storage configuration.

Microsoft Research developed the Netherite storage provider and uses Azure Event Hubs and the FASTER database technology on top of Azure Page Blobs to store state information. It provides better throughput performance achieved by representing states differently than Azure Storage – also visible through HelloCities5 benchmark tests the company conducted.


Source: https://microsoft.github.io/durabletask-netherite/#/throughput

The MSSQL provider was designed to fulfill enterprise needs, including the ability to decouple from the Azure cloud, and is compatible with both on-premises and cloud-hosted deployments of SQL Server, including Azure SQL Database, Edge devices, and Linux containers. In addition, the Azure Functions Core Tools and the Azure Arc App Service extension have been updated to support automatically configuring Durable Function apps on a Kubernetes cluster with the MSSQL KEDA scaler for elastic scale-out.


Source: https://techcommunity.microsoft.com/t5/apps-on-azure-blog/new-storage-providers-for-azure-durable-functions/ba-p/2382044

Davide Mauri, a principal product manager of Azure SQL DB at Microsoft, posted on LinkedIn:

#AzureSQL and #SQLServer can now be used to support Azure Durable Functions to scale above and beyond , anywhere you want to run them. On #Azure, On-Prem, or even in other clouds. Amazing!

With the availability of several backends, Microsoft recommends the default Azure storage provider for minimal setup and lowest minimum cost, Netherite for maximum throughput, and MSSQL to run anywhere.

Lastly, more detailed documentation on architecture, scaling, and performance is available on the github.io pages for Netherite and MSSQL.

About the Author

Steef-Jan Wiggers

Show moreShow less

Rate this Article

Adoption
Style

Related Content

The InfoQ Newsletter

A round-up of last week’s content on InfoQ sent out every Tuesday. Join a community of over 250,000 senior developers. View an example

We protect your privacy.

BT

AltStyle によって変換されたページ (->オリジナル) /