SQLite3 and MySQL are two different things. SQLite3 operates on a single file, and MySQL is a service from a separate process. This totally depends on your individual use case.
If you don't have enough resources (CPU, RAM) use SQLite Otherwise, MySQL And for your coins EconomyAPI uses yaml by default Why you don't use it Yaml is simple to use, stores in a text file with lowest storage usage you want to store data such as playerA: 15Coins playerB: 20Coins Use SQLite and MySQL for store data such as playerA: Coins: 15 NameTag: PlAyErA CID: lwjrskvbdxhvkbdoorshghejshg
I worked with it when I was developing web applications You are right but at Theory in Working SQLite uses less than MySQL
In theory, if your traffic is high and if you have multiple processes accessing it, SQLite would use more CPU.