Geek Answers Handbook

Mobile Application - Server Architecture

I want to launch a mobile application, but I have some questions. I am confused in the database connection layer. Should I build my 2-layer architecture; Level 1 is a mobile application (connecting to a database in a mobile application), Level 2 is just a database. Or 3 layers; 1st is a mobile application, 2nd is a server (which handles the connection between the database and the application), 3rd is the database.

What are the pros and cons of these two architectures? thanks in advance

+5
source share
2 answers

The only advantage associated with the fact that the mobile application is transmitted directly to the database is that it can be implemented faster in the short term.

In a slightly longer mode, three layers are a much better choice for several reasons:

  • - (, API JSON), . , , . , , , , , . . .

  • - , .. , .

  • - , , ( № 1 - ).

  • , , , :)

- / , - Ruby, Python, PHP, Node. "" , .

+10

. . : "TODO" . , , , ().

, "TODO" , "TODO 2.0" "todo" : -, . , "TODO" . "todo" , , .

+1

More articles:


All Articles