Explore topic-wise InterviewSolutions in Current Affairs.

You can use the Azure Cosmos DB global replication PORTAL pane to add a region and then fail over to the REQUIRED region. For instructions, SEE DEVELOPING with multi-region Azure Cosmos DB accounts.

You can use the Azure Cosmos DB global replication portal pane to add a region and then fail over to the required region. For instructions, see Developing with multi-region Azure Cosmos DB accounts.

You can use the Azure Cosmos DB PORTAL’s global replication settings to add REGIONS that are suitable for your APPLICATION. To develop a globally distributed application, you should also add your application with the Preferred Location information SET to the LOCAL region for providing low read latency.

You can use the Azure Cosmos DB portal’s global replication settings to add regions that are suitable for your application. To develop a globally distributed application, you should also add your application with the Preferred Location information set to the local region for providing low read latency.

No, you can create and use existing Azure Table storage assets without interruption of any KIND. However, if you do not use the Table API, you cannot BENEFIT from the automatic index, the ADDITIONAL consistency option, or global distribution.

No, you can create and use existing Azure Table storage assets without interruption of any kind. However, if you do not use the Table API, you cannot benefit from the automatic index, the additional consistency option, or global distribution.

YES, the same API is SUPPORTED.

Yes, the same API is supported.

Not at this TIME.

Not at this time.

You can use the capacity estimator to CALCULATE the Table Throughput that's REQUIRED for the operations. For more information, see Estimate Request Units and Data Storage. In general, you can represent your ENTITY as JSON and provide the NUMBERS for your operations.

You can use the capacity estimator to calculate the Table Throughput that's required for the operations. For more information, see Estimate Request Units and Data Storage. In general, you can represent your entity as JSON and provide the numbers for your operations.

You can USE the Table API Metrics PANE to MONITOR requests and STORAGE usage.

You can use the Table API Metrics pane to monitor requests and storage usage.

Azure COSMOS DB is designed to provide unlimited storage via the use of horizontal scaling. The service can MONITOR and EFFECTIVELY increase your storage.

Azure Cosmos DB is designed to provide unlimited storage via the use of horizontal scaling. The service can monitor and effectively increase your storage.

AzCopy and the Azure COSMOS DB Data Migration TOOL are both SUPPORTED.

AzCopy and the Azure Cosmos DB Data Migration Tool are both supported.

Yes, you can connect by CREATING two separate INSTANCES of the CloudTableClient, each pointing to its own URI via the connection string.

Yes, you can connect by creating two separate instances of the CloudTableClient, each pointing to its own URI via the connection string.

YES, the Table API SUPPORTS OData query and LINQ query.

Yes, the Table API supports OData query and LINQ query.

YES, OPTIMISTIC concurrency is PROVIDED via the use of the ETag MECHANISM.

Yes, optimistic concurrency is provided via the use of the ETag mechanism.

There is SUPPORT for POWER Shell. AZURE CLI support is not CURRENTLY available.

There is support for Power Shell. Azure CLI support is not currently available.

You can USE the Azure Storage EXPLORER.

Tools with the flexibility to TAKE a connection string in the format specified previously can support the new Table API. A list of table tools is provided on the Azure Storage CLIENT Tools page.

You can use the Azure Storage Explorer.

Tools with the flexibility to take a connection string in the format specified previously can support the new Table API. A list of table tools is provided on the Azure Storage Client Tools page.

NONE. There are no changes for EXISTING or new CUSTOMERS who are using the existing AZURE Table storage SDKs.

None. There are no changes for existing or new customers who are using the existing Azure Table storage SDKs.

For information about config SETTINGS, see Azure Cosmos DB capabilities. Some settings are HANDLED on the CreateCloudTableClient method and other VIA the app.config in the APPSETTINGS section in the client application.

For information about config settings, see Azure Cosmos DB capabilities. Some settings are handled on the CreateCloudTableClient method and other via the app.config in the appSettings section in the client application.

You can share your feedback in any of the following ways:

• User voice
• MSDN FORUM
• Stack OVERFLOW

You can share your feedback in any of the following ways:

No, EXISTING storage SDKs should still work. HOWEVER it is recommended that one always GETS the latest SDKs for the BEST support and in many cases superior performance. See the list of available languages in the Introduction to Azure COSMOS DB Table API.

