Performance regarding API calling

I need to “create or update” a language table(the are 28 different language tables) depending on the language settings of the user so I have two options.

  1. On the client, check the users’s language and the use the save API
Backendless.Data.of(SpanishRanking.class).save(ranking); 

This way I need to set up a handle onBeforeCreate to check if this user is already on the table.
I support ranking separated in 28 languages(28 tables) so I would need handlers for all of them. But I call 28 different APIs right? one for every language(every table)
2. Make a service API passing the language id, and in the server check if the user exist in the appropiate table and then call save. So all the users would call the same service API

MY QUESTION is : given a is there any performance difference between 1 and 2 ?

Thank you

Alfredo,

I recommend creating a small prototype for both 1 and 2 and comparing the performance between the approaches.

Regards,
Mark

Thanks for the advice.