Functions That Use the DB
BACKND Base
In BACKND Base, user authentication is performed when all features are called regardless of type, and 0.5 to 2 read and write throughputs occur at this time.
This means if DB usage occurs, the DB usage(read, write throughput) of the feature + user authentication throughput will occur.
In the case of the following three methods: server time lookup, server status lookup, and server version lookup, there are no read and write throughputs.
| Function | Description |
|---|---|
| Game operation | DB usage occurs when you use announcements, events, and policy features. |
| 1:1 Inquiry | DB usage occurs when you use the 1:1 inquiry feature. |
| Game information | DB usage occurs for the size of the data used when inserting, modifying, looking up, or deleting game information. |
| Game user | DB usage occurs when using features that exist in game user management. |
| Ranking | DB usage occurs when using the ranking features. DB usage for one-time update and lookup is almost the same regardless of the number of users. If you use the column reset feature when initializing the ranking, the DB usage will occur according to the number of users who participated in the ranking. |
| (Old) General ranking | DB usage occurs when using the general ranking feature. If the number of users increases, DB usage may increase in proportion to the number of users when updating the ranking. |
| (Old) Real-time ranking | DB usage occurs when using the real-time ranking feature. DB usage for one-time update and lookup is almost the same regardless of the number of users. |
| Coupon management | Aside from the DB usage that occurs during the user authentication process, there is no DB usage. |
| Push message settings | DB usage occurs when saving and deleting push tokens. |
| Game log | DB usage occurs when saving and looking up game logs. |
| Chart management | Aside from the DB usage that occurs during the user authentication process, there is no DB usage. Chart data size and DB usage are irrelevant. |
| Probability management | Aside from the DB usage that occurs during the user authentication process, there is no DB usage. Probability chart data size and DB usage are irrelevant. |
| User search | DB usage occurs when searching users. |
| Mail feature | DB usage occurs when using the mail feature. |
| Message feature | DB usage occurs when using the message feature. |
| Guild feature | DB usage occurs when using the guild feature. |
| Real-time notifications | Real-time notifications themselves do not use DB. |
| BACKND Function | Aside from the DB usage that occurs during the user authentication process, there is no DB usage. However, DB usage may occur when calling BACKND Base features within BACKND Function. |
BACKND Match
| Function | Description |
|---|---|
| Matching card list lookup | DB usage occurs in the user authentication process and matching card list lookup. |
| Match/in-game server access | DB usage occurs during the user authentication process. |
| Exchanging data from match / in-game server | DB usage does not occur. |
| Match result compilation | DB usage occurs in the process of saving results. |
| Matching result lookup | DB usage occurs in the process of looking up results. |
BACKND Chat
| Function | Description |
|---|---|
| Channel list lookup | DB usage occurs in the user authentication process and channel list lookup. |
| Chat server access | DB usage occurs during the user authentication process. |
| Chat, whisper exchange | DB usage does not occur. |
| Block user | DB usage does not occur. |
| Report user | DB usage occurs. |
Console
DB fees are incurred the same as for SDK when looking up data in the console.