No, existing storage SDKs should still work. However it is recommended that one always gets the latest SDKs for the best support and in many cases superior performance. See the list of available languages in the Introduction to Azure Cosmos DB Table API.

The Azure COSMOS DB Table API is available in the Azure portal. First you must sign up for an Azure subscription. After you've SIGNED up, you can add an Azure Cosmos DB Table API account to your Azure subscription, and then add TABLES to your account.

You can find the supported languages and associated quick-starts in the Introduction to Azure Cosmos DB Table API.

The Azure Cosmos DB Table API is available in the Azure portal. First you must sign up for an Azure subscription. After you've signed up, you can add an Azure Cosmos DB Table API account to your Azure subscription, and then add tables to your account.

You can find the supported languages and associated quick-starts in the Introduction to Azure Cosmos DB Table API.

The quickest way to connect to the Azure Cosmos DB API for MongoDB is to head over to the Azure portal. GO to your account and then, on the left navigation menu, click QUICK Start. Quick Start is the best way to GET code snippets to connect to your database.

Azure Cosmos DB enforces strict security requirements and standards. Azure Cosmos DB accounts require authentication and secure communication via SSL, so be sure to use TLSv1.2.

The quickest way to connect to the Azure Cosmos DB API for MongoDB is to head over to the Azure portal. Go to your account and then, on the left navigation menu, click Quick Start. Quick Start is the best way to get code snippets to connect to your database.

Azure Cosmos DB enforces strict security requirements and standards. Azure Cosmos DB accounts require authentication and secure communication via SSL, so be sure to use TLSv1.2.

The Azure Cosmos DB API for MongoDB is a compatibility LAYER that allows applications to easily and transparently communicate with the native Azure Cosmos DB DATABASE engine by using existing, community-supported Apache MongoDB APIs and DRIVERS. Developers can now use existing MongoDB tool chains and skills to build applications that take advantage of Azure Cosmos DB. Developers benefit from the unique capabilities of Azure Cosmos DB, which include auto-indexing, BACKUP MAINTENANCE, financially backed service level agreements (SLAs), and so on.

The Azure Cosmos DB API for MongoDB is a compatibility layer that allows applications to easily and transparently communicate with the native Azure Cosmos DB database engine by using existing, community-supported Apache MongoDB APIs and drivers. Developers can now use existing MongoDB tool chains and skills to build applications that take advantage of Azure Cosmos DB. Developers benefit from the unique capabilities of Azure Cosmos DB, which include auto-indexing, backup maintenance, financially backed service level agreements (SLAs), and so on.

Yes. The Azure Cosmos DB Emulator provides a high-fidelity emulation of the Cosmos DB service. It supports functionality that's identical to Azure Cosmos DB, including SUPPORT for creating and querying JSON documents, provisioning and scaling collections, and executing stored procedures and triggers. You can develop and test APPLICATIONS by using the Azure Cosmos DB Emulator, and DEPLOY them to Azure at a global scale by making a single configuration change to the connection endpoint for Azure Cosmos DB.

Yes. The Azure Cosmos DB Emulator provides a high-fidelity emulation of the Cosmos DB service. It supports functionality that's identical to Azure Cosmos DB, including support for creating and querying JSON documents, provisioning and scaling collections, and executing stored procedures and triggers. You can develop and test applications by using the Azure Cosmos DB Emulator, and deploy them to Azure at a global scale by making a single configuration change to the connection endpoint for Azure Cosmos DB.

Yes, because Azure Cosmos DB is a RESTful service, resource LINKS are immutable and can be cached. DocumentDB API CLIENTS can specify an "If-None-Match" HEADER for reads against any resource-like document or collection and then update their local copies after the SERVER VERSION has changed.

Yes, because Azure Cosmos DB is a RESTful service, resource links are immutable and can be cached. DocumentDB API clients can specify an "If-None-Match" header for reads against any resource-like document or collection and then update their local copies after the server version has changed.

You can bulk-insert documents into Azure Cosmos DB in EITHER of two WAYS:

• The data MIGRATION tool, as described in Database migration tool for Azure Cosmos DB.
• STORED procedures, as described in Server-side JavaScript PROGRAMMING for Azure Cosmos DB.

You can bulk-insert documents into Azure Cosmos DB in either of two ways:

