In-Progress
...
...
...
...
...
...
Overview
...
Another factor to consider is in the near future, improvements made in caching Okapi tokens will naturally eliminate the need to go to mod-authtoken on every API call to get the same type of resource (
Jira Legacy |
---|
server | FOLIO Issue TrackerSystem JIRA |
---|
serverId | 6ccf3fe401505d01-3301b853-368a3c2e-983e90f1-20c466b11a49ee9b165564fc |
---|
key | MODAT-83 |
---|
|
). Additionally, there might be an improvement in the way to lookup a one-record result that'd not execute SELECT count_estimate() in the database, thus it may not be as taxing on the database's memory (
Jira Legacy |
---|
server | FOLIO Issue TrackerSystem JIRA |
---|
serverId | 6ccf3fe401505d01-3301b853-368a3c2e-983e90f1-20c466b11a49ee9b165564fc |
---|
key | RMB-724 |
---|
|
). If these improvements were made in the near future, concatenating UUIDs may not gain as much benefit.
Recommended Improvements
Jira Legacy |
---|
server | FOLIO Issue TrackerSystem JIRA |
---|
serverId | 6ccf3fe401505d01-3301b853-368a3c2e-983e90f1-20c466b11a49ee9b165564fc |
---|
key | RMB-724 |
---|
|
Jira Legacy |
---|
server | FOLIO Issue TrackerSystem JIRA |
---|
serverId | 6ccf3fe401505d01-3301b853-368a3c2e-983e90f1-20c466b11a49ee9b165564fc |
---|
key | MODAT-83 |
---|
|