Comparison Between Shared and Exclusive Instances

LakeFormation provides different types of instances to meet customers' requirements on performance and costs in different scenarios.

NOTE:

The exclusive feature is available only to whitelisted users.

• Billing

  For details about the billing items and description of shared and exclusive instances, see Table 1 in Billing.

• Performance

  Table 1 Performance

  Item	Shared Instance	Exclusive Instance
  Deployment	Physical resources are shared, but instances are logically isolated.	Physical resources are exclusively used. The performance of an instance is not affected by other instances. You can select different specifications based on your requirements.
  QPS	2,000 requests can be sent to a shared instance per second.	The value fluctuates based on the QPS setting selected during the instance's creation.

• Functions

  Table 2 Functions

  Item	Description	Shared Instance	Exclusive Instance
  Catalog management	Allows you to create, modify, delete, and view metadata of data lake catalogs.	√	√
  Database management	Allows you to create, modify, delete, and view metadata of data lake databases.	√	√
  Table management	Allows you to create, modify, delete, and view metadata of data lake tables.	√	√
  Function management	Allows you to create, modify, delete, and view metadata of data lake functions.	√	√
  Metadata lifecycle management	Allows you to configure data deletion policies, saving space and costs and improving system flexibility.	√	√
  Metadata permission management	Allows you to authorize, remove, and view metadata.	√	√
  Data migration	Supports full or incremental migration of metadata from external services to the current LakeFormation instance for unified management.	√	√
  Permission migration management	Supports full or incremental migration of metadata permissions from external services to the current LakeFormation instance for unified management.	√	√
  Client access management	Supports unified access management. You can create an access client to establish a network connection channel for a specified client environment so that other cloud services can access LakeFormation instances.	√	√