The DocumentDB API supports language-integrated transactions via JavaScript-stored procedures and TRIGGERS. All database operations inside scripts are executed under SNAPSHOT isolation. If it is a single-partition collection, the execution is scoped to the collection. If the collection is partitioned, the execution is scoped to DOCUMENTS with the same partition-key value within the collection. A snapshot of the document versions (ETags) is taken at the START of the transaction and committed only if the script SUCCEEDS. If the JavaScript throws an error, the transaction is rolled back.

The DocumentDB API supports language-integrated transactions via JavaScript-stored procedures and triggers. All database operations inside scripts are executed under snapshot isolation. If it is a single-partition collection, the execution is scoped to the collection. If the collection is partitioned, the execution is scoped to documents with the same partition-key value within the collection. A snapshot of the document versions (ETags) is taken at the start of the transaction and committed only if the script succeeds. If the JavaScript throws an error, the transaction is rolled back.

The DocumentDB API supports optimistic CONCURRENCY control (OCC) through HTTP entity tags, or ETags. Every DocumentDB API resource has an ETag, and the ETag is set on the server every time a document is updated. The ETag header and the current VALUE are included in all response messages. ETags can be used with the If-Match header to allow the server to decide whether a resource should be updated. The If-Match value is the ETag value to be checked against. If the ETag value matches the server ETag value, the resource is updated. If the ETag is no longer current, the server rejects the OPERATION with an "HTTP 412 Precondition failure" response CODE. The client then re-fetches the resource to ACQUIRE the current ETag value for the resource. In addition, ETags can be used with the If-None-Match header to determine whether a re-fetch of a resource is needed.

The DocumentDB API supports optimistic concurrency control (OCC) through HTTP entity tags, or ETags. Every DocumentDB API resource has an ETag, and the ETag is set on the server every time a document is updated. The ETag header and the current value are included in all response messages. ETags can be used with the If-Match header to allow the server to decide whether a resource should be updated. The If-Match value is the ETag value to be checked against. If the ETag value matches the server ETag value, the resource is updated. If the ETag is no longer current, the server rejects the operation with an "HTTP 412 Precondition failure" response code. The client then re-fetches the resource to acquire the current ETag value for the resource. In addition, ETags can be used with the If-None-Match header to determine whether a re-fetch of a resource is needed.

The DOCUMENTDB API SUPPORTS low-latency aggregation at any scale VIA aggregate functions COUNT, MIN, MAX, AVG, and SUM via the SQL grammar.

The DocumentDB API supports low-latency aggregation at any scale via aggregate functions COUNT, MIN, MAX, AVG, and SUM via the SQL grammar.

The SQL query language is an enhanced subset of the query functionality that's SUPPORTED by SQL. The Azure Cosmos DB SQL query language PROVIDES rich HIERARCHICAL and relational operators and extensibility via JavaScript-based, user-defined functions (UDFs). JSON grammar allows for modeling JSON documents as TREES with labeled nodes, which are USED by both the Azure Cosmos DB automatic indexing techniques and the SQL query dialect of Azure Cosmos DB.

The SQL query language is an enhanced subset of the query functionality that's supported by SQL. The Azure Cosmos DB SQL query language provides rich hierarchical and relational operators and extensibility via JavaScript-based, user-defined functions (UDFs). JSON grammar allows for modeling JSON documents as trees with labeled nodes, which are used by both the Azure Cosmos DB automatic indexing techniques and the SQL query dialect of Azure Cosmos DB.

You can create users and permissions by USING one of the Cosmos DB API SDKS or the REST APIS.

You can create users and permissions by using one of the Cosmos DB API SDKs or the REST APIs.

You can CREATE databases by using the Azure PORTAL, as described in Add a COLLECTION, ONE of the Azure Cosmos DB SDKs, or the REST APIs.

You can create databases by using the Azure portal, as described in Add a collection, one of the Azure Cosmos DB SDKs, or the REST APIs.

A collection is a group of documents and their associated JavaScript application logic. A collection is a billable entity, where the COST is determined by the throughput and USED storage. Collections can span one or more partitions or servers and can scale to handle practically unlimited volumes of storage or throughput.

Collections are also the BILLING entities for Azure Cosmos DB. Each collection is billed hourly, based on the provisioned throughput and used storage SPACE.

