The first of the CloudGraphs series introduced the problem statement: Let’s represent this nifty localization data in a cloudy graph database so that it can be distributed across a cloud system. This article follows up with the preliminary architecture, attempting to answer the ‘how’ and ‘why’. Why each technology in the first post’s stack? Well, let’s start with the informal ‘back-of-napkin’ architecture diagram below.
In the interest of a bit of learning and initiating some public projects on SemiSorted, we’re taking on a cloud-based project! Dehann Fourie in the MIT CSAIL lab is working on a really impressive open-source pose estimation framework, and the idea is to learn cloud technologies by growing it into a distributed cloud solution. This whole project is a learning curve in Neo4j, MongoDB, CloudFoundry, and JuliaLang, and the articles will be written in the same way the project was executed: with haphazard enthusiasm and a bit (~lot) of hackery.
With the advent of cloud, and the race to create new business models, I’d like join in the fray and coin a new term – XaaS! XaaS stands for (Xtremely everything) as a Service! It’s a cloud business model that incorporates PaaS, SaaS, HaaS, TaaS, FaaS, GaaS, SnaaS, MCAaaS etc.