问题
Let's assume, I have a REST API serving an entity. My aim is to find a way to effectively split the attributes of the entity used by Update calls (PATCH/PUT) in such a way that the resulting combination of columns are disjoint (or nearly).
If they are disjoint (best case), then it is easier, to split that given API to many sub APIs, which do not affect each other and thereby accessing disjoint columns in the table entity.This further allows to perhaps split that table to multiple sub tables.
How can I do this?
I've parsed all requests from the API, to get an output of all possible unique combinations of columns ordered (in desc) by its request count. For example,
column1-column2-column4-column7-column23 94588 {number of requests of this type in a given time frame}
column1-column2-column15-column18-column33-column45-column112 45678
column11-column22-column36-column48-column53 26790
...{assume 700K request total in the given period with around 700+ unique combinations}
来源:https://stackoverflow.com/questions/58134463/given-a-set-of-update-requests-for-a-table-how-can-i-use-this-to-split-requests