A collection is a group of documents and their associated JavaScript application logic. A collection is a billable entity, where the cost is determined by the throughput and used storage. Collections can span one or more partitions or servers and can scale to handle practically unlimited volumes of storage or throughput.

Collections are also the billing entities for Azure Cosmos DB. Each collection is billed hourly, based on the provisioned throughput and used storage space.

Yes, the DocumentDB API supports cross-document transactions expressed as JavaScript-stored PROCEDURES and triggers. Transactions are scoped to a single partition within each collection and executed with ACID semantics as "all or nothing," isolated from other concurrently executing CODE and user requests. If exceptions are thrown through the server-side execution of JavaScript application code, the ENTIRE transaction is rolled back.

Yes, the DocumentDB API supports cross-document transactions expressed as JavaScript-stored procedures and triggers. Transactions are scoped to a single partition within each collection and executed with ACID semantics as "all or nothing," isolated from other concurrently executing code and user requests. If exceptions are thrown through the server-side execution of JavaScript application code, the entire transaction is rolled back.

Yes, the DocumentDB API allows APPLICATIONS to store arbitrary JSON documents without schema definitions or HINTS. DATA is immediately AVAILABLE for query through the Azure Cosmos DB SQL query interface.

Yes, the DocumentDB API allows applications to store arbitrary JSON documents without schema definitions or hints. Data is immediately available for query through the Azure Cosmos DB SQL query interface.

Samples for the DocumentDB API .NET, Java, Node.js, and Python SDKS are AVAILABLE on GitHub.

Samples for the DocumentDB API .NET, Java, Node.js, and Python SDKs are available on GitHub.

Microsoft DocumentDB API is available in the Azure portal. First you MUST sign up for an Azure subscription. Once you sign up for an Azure subscription, you can add DocumentDB API container to your Azure subscription. For instructions on adding an Azure Cosmos DB account, see Create an Azure Cosmos DB database account. If you had a DocumentDB account in the past, you now have an Azure Cosmos DB account.

SDKs are available for .NET, Python, Node.js, JavaScript, and Java. Developers can also USE the RESTful HTTP APIs to interact with Azure Cosmos DB resources from VARIOUS PLATFORMS and languages.

Microsoft DocumentDB API is available in the Azure portal. First you must sign up for an Azure subscription. Once you sign up for an Azure subscription, you can add DocumentDB API container to your Azure subscription. For instructions on adding an Azure Cosmos DB account, see Create an Azure Cosmos DB database account. If you had a DocumentDB account in the past, you now have an Azure Cosmos DB account.

SDKs are available for .NET, Python, Node.js, JavaScript, and Java. Developers can also use the RESTful HTTP APIs to interact with Azure Cosmos DB resources from various platforms and languages.

AZURE Cosmos DB is present ACROSS all Azure REGIONS, as specified on the Azure regions page. Because it is the core service, every NEW datacenter has an Azure Cosmos DB presence.

When you set a region, remember that Azure Cosmos DB RESPECTS sovereign and government clouds. That is, if you create an account in a sovereign region, you cannot replicate out of that sovereign region. Similarly, you cannot enable replication into other sovereign locations from an outside account.

Azure Cosmos DB is present across all Azure regions, as specified on the Azure regions page. Because it is the core service, every new datacenter has an Azure Cosmos DB presence.

When you set a region, remember that Azure Cosmos DB respects sovereign and government clouds. That is, if you create an account in a sovereign region, you cannot replicate out of that sovereign region. Similarly, you cannot enable replication into other sovereign locations from an outside account.

The PREFERRED LOCATIONS VALUE can be set to any of the Azure regions in which COSMOS DB is available. For a LIST of available regions, see Azure regions.

The Preferred Locations value can be set to any of the Azure regions in which Cosmos DB is available. For a list of available regions, see Azure regions.

A master key is a security token to ACCESS all resources for an account. Individuals with the key have read and write access to all resources in the database account. Use caution when you distribute master keys. The PRIMARY master key and SECONDARY master key are AVAILABLE on the Keys blade of the Azure portal.

A master key is a security token to access all resources for an account. Individuals with the key have read and write access to all resources in the database account. Use caution when you distribute master keys. The primary master key and secondary master key are available on the Keys blade of the Azure portal.

Azure Cosmos DB is available in the Azure portal. First, SIGN up for an Azure subscription. After you've SIGNED up, you can add a DocumentDB API, Graph API (Preview), Table API, or MongoDB API account to your Azure subscription.

