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 on 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:
Stephan is an ex-Microsoft delivery architect for Microsoft Consulting Service. During his time at Microsoft he created business solutions using Microsoft Dynamics 365 CRM, Office 365 and Azure. He has 20 years of software development experience, 16 years of consulting experience and 7 years of enterprise project experience. He's worked with some of Microsoft's largest fortune 500 customers. As a delivery architect, he lead the software development teams that built large-scale enterprise CRM solutions. He was also a member of the interviewing team that would screen candidates applying to work for Microsoft. After receiving years of training from Microsoft he is bringing his product knowledge and experience to the Dynamics community.