Foreword

前言

With the wave of cloud adoption well underway, there is a major shift happening towards “cloud native”?development,?often built with?microservice-architectures. These microservices are both stateless and stateful,?and run on the cloud and edge, embracing the diversity of languages and frameworks available today. This enterprise shift is driven by both the market forces of faster time to market, as well as the scale and efficiencies of building services for the cloud. Even before COVID-19, cloud adoption was accelerating for enterprises and developers were being asked to do even more to deliver on building these distributed system applications, and that has only accelerated since. Developers in enterprises?seek?to focus on business logic, while leaning on platforms to imbue their applications with scale, resiliency, maintainability, elasticity, and the other attributes of cloud-native architectures, which is why there is also shift towards serverless platforms that hide the underlying infrastructure. Developers should not be expected to become distributed systems experts. This is where Dapr steps in to help you, whether you are building on infrastructure such as Kubernetes, or on a serverless platform.

隨著云采用浪潮的發展，我們在 "云原生" 開發方面發生了重大轉變，通常使用微服務體系結構構建。這些微服務可以是無狀態也可以是有狀態的，可以在云上運行也可以在邊緣上運行，從而支持當今可用的各種語言和框架。驅動企業轉型因素是，更快速地回應市場需求，以及構建云服務的規模和效率。即使在 COVID-19 之前，企業和開發人員仍需要做更多的工作來交付這些分布式系統應用程序，而自那以后，云的采用速度就加快了。企業中的開發人員尋求專注于業務邏輯，同時學習依靠平臺為其應用注入擴展、彈性、可維護性、靈活性以及云原生架構的其他特征，這就是為什么也出現了向無服務平臺（隱藏基礎設施架構）的轉變原因。不應期望開發人員成為分布式系統專家。?無論您是在 Kubernetes 等基礎設施上構建，還是在無服務平臺上進行構建，Dapr 都在此介入幫助您。

Dapr is designed as an enterprise, developer-focused,?microservices programming model platform with the mantra “any language, any framework, run anywhere”. It?makes building distributed applications easy and portable across any infrastructure, from public-cloud, through?hierarchical edge, and even down to single node IoT devices.??It emerged from both our experiences building services in Azure as well as time spent working with customers building applications on Azure Kubernetes Service and Azure Service Fabric. Over and over, we saw common problems that they had to address. It became clear that there was a need to provide a “library” of common microservice best practices that developers could use, not only in new greenfield applications, but also to aid in the modernization of existing applications. In the containerized, distributed, and networked cloud native world, the sidecar model has emerged as the preferred approach, in the same way DLLs are preferred in the client/server generation. Using Dapr’s sidecar and APIs give you, as a developer, all the power of distributed systems functionality, with the ease of a single HTTP or gRPC local call.

Dapr 是一種以開發人員為中心的企業級微服務編程模型平臺，其口號是"任何語言、任何框架、隨處運行"。它使得跨任何基礎設施、公有云、分層邊緣，甚至是單節點 IoT 設備構建分布式應用程序變得簡單、可移植。它體現我們在 Azure 中生成服務的經驗，以及與客戶在 Azure Kubernetes 服務和 Azure Service Fabric 上構建應用程序所做的努力。同時，我們看到了他們必須解決的常見問題。顯然，需要提供一種可供開發人員使用的微服務最佳實踐的"庫"，不僅可以用于開發新應用，還可以幫助應對現有應用程序的現代化改造。在容器化、分布式和網絡云原生世界中，邊車模式已成為首選方式，其方式與在客戶端/服務器生時代中首選 Dll 的方式相同。使用 Dapr 的邊車和 Api，為開發人員提供了分布式系統功能的所有能力，只需使用 HTTP 或 gRPC 本地調用。

To address the wide range of scenarios that developers face, Dapr provides features such as state management, service to service invocation, pub/sub and integration to external systems with I/O bindings, which are based on the triggers and bindings of Azure Functions. These in turn take advantage of Dapr’s component model which allows you to “swap out”, say different underlying state stores, without having to change any code, making code more portable, more flexible and allowing for experimentation of what best suits your needs. Developers don’t need to learn and incorporate service SDKs into their code, worry about authentication, secret management, retries or conditional code that targets specific deployment environments.

為了解決開發人員面臨的各種情況，Dapr 提供了狀態管理、服務到服務調用、發布/訂閱和與外部系統的集成（基于輸入/輸出綁定）。它們利用了 Dapr 的組件模型，允許您可以替換（例如不同的底層狀態存儲），而無需更改任何代碼，使代碼更具可移植性，更具靈活性，并允許實驗什么最適合你的需要。開發人員無需了解服務 Sdk 并將其合并到代碼中，無需擔心身份驗證、機密管理、重試或特定部署環境相關的條件代碼。

