For what parts of a LinkedIn-type social network you would suggest to use Aerospike for (if at all)? Examples: user auth info, user short profiles, user full profiles, posts, system messages/alerts, user messages, articles, audio info, images info, video info, friends, different stats, etc. etc. As you you see, there are roughly three different groups of data with different read/write ratio and caching options:
- users + auth
- posts + messages
MVP is built using MySQL for everything except for relations - using OrientDB for traversals like “friends-of-friends”. Sure, in the far and bright future, the system will be much more sophisticated. Right now, i would just like to build a small but solid foundation, with tools correctly selected for the current needs - first users, first scaling, lean budget, and all other startup niceties.
Any advice is highly appreciated! Thank you, Dennis