Storing official runtime limits in a generic record

The situation

They needed to record the official runtime limits that affect a certain process. The current information was found in official documentation, including limits and context. A plan was in place to observe and record these limits. They had to decide how to store this information in a way that would be useful and accurate. The goal was to create a record that would prevent future mistakes and make the information easily accessible. They considered different options for storing the runtime limits, including creating a generic record or hardcoding the limits for a specific task.

What they weighed

• A generic runtime-constraints record stores provider limits as data rows and links them to the owning long-running-work and byte-stream mechanisms.

  Chosen

• A note hardcodes only the current task's limits.

What they decided

A generic runtime-constraints record stores provider limits as data rows and links them to the owning long-running-work and byte-stream mechanisms.

Why

They chose the generic record because it would allow the official limits to be reused and easily accessed. This approach also prevented the need to hardcode limits for each task, which could lead to errors and inconsistencies. The existing implementation already supported this approach, making it a practical choice. By storing the limits in a generic record, they could ensure that the information was accurate and easily available for future use.

The first step

They would write the official runtime limits into a shared knowledge note and active plan, indexed beside the existing staging note.

How they would know it worked

The success of this approach would be measured by the accuracy and completeness of the recorded limits, as well as the ease of accessing and using this information in the future.

How it turned out

Not known yet. The result is added here when it comes in.