Microsoft Technology Licensing, LLC

Kumar Gaurav Khanna

Michael M Magruder

Andrew J Pardoe

Diana Milirud

Gaye Oncul Kok

Melitta L G Andersen

Stephen Harris Toub

Gopala Krishna R Kakivaya

Raja Krishnaswamy

Eric Lynn Eilebrecht

Brian M Grunkemeyer

Girish Mittur Venkataramanappa

Thomas Lai

Manuel Alfred Fahndrich

Jan Kotas

Michael Barnett

Todd F Pfleiger

Ankur Jauhari

Richard Byers

Zhengguo Sun

Zhanliang Chen

David M Kean

Subramanian Ramaswamy

Matthew Snider

Hsu-chieh Yuan

Yogesh Kumar

Matthew Cohn

Nikola Puzovic

Jon Langdon

Alok Shriram

Eric N St John

Vipul D Patel

Manoj Singiresu

Ana Trajkovic

Mohammad Rahim Bhojani

Divya Swarnkar

Michael J Rayhelson

Michael Rousos

Weitao Su

Katherine E King

A data processing system implements techniques for provisioning and operating databases including receiving a request to provision a new database that includes multiple replicas. The data processing system provisions the new database including the plurality of replicas. The plurality of replicas includes a primary replica, one or more secondary replicas, and one or more delta replicas. The primary replica is configured to handle read and write operations. The one or more secondary replicas include a copy of data and transactional log information of the primary replica and are unable to handle write operations. The one or more delta replicas are a copy of the transactional log information of the primary replica and are unable to handle read operations or write operations.

Techniques for stateful persisted service resource reduction

Data-aware orchestration with respect to a distributed system platform enables at least lifting and shifting of pre-existing applications and associated data without developer action. A volume of a local store is created automatically in response to a container comprising a user application that is non-native with respect to the distributed system platform. The volume is then exposed to the container for use by the application to save and retrieve data. The container and local store are co-located on a compute node providing at least high availability. The application and local store can be duplicated on one or more replicas providing reliability in case of a failure. Further, partitions can be created automatically in response to declarative specification.

Data-aware orchestration

An exception handling system is described herein that provides one or more distinguished classes of software exceptions that are handled differently than other exceptions. The system treats a distinguished exception as a 'hard to catch' exception that is not passed to the catch block of program code unless a developer performs extra steps to acknowledge the distinguished nature of the exception and confirm that the program code is prepared to properly handle the exception. Exceptions that fall into this class are typically those that represent conditions from which normal exception handling practices cannot successfully recover, namely exceptions that corrupt application state. Accordingly, the system prevents the developer from catching these classes of exceptions by default unless the developer explicitly requests to have these exceptions delivered to the program code. Thus, the exception handling system encourages correct programming practices by preventing developer error by default.

Handling exceptions related to corrupt application state

An enhanced binder provides flexibility and certainty when selecting a version of a software library to load, and an enhanced loader prevents a library version vulnerable to a security flaw from being loaded. The binder can perform unification, implicit override, and/or redirection. Implicit override searches assembly-specific locations for an implicit_version, and override the previously chosen unification or other version with the implicit_version when the implicit_version is greater. The implicit_version gets updated with the individual assembly, whereas the unification_version gets updated with the framework. Redirection may override the implicit_version. Unlike redirection, an implicit_version does not recite an explicit range and is found outside application configuration files. The implicit_version is specified implicitly by the assembly without an XML declaration. Vulnerable libraries are not loaded, based on out-of-band metadata placed in response to a list of known out-of-band assemblies, an out-of-band-servicing attribute, or a custom servicing library.

Out-of-band framework libraries within applications

An error handling system is described herein that provides a facility for controlling the behavior of software when the software violates a contract condition. The system provides configurable runtime behavior that takes place when a contract fails. The error handling system provides an event that a hosting application or other software code can register to handle and that the system invokes upon detecting a contract failure. The application's response to the event determines how the system handles the failure. If the event is unhandled, the system triggers an escalation policy that allows an administrator or application to specify how the system handles contract failures. Thus, the error handling system provides increased control over the handling of contract failures within software code.

Contract failure behavior with escalation policy

A system and method for handling exceptions in a multi-threaded computing environment. Information, such as that relating to an error state or pertaining to the propagation history of an exception, is stored in a separate object from the exception object itself. The separate propagation information object is accessible to the plurality of threads that are used to execute a user task. The separate object allows rich diagnostic information pertaining to the exception and its propagation through multiple threads to be presented to the developer of the software.

Separation of error information from error propagation information

Systems and methods are described for coordinating error reporting among a plurality of managed runtimes that are concurrently executing in the same process. In accordance with various embodiments, an error reporting manager that executes concurrently in the same process as the managed runtimes coordinates error reporting among the managed runtimes in a manner that does not require the managed runtimes to be aware of each other or to communicate directly with each other.

Coordination of error reporting among multiple managed runtimes in the same process

Growing community of inventors

Woodinville, WA, United States of America

Kumar Gaurav Khanna