Archtecture

[kumavis]

vapor has got me splitting things into tiny services (currently 4 going on 5), and I forgot all we talked about before but it seems like we should have:

services:

• app cdn server (just use gh-pages)
• a DAG DB ( nodes/posts with links/replies + data/audio_id ), [interfaced by levelDB]
• streaming audio binary DB server [needs research -- fs-based may be best]
• a user auth setup... is this what we're using Geddy for? I forgot about auth... We should maybe figure this out first.... could tie to existing service e.g. Twitter.

front-end:

• Mercury - I recommend since I anticipate a super minimal UI. We should get on voip and I'll walk you through the basics. or I could just throw it together and catch up later.
• DAG db interface - could do it via a stream or queries via http. Not sure if we really need the constant + stateful connection -- unless we want to tie auth session lifecycle to that connection?
• audio streaming interface -- like we currently have it, binary streaming over http

[kumavis]

@flyswatter continuing over here

seems like we almost have most of the service parts. Mainly auth and building a web interface we like.