This book shows how Dapr reduces your development time and overall code maintenance by incrementally “Daperizing” the canonical .NET reference application, eShop. For example, in the original eShop implementation, significant amounts of code were written to abstract between Azure Service Bus and RabbitMQ for publishing events between services. All this code can be discarded and simply replaced with Dapr’s pub/sub API and component model which had an even wider range of pub/sub brokers, rather than just two. Dapr’s actor model, when used in the reworked eShop application, shows the ease of building long running, stateful, event driven, workflow applications with all the difficulties of concurrency and multi-threading removed. By the end of this book, you will see the drastic simplification that Dapr brings to your application development, and I firmly believe all developers embarking on a cloud native app building journey should leverage Dapr.

本書說明了 Dapr 如何逐步簡化 標準.NET 參考應用程序 eShop，來縮短開發時間和總體代碼維護。例如，在原始 eShop 實現中，編寫大量代碼來抽象Azure 服務總線和 RabbitMQ，以在服務之間發布事件。所有這些代碼都可以丟棄，只需替換為 Dapr 的 訂閱/發布 API 和組件模型，訂閱/發布代理有很多種，不只是兩個。在修訂的eShop 應用程序中使用時，Dapr 的執行組件模型可讓你輕松構建長時間運行、有狀態、事件驅動的工作流應用程序，同時移除了并發和多線程處理的所有難題。本書結束后，您將看到 Dapr 為您的應用程序開發帶來的極大簡化，我堅信所有踏上云原生應用構建之旅的開發人員都應該利用 Dapr。

We?publicly?announced Dapr?with the v0.1?release?in Oct 2019 and now, a year and half later, I am thrilled to say that Dapr is ready for production usage with the v1.0 release. Getting Dapr to v1.0 has truly been a community effort. It has been amazing to see the open-source community coalesce around Dapr and grow since it was first announced – from 114 contributors in October 2019 to over 700 in early 2021 - a six-fold increase in 16 months! Contributions to the project have gone to every Dapr repo and have ranged from opening issues, commenting on feature proposals, providing samples, and of course contributing code. The parts of the project community members have contributed to the most include the Dapr runtime, docs, CLI, SDKs and the creation of a rich ecosystem of components. Maintaining this openness is critical to Dapr’s future.

我們已在2019年10月推出了 Dapr 的0.1 版發布，現在，我興奮不已說 Dapr ?V1.0已準備就緒以供生產使用。發布Daprv1.0確實是社區努力的結果。自Dapr首次宣布以來，Dapr開源社區聯合起來并不斷發展壯大，令人驚嘆——從2019年10月的114個貢獻者增加到2021年初的700多個——在16個月內增長了6倍！對項目的貢獻已提交到每個 Dapr 存儲庫，包括打開問題、評論功能提案、提供示例，以及貢獻代碼。?項目社區成員貢獻最大的部分包括 Dapr 運行時、文檔、CLI、SDK 和創建豐富的組件生態系統。保持這種開放性對Dapr的未來至關重要。

Dapr is really just getting started, though, and you should expect to see more Dapr capabilities and more support for Dapr in Azure services. I hope that you will take advantage of Dapr to enable you to focus on your core business logic and accelerate your microservices development. I am are excited to have you join us in the?Dapr?community on this journey at?https://github.com/dapr/?and on Discord?https://aka.ms/dapr-discord.

不過，Dapr 剛剛開始，你應該期待更多的 Dapr 功能，并在Azure 服務中為 Dapr 提供更多支持。我希望您能夠利用 Dapr 來使您能夠專注于核心業務邏輯，并加速微服務開發。我很高興有你加入我們Dapr社區的:https://github.com/dapr/?旅程和https://aka.ms/dapr-discord 。

Modern distributed systems are complex. You start with small, loosely coupled, independently deployable services. These services cross process and server boundaries. They then consume different kinds of infrastructure backing services (databases, message brokers, key vaults). Finally, these disparate pieces compose together to form an application.

現代分布式系統非常復雜。首先，你從小的、松散耦合且可部署的服務開始。這些服務跨進程和服務邊界。然后，它們使用不同類型的基礎設施支持服務 (數據庫、消息代理、key vault) 。最后，這些分散的部分組合在一起構成應用程序。

Mark Russinovich?Azure CTO and Technical Fellow?Microsoft

馬克·魯西諾維奇?Azure CTO和微軟技術研究員

總結

以上是生活随笔為你收集整理的面向.NET开发人员的Dapr——前言的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。