Defining domains, and creating the architecture that our distributed system is going to be built upon, inherently starts with deciding on the persistence store. In return, data domains can be defined and access models can be designated. In most cases, this decision does not need to be limited to a single data store, but the system can make use of multiple data types and different data stores. The Azure platform offers various resources with different data management concepts and feature sets. It is important to choose a data store model that is best suited to the application requirements and take account of cost and management. Let's take a look at these different models and when to use them.
Germany
Slovakia
Canada
Brazil
Singapore
Hungary
Philippines
Mexico
Thailand
Ukraine
Luxembourg
Estonia
Lithuania
Norway
Chile
United States
Great Britain
India
Spain
South Korea
Ecuador
Colombia
Taiwan
Switzerland
Indonesia
Cyprus
Denmark
Finland
Poland
Malta
Czechia
New Zealand
Austria
Turkey
France
Sweden
Italy
Egypt
Belgium
Portugal
Slovenia
Ireland
Romania
Greece
Argentina
Malaysia
South Africa
Netherlands
Bulgaria
Latvia
Australia
Japan
Russia