Home /  Stash / 

Limits

Limits

Unless noted otherwise, limits can be increased upon request. To request a limit increase, contact support.

Keyspaces

Limits for Keyspaces, which can contain many Key-Value Pairs
Resource or operationDefault limitCan be increased
Maximum number of Keyspaces10Yes
Keyspace sizeNo practical limit in terms of bytes or Key-Value PairsN/A
Throttle per account, across all Stash APIs25 requests per second (RPS)Yes
Keyspace Name length250 charactersNo
Keyspace Name allowed charactersAlphanumeric (a-zA-Z0-9), underscore (_), period (.), hyphen (-)No

Key-Value Pairs

Limits for Key-Value Pairs, which are made up of Keys and Values
Resource or operationDefault limitCan be increased
Key length255 charactersNo
Key-Value Pair size8 KB (more details)No
Precision of Number types in Values38 significant figures (more details)No
Supported string characters in ValuesUTF-8No

How is the size of a Key-Value Pair calculated?

  • The size of a Key-Value Pair is equal to: i) the number of characters in the Key, plus ii) the Value size, plus iii) 2 additional bytes of overhead.
  • The Value size is equal to: i) the number of bytes in the JSON attribute names (encoded with UTF-8 binary encoding), plus ii) the sizes of the JSON values.

You can estimate the size of JSON values with the following guidelines:

  • String values are encoded with UTF-8 binary encoding. The size of a string is the number of UTF-8-encoded bytes.
  • Number values are variable length, with up to 38 significant digits. Leading and trailing zeroes are trimmed. The size of a number value is approximately 1 byte per two significant digits + 1 byte.
  • Boolean or Null values are 1 byte in size.
  • Lists incur 3 bytes of overhead, regardless of their contents. The size of a List value is the sum of the size of its elements + 1 byte per element. The size of an empty List is just the 3 bytes of overhead.
  • Maps incur 3 bytes of overhead, regardless of their contents. The size of a Map value is the sum of the size of its string keys + the sum of the size of its elements + 1 byte per element. The size of an empty Map is just the 3 bytes of overhead.

For storage billing purposes, each Stash value requires 100 bytes of overhead for indexing.

What is the accepted range for Numeric values?

Numbers can have up to 38 significant figures.

  • Positive range: 1E-130 to 9.9999999999999999999999999999999999999E+125
  • Negative range: -9.9999999999999999999999999999999999999E+125 to -1E-130

Feedback

Have an idea for something we could improve? Page not clear? We love feedback - send us a message.

Stedi

Build EDI integrations fast, without being an EDI expert

Start building
About
ProductPricingCareersContactBlog
Follow
  1. Twitter
  2. GitHub
Backed by
AdditionBloomberg BetaFirst RoundStripeUSV
Customer AgreementService TermsPrivacy Notice

Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.