Azure #CosmosDB: Case study around RU/min with the Universal Store Team

%3CLINGO-SUB%20id%3D%22lingo-sub-76498%22%20slang%3D%22en-US%22%3EAzure%20%23CosmosDB%3A%20Case%20study%20around%20RU%2Fmin%20with%20the%20Universal%20Store%20Team%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-76498%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20Universal%20Store%20Team%20(UST)%20in%20Microsoft%20is%20the%20platform%20powering%20all%20%E2%80%9Cstorefronts%E2%80%9D%20of%20Microsoft%20assets.%20These%20storefronts%20can%20be%20web%2C%20rich%20client%2C%20or%20brick%20mortar%20stores.%20This%20includes%20the%20commerce%2C%20fraud%2C%20risk%2C%20identity%2C%20catalog%2C%20and%20entitlements%2Flicense%20systems.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20team%2C%20in%20the%20UST%2C%20streams%20user%20engagement%20of%20paid%20applications%2C%20such%20as%20games%2C%20in%20near%20real-time.%20This%20data%20is%20used%20by%20Microsoft%20Fraud%20systems%20to%20identify%20if%20a%20customer%20is%20eligible%20for%20refund%20upon%20request.%20The%20streaming%20data%20is%20ingested%20to%20Azure%20Cosmos%20DB.%20Today%2C%20this%20usage%20data%20along%20with%20other%20insights%20provided%20by%20the%20Customer%20Knowledge%20platform%20forms%20the%20key%20factors%20in%20the%20refund%20decision.%20Since%20this%20infrastructure%20is%20used%20for%20UST%20Self-Serve%20refund%2C%20it%20is%20imperative%20that%20we%20drive%20down%20the%20operation%20cost%20as%20much%20as%20possible.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAzure%20Cosmos%20DB%20was%20chosen%20primarily%20for%20three%20reasons%2C%20guaranteed%20SLAs%2C%20elastic%20scale%2C%20and%20global%20distribution.%20It%20is%20crucial%20for%20the%20data%20store%20to%20keep%20up%20with%20the%20incoming%20stream%20of%20events%20with%20guaranteed%20SLAs.%20The%20storage%20needed%20to%20be%20replicated%20in%20order%20to%20serve%20refund%20queries%20faster%20across%20multiple%20regions%20with%20support%20for%20disaster%20recovery.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20455px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F15571i1A6B4396F3A5FEE7%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22cosmosdb.png%22%20title%3D%22cosmosdb.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ERead%20about%20it%20on%20the%20Azure%20blog.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-76498%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Community Manager

The Universal Store Team (UST) in Microsoft is the platform powering all “storefronts” of Microsoft assets. These storefronts can be web, rich client, or brick mortar stores. This includes the commerce, fraud, risk, identity, catalog, and entitlements/license systems.

 

The team, in the UST, streams user engagement of paid applications, such as games, in near real-time. This data is used by Microsoft Fraud systems to identify if a customer is eligible for refund upon request. The streaming data is ingested to Azure Cosmos DB. Today, this usage data along with other insights provided by the Customer Knowledge platform forms the key factors in the refund decision. Since this infrastructure is used for UST Self-Serve refund, it is imperative that we drive down the operation cost as much as possible.

 

Azure Cosmos DB was chosen primarily for three reasons, guaranteed SLAs, elastic scale, and global distribution. It is crucial for the data store to keep up with the incoming stream of events with guaranteed SLAs. The storage needed to be replicated in order to serve refund queries faster across multiple regions with support for disaster recovery.

 

cosmosdb.png

 

Read about it on the Azure blog.

0 Replies