New answers tagged

0

Technically, your gameserver is already an API used by clients as an intermediary to communicate with the database. API does not necessarily mean web service API. A service-oriented architecture (SOA) has several advantages: When you have multiple consumers, then you can offer a static interface which is decoupled from the implementation details. This is ...


1

You can do whichever one you want. Note that the second option is more work. Note that the database is already an API, so if you want to put your own API on top of that API you'd better have a good reason for it. There are some good reasons, like if you want to make it possible to drastically change the database system later. If you use MySQL and the game ...


Top 50 recent answers are included