Home Game Development Tile based mostly chunk system. SQl, or NoSQL?

Tile based mostly chunk system. SQl, or NoSQL?

0
Tile based mostly chunk system. SQl, or NoSQL?

[ad_1]

I noticed, that utilizing the os file system just isn’t the perfect resolution for my IO certain recreation.

Therefore I’ve determined to make use of a database. But, I would like the precise design for good efficiency.

I do know that NoSQL can carry out higher, relying on the state of affairs. and It can map higher to OOP. Since my recreation makes use of buildings(structs) to arrange knowledge. This looks like choice.

However, it is advisable to open the whole doc to make even a small change in NoSQL. Wheres, In SQL, You solely must index the tables you want.

In My recreation, The chunks are generated solely as soon as, after which learn and modified virtually indefinitely.

Which design is healthier(Performance Wise) for my recreation?

Criticism is welcome!

[ad_2]

LEAVE A REPLY

Please enter your comment!
Please enter your name here