Azure Cosmos DB is available in the Azure portal. First, sign up for an Azure subscription. After you've signed up, you can add a DocumentDB API, Graph API (Preview), Table API, or MongoDB API account to your Azure subscription.

YES, you can sign up for a time-limited account at no CHARGE, with no commitment. To sign up, visit Try Azure Cosmos DB for free or read more in the Try Azure Cosmos DB FAQ.

If you are new to Azure, you can sign up for an Azure free account, which gives you 30 days and and a CREDIT to try all the Azure services. If you have a Visual Studio subscription, you are also eligible for free Azure credits to use on any Azure service. 

You can also use the Azure Cosmos DB Emulator to DEVELOP and test your application locally for free, without CREATING an Azure subscription. When you're satisfied with how your application is working in the Azure Cosmos DB Emulator, you can switch to using an Azure Cosmos DB account in the cloud.

Yes, you can sign up for a time-limited account at no charge, with no commitment. To sign up, visit Try Azure Cosmos DB for free or read more in the Try Azure Cosmos DB FAQ.

If you are new to Azure, you can sign up for an Azure free account, which gives you 30 days and and a credit to try all the Azure services. If you have a Visual Studio subscription, you are also eligible for free Azure credits to use on any Azure service. 

You can also use the Azure Cosmos DB Emulator to develop and test your application locally for free, without creating an Azure subscription. When you're satisfied with how your application is working in the Azure Cosmos DB Emulator, you can switch to using an Azure Cosmos DB account in the cloud.

For details, refer to the Azure Cosmos DB pricing details page. Azure Cosmos DB usage CHARGES are determined by the number of provisioned CONTAINERS, the number of hours the containers were online, and the provisioned THROUGHPUT for each container. The term containers here refers to the DocumentDB API collection, Graph API graph, MongoDB API collection, and Table API tables.

For details, refer to the Azure Cosmos DB pricing details page. Azure Cosmos DB usage charges are determined by the number of provisioned containers, the number of hours the containers were online, and the provisioned throughput for each container. The term containers here refers to the DocumentDB API collection, Graph API graph, MongoDB API collection, and Table API tables.

There is no limit to the total amount of throughput that a container can support in Azure Cosmos DB. The KEY IDEA is to distribute your workload roughly EVENLY among a sufficiently large number of PARTITION keys.

There is no limit to the total amount of throughput that a container can support in Azure Cosmos DB. The key idea is to distribute your workload roughly evenly among a sufficiently large number of partition keys.

There is no limit to the TOTAL amount of DATA that a container can store in AZURE Cosmos DB.

There is no limit to the total amount of data that a container can store in Azure Cosmos DB.

Yes, Azure Cosmos DB is HIPAA-compliant. HIPAA ESTABLISHES requirements for the use, DISCLOSURE, and safeguarding of individually IDENTIFIABLE health information.

Yes, Azure Cosmos DB is HIPAA-compliant. HIPAA establishes requirements for the use, disclosure, and safeguarding of individually identifiable health information.

Key/value (table), columnar, document and graph data models are all natively supported because of the ARS (atoms, records and sequences) design that Azure Cosmos DB is built on. Atoms, records, and sequences can be EASILY mapped and projected to various data models. The APIs for a subset of models are available RIGHT now (DocumentDB, MONGODB, Table, and Graph APIs) and others specific to additional data models will be available in the future.

Azure Cosmos DB has a schema agnostic indexing engine capable of automatically indexing all the data it ingests without requiring any schema or secondary indexes from the developer. The engine relies on a set of logical index layouts (inverted, columnar, tree) which decouple the storage layout from the index and query processing SUBSYSTEMS. Cosmos DB also has the ability to support a set of wire protocols and APIs in an extensible manner and translate them efficiently to the core data model (1) and the logical index layouts (2) making it uniquely capable of supporting multiple data models natively.

Key/value (table), columnar, document and graph data models are all natively supported because of the ARS (atoms, records and sequences) design that Azure Cosmos DB is built on. Atoms, records, and sequences can be easily mapped and projected to various data models. The APIs for a subset of models are available right now (DocumentDB, MongoDB, Table, and Graph APIs) and others specific to additional data models will be available in the future.

