Data Limits and Cost

To ensure good performance, the HERE platform has limits on data storage and throughput. Some limits can be controlled by layer configuration, which may impact your cost since you are charged based on how you have configured the layers and data usage. As a general rule, the more data you send and receive from the HERE platform, and the more data you store, the more you will be charged. You will also be charged more if you configure layers for for higher performance.

You are charged for your use of the HERE platform based on how you have configured the layers and data usage.

Versioned Layers

Limits

• Maximum partition size: 50 GB
• We recommend that you do not exceed 24 MB/second when publishing metadata

Cost Considerations

• Usage
  • You are charged for the amount of metadata and data stored in the layer
  • You are charged based on the amount of data you read and write using the blob and metadata APIs
• Configuration
  • There are no layer configuration settings that affect cost

Volatile Layers

Limits

• Maximum partition size: 2 MB

Cost Considerations

• Usage
  • You are charged based on the amount of data you read and write using the blob API
• Configuration
  • You are charged based on the storage capacity configured for the layer. The price increases as the storage capacity increases.
  • You are charged based on the data redundancy configured for the layer. For multi-instance mode, your cost triples because two additional copies of your data are created, for a total of (3) copies, to provide durability.

Stream Layers

Limits

• We recommend that messages be smaller than 1 MB for best performance.
• Maximum throughput: Determined by the the maximum throughput setting configured for the layer. Catalogs in the HERE Marketplace have a maximum outbound throughput of 2000 KBps (Kilobytes per second).
• The maximum amount of data that can be concurrently stored in a stream layer can be calculated as follows: (inbound throughput) x (retention time).

Cost Considerations

• Usage
  • Usage does not affect cost
• Configuration
  • You are charged based on the maximum throughput configured for the layer
  • You are charged based on the retention setting configured for the layer

Index Layers

Best Practice

It is recommended to group messages with the same indexing attributes before indexing instead of storing metadata for many small files in index layer.

Cost Considerations

• Usage
  • You are charged for the amount of metadata and data stored in the layer
  • You are charged based on the amount of data you read and write using the blob and index APIs
• Configuration
  • You are charged based on the retention setting configured for the layer

Object Store Layers

Limits

• Maximum single object size: 500 GB
• There is no limit on the total storage capacity of a single layer

Cost Considerations

• Usage
  • You are charged for the amount of metadata and data stored in the layer
  • You are charged based on the amount of data you read and write using the blob API
• Configuration
  • There are no layer configuration settings that affect cost

Interactive Map Layers

Limits

• Maximum payload size is 10 MB
• Maximum uncompressed response size is 100 MB, but you can retrieve bigger results by either adding an encoding header or iterating over the result set using handles.

Cost Considerations

• Usage
  • You are charged for the amount of metadata and data stored in the layer
  • You are charged based on the amount of data you read and write using the interactive API
  • Indexing of layers happens on the fly, so no additional IO is charged, but the indexes add to the data stored.