Many IDs in our platform are returned as integers. These IDs are sequential, which means that they get bigger (and longer) over time.
If you are an app developer who stores these IDs in a database, please store them as large integers (Javascript BigInt, SQL BigInt, Java long etc) or character strings, to prevent overflow issues.
Even if a specific ID is currently compatible with the integer type, it may eventually become too long to be stored as one.
For example, board and item IDs are already too long, and subscription IDs and integration IDs will become too long in the next year or so.
Different languages and databases have various ways of handling large integers, so your experience may vary – some applications may throw an overflow error while others will handle it behind the scenes.