Azure Cosmos DB has a schema agnostic indexing engine capable of automatically indexing all the data it ingests without requiring any schema or secondary indexes from the developer. The engine relies on a set of logical index layouts (inverted, columnar, tree) which decouple the storage layout from the index and query processing subsystems. Cosmos DB also has the ability to support a set of wire protocols and APIs in an extensible manner and translate them efficiently to the core data model (1) and the logical index layouts (2) making it uniquely capable of supporting multiple data models natively.

A request unit (RU) is the measure of throughput in Azure Cosmos DB. A 1-RU throughput corresponds to the throughput of the GET of a 1-KB document. Every operation in Azure Cosmos DB, including reads, writes, SQL queries, and stored procedure executions, has a deterministic RU value that's based on the throughput required to COMPLETE the operation. INSTEAD of thinking about CPU, IO, and memory and how they each affect your application throughput, you can think in terms of a single RU measure.

You can reserve each Azure Cosmos DB container with provisioned throughput in terms of RUs of throughput per second. For applications of any scale, you can BENCHMARK individual requests to measure their RU values, and PROVISION a container to handle the total of request units ACROSS all requests. You can also scale up or scale down your container's throughput as the needs of your application evolve.

A request unit (RU) is the measure of throughput in Azure Cosmos DB. A 1-RU throughput corresponds to the throughput of the GET of a 1-KB document. Every operation in Azure Cosmos DB, including reads, writes, SQL queries, and stored procedure executions, has a deterministic RU value that's based on the throughput required to complete the operation. Instead of thinking about CPU, IO, and memory and how they each affect your application throughput, you can think in terms of a single RU measure.

You can reserve each Azure Cosmos DB container with provisioned throughput in terms of RUs of throughput per second. For applications of any scale, you can benchmark individual requests to measure their RU values, and provision a container to handle the total of request units across all requests. You can also scale up or scale down your container's throughput as the needs of your application evolve.

Azure COSMOS DB is a good choice for new web, mobile, gaming, and IOT APPLICATIONS where AUTOMATIC scale, predictable performance, fast order of millisecond response times, and the ability to query over schema-free data is important. Azure Cosmos DB lends itself to RAPID development and supporting the continuous iteration of application data models. Applications that manage user-generated content and data are common use cases for Azure Cosmos DB.

Azure Cosmos DB is a good choice for new web, mobile, gaming, and IoT applications where automatic scale, predictable performance, fast order of millisecond response times, and the ability to query over schema-free data is important. Azure Cosmos DB lends itself to rapid development and supporting the continuous iteration of application data models. Applications that manage user-generated content and data are common use cases for Azure Cosmos DB.

In the AZURE portal, CLICK the Azure Cosmos DB icon in the left pane. If you had a DocumentDB account before, you now have an Azure Cosmos DB account, with no change to your BILLING.

In the Azure portal, click the Azure Cosmos DB icon in the left pane. If you had a DocumentDB account before, you now have an Azure Cosmos DB account, with no change to your billing.

The DocumentDB API is ONE of the supported APIs and DATA models for Azure Cosmos DB. In ADDITION, Azure Cosmos DB supports you with Graph API (Preview), Table API and MONGODB API. 

The DocumentDB API is one of the supported APIs and data models for Azure Cosmos DB. In addition, Azure Cosmos DB supports you with Graph API (Preview), Table API and MongoDB API. 

Azure Cosmos DB is a GLOBALLY replicated, multi-model database service that that offers RICH querying over schema-free data, helps deliver configurable and reliable performance, and enables rapid development. It's all achieved through a managed platform that's backed by the power and reach of Microsoft Azure.

Azure Cosmos DB is the right solution for web, mobile, gaming, and IoT applications when predictable throughput, high AVAILABILITY, low latency, and a schema-free data model are key requirements. It delivers schema flexibility and rich indexing, and it includes multi-document transactional support with INTEGRATED JavaScript.

Azure Cosmos DB is a globally replicated, multi-model database service that that offers rich querying over schema-free data, helps deliver configurable and reliable performance, and enables rapid development. It's all achieved through a managed platform that's backed by the power and reach of Microsoft Azure.

Azure Cosmos DB is the right solution for web, mobile, gaming, and IoT applications when predictable throughput, high availability, low latency, and a schema-free data model are key requirements. It delivers schema flexibility and rich indexing, and it includes multi-document transactional support with integrated JavaScript.