How to organize an application server?

Question

Java

Hello everybody! I am writing an application for Android, and I needed a server. The application sends data to the server and downloads the same data to the application on request (for example, on other smartphones). Data on the server is planned to be added, deleted and, accordingly, also dynamically loaded (VPS / VDS technologies).
For example, like Avito: created --> sent --> server received, etc.
How to do it all? :\ Wrote applications that used sockets. Servlet technologies are also known. But I don't think this is what I need.
Please answer how can I organize this server? What software to use? What to read on this topic? And then I don’t understand where I need to start dancing.
Thank you.

Answer 1

in all such questions, parse.com is advised, there are already more than a dozen of them - look,
and if you want everything yourself, take, for example, spring. You will zasharashish on it rest service, and forward.

Answer 2

Third-party services, specific jap all this is the tenth thing
1. Read what RESTful API is
2. Analyze all the screens and functionality
3. Write documentation (you need it first of all, not the customer, it will make life much easier when writing a client and a server)
4 . Go to bed.
Point 4 in all seriousness, after writing the documentation, it is worth looking at it with a fresh look.
If there is an idea what kind of asshole wrote this, then go back to point 1) if not, don’t be upset, but proceed with the implementation, most likely it will appear in the process)))
For the client, I recommend a bunch of retrofit + gson
For the server, you know something better, in any adequate language with normal web tools there are tools to facilitate the creation of the rest of the server
, here is an example for php (uses the slim microframework, without knowing php it’s quite possible to figure it out in a day)
www.androidhive.info/2014/ 01/how-to-create-rest-ap...
www.androidhive.info/2014/01/how-to-create-rest-ap...
if Java can take a closer look at Spring or something like that, but it's harder there.
In general, the main thing to keep in mind is the idea that everything is much simpler than it seems, the client does not care what the server is written on.

Answer 3

start with TK.