現在只要透過 SQL Server 的好夥伴 System Center 以及 SQL Server 管理套件，可以快速提供管理者所需的資料庫效能、可用性、組態監控、效能資料蒐集等資訊。當 DB 發生問題時 System Center 會主動通知管理者並告知問題所在，協助管理者在最短時間內排除障礙。同時還包含了可自訂的儀表板檢視、圖表檢視以及問題解決知識庫，加上各種豐富的報表，讓 DBA 一手掌握所有狀況! 即時是管理不同版本的 SQL Server，System Center 也能輕鬆做到。此外，當遇到長時間執行的交易問題時，System Center 也能辨別出是哪支程式的 SQL 語法所造成，真正釐清問題的所在!
How do we use C++14 to make our code better, rather than just different? How do we do so on a grand scale, rather than just for exceptional programmers? We need guidelines to help us progress from older styles, such as "C with Classes", C, "pure OO", etc. We need articulated rules to save us from each having to discover them for ourselves. Ideally, they should be machine-checkable, yet adjustable to serve specific needs.
In this talk, I describe a style of guidelines that can be deployed to help most C++ programmers. There could not be a single complete set of rules for everybody, but we are developing a set of rules for most C++ use. This core can be augmented with rules for specific application domains such as embedded systems and systems with stringent security requirements. The rules are prescriptive rather than merely sets of prohibitions, and about much more than code layout. I describe what the rules currently cover (e.g., interfaces, functions, resource management, and pointers). I describe tools and a few simple classes that can be used to support the guidelines.
The core guidelines and a guideline support library reference implementation will be open source projects freely available on all major platforms (initially, GCC, Clang, and Microsoft).
Authentication and Authorisation can be tricky, with many different methods of performing similar tasks and it can be hard to figure out what's best for your projects. It gets even trickier when you start thinking about how to authorise cross platform applications including web and apps (and now with Xamarin thrown in, it's even murkier!). Throw in WebAPI2 on the other side and it's starting to become unclear how to make a great experience for developers and end users alike. In this session Jordan will demonstrate how to build a centralised authentication system that supports web and apps, passing claims around all over the place using Json Web Tokens ending up in a WebAPI2 based API site. The session will investigate a range of concepts from web to app to API, including best practices, Autofac powered filters, OWIN and other cool concepts that your services need!
Any sample code, video, or other supporting content for this presentation (if available for this session) is loaded in the zip file.