CODEWITHSUNDEEP
iphoneiosnode.jscore-dataamazon-web-services
jakenberg
jakenberg

Reputation: 2113

Cloud storage options with iOS

I'm trying to create a back-end in which I can have many users communicate with each other amongst an iPhone app I'm creating. I've tried working with Core Data, Google App Engine, Google Cloud Storage, and Amazon Web Services (RDS & Elastic Beanstalk). Unfortunately, after weeks of trying to get any of this working, none of it will!

I've been trying to get in touch with someone who would know how startups (when they were little) like Instagram, Path, and Pinterest have managed to do this. But everyone out there seems to despise this stuff as much as I'm growing to...

I would love for someone to simply map out EXACTLY how I need to create a back-end database that I can save and query data to and from that many users can see. That means that just SQLite, Core Data, or Parse by itself isn't going to work here!

A tutorial of some kind would be incredible.

Upvotes: 5

Views: 1819

Answers (1)

bryanmac
bryanmac

Reputation: 39306

First off, technologies like CoreData and sqlite are typically local device storage. Local device storage is not going to get you shared cloud storage.

Parse.com is a fast way for devices to access cloud storage and get going fast. Especially useful for games and other mobile apps to access cloud data via an app id and app key. It's simple storage to avoid creating your own backend if it fills all your needs and requirements.

When you get to a multi-tenant cloud backend where you roll your own services and multiple devices accessing your cloud application you need to look into exposing your web API. Exposing RESTful API over http is great for devices and web clients. Exposing the data as JSON is especially conventient for the web and easily consumed by devices.

Those web service end points in the cloud access some sort of backend storage which is optimized for concurrent access by mutliple clients. This is typically a SQL backend like MySQL, SQLServer etc... or a NoSQL solution like mongodb, couchDB, etc...

Some front end web api technologies to look into:

Some back end storage technologies to look into:

If the data is used by many many multi-tenant clients, the backends can scaled up (larger and larger) or get sharded. Sharding is where the data for multiple users is split into many databases or datastores with some sort of lookup algorithm for requests to find where that users data is stored. The front end web api servers abstract the backend storage.

Finally, you'll end up needing some sort of caching/fast lookup technology (if you're successful :):

  • Redis: fast in memory storage over sockets
  • memcached: facebook uses - simple key value in memory caching across many front end servers.

Your question is an open ended up broad question so start by googling many of these terms and technologies.

Each of these links will have resources and tutorials. Get a cloud VM, play with each and decide which fits your needs best. There is no one size fits all solution.

Upvotes: 7

Related Questions