We are adding a new guardrail around event sizes. In addition to the existing rate limits there will now be a 10 Kib size limit to any event emitted to the platform.
This guardrail is being introduced to ensure events remain concise and purpose-driven, as they are not intended to transmit large amounts of data. By limiting event sizes, we aim to reduce unnecessary load on the platform, improve performance, and maintain the scalability and reliability of our services. These limits also encourage more efficient data practices by developers, helping to optimize event handling and processing
These new size limits will be enforced starting December 16th, 2024.
I think strictly speaking it should be 10 KiB, which is the same as 10 KB or 10.24 kB.
Back in the day we used to use kb to mean 1024 bytes, unless someone was trying to sell us disc drives where we knew it might mean 1000 bytes (by this time drives had reached Gb sizes where 1 Gb usually meant 1000 Mb but 1 Mb could still be either 1024 kb or 1000 kb, and similarly for 1 kb). However b could also mean bits, and k was often written as K as it wasn’t being used as an SI prefix. We coped.
Somewhere in time the convention of using k to only mean 1000, as in SI units, with K for 1024 crept in, as did using B for bytes. Then KiB was introduced to further avoid ambiguity.
I still tend to use kb ambiguously and write bits in full. I can still automatically write numbers SI style but often don’t because avoiding word wrap can be a hassle.
Have to say that 10 KiB still sounds jolly large for events.