|
所在平台: Udemy |
课程主页: https://www.udemy.com/course/dynamics-365-system-performance-and-scalability/
课程评论：没有评论
**课程名称：Microsoft Dynamics 365 系统性能与可伸缩性** **课程概述：** 本课程旨在强调系统性能作为一项关键的非功能性需求，它常常在出现问题之前被忽视。投资数月开发的系统在上线后若因性能问题而失败，其后果可能十分严重，包括用户投诉和政治压力，甚至可能导致人员失业。尽管系统性能有时被视为一个难以捉摸的方面，但它实际上根植于设计模式和分布式系统架构原则。 本课程将深入探讨 Dynamics 平台内部机制，并务实地分析在企业级应用开发中应避免和缓解的设计“反模式”。这些宝贵的信息源自微软内部的系统性能研究挑战以及真实微软企业客户的解决方案，此前从未向公众披露。 **课程学习目标：** * 掌握系统性能的基础组成部分。 * 理解影响系统上线后行为的关键变量。 * 识别最常见的导致性能不佳的“负载反模式”。 * 学习在系统设计中可以主动考虑并应用于现有系统进行弥补的优化策略。 **课程定位：** 本课程并非技术性的深度解析，而是一次战略层面的概念和模式回顾，旨在帮助学习者构建高性能和可伸缩的系统。这些概念适用于开发者和业务分析师，并可用于系统架构设计讨论。虽然这些概念也能用于已存在的性能问题的缓解，但从一开始就将这些设计考虑因素纳入其中，会更加轻松且痛苦更小。
System performance is a critical non-functional requirement in any application, yet it's seldom taken into account until after it becomes a problem. The worst thing that can happen after investing months in developing a system is for it to fail after being deployed to users. User feedback and politics can be quite brutal when a system fails to meet expectations and the consequences of a poorly performing system can be severe even to the point people lose their jobs. While system performance is often times looked at as an intangible aspect of application development it's based in design patterns and distributed system architecture principles that can be addressed. In this course, we'll review Dynamics platform internals and take a pragmatic look at design anti-patterns we should avoid and mitigate in enterprise applications. This information which has never been presented to the public outside of Microsoft is derived from system performance research challenges and solutions of real world Microsoft enterprise customers. In this course you will learn: The basic components of system performanceThe variables that play into how a system will behave after go liveLoad anti-patterns that are the most common causes of poor performanceDesign considerations that we can make proactively and mitigate retroactively in existing systems This course is not meant to be technical deep dive, but rather a strategic review of the concepts and patterns that are required to build systems that perform and can scale. These concepts are applicable to both developers and business analysts alike and can be used in system architecture design conversations. While these concepts can be applied retroactively in performance mitigation scenarios it's significantly easier and less painful to build your system with these design considerations in mind.
