Storing data that needs to be obtained in the mobile application

I have seen many examples of extracting data from websites to be used as application content. Now I am developing my own application, I have my own content for my users, where should I store my content so that it can be retrieved from my application? Is this a server? Or a cloud? I've done some research on Parse, AWS, Google Cloud Platform, they all seem pretty confusing to me. Is it correct that this is the correct approach to storing application content?

Please help and give me some advice. I have no experience with these, sorry ...

+3


source to share


1 answer


My rule of thumb is someone who only knows Google and Amazon AWS.

If the data is images / movies / files: use AWS S3 or Google Cloud Storage

If the data is text, use the database system:

  • For RDBMS like MySQL use AWS RDS or Google Cloud SQL
  • For NoSql: AWS SimpleDb, DynamoDb. On Google Cloud, MongoDb hosting is a tutorial .

You don't need a dedicated service to host the database, but we pay for its performance.



All file metadata (like url, name, etc.) must be stored in the database. Then create a server to serve a so-called REST API in the cloud, which acts as a brain to connect all the dots, manage data work, and as much preprocessing as possible so that your user devices aren't burdened. You can instantiate a cloud for starters for cheap on AWS EC2 or Google Cloud Engine.

Example example: tracking custom downloads

It's very simple. The key is not to specify the image url right away, but to wrap it in a request. Let's say the image is a photo .jpg, and the user who downloads or requests it is Bob (we usually get information about the user through the login to the application, and we are most interested not in the name, but in the email or social media credentials). This way you can create a server to handle the request via http://www.example.com/track?name=bob&image=photo

The server uses all of the Bob, Photo, and possibly time and place if necessary, and then store these values ​​in your database when processing. Then you return the real url photo.jpg as the response to Bob's request. That's it, you have Bob.

0


source







All Articles