Trawiller embryo

assumptions.md

@@ -1 +1,5 @@
 # Assumptions
+- App is for internal public as per requirement "... Travix wants to launch its own [specialized] micro-blogging platform"
+- Leveraging the infra structure to AWS is not an impediment
+- The project design assumes that the team members are comfortable with NodeJs and working in an Agile fashion
+- This is a high overview of a general architecture. Details might be ommited or missed due to time constraints

questions.md

@@ -1 +1,7 @@
 # Questions
+1. Is Trawiller meant to be used by internal personel?
+2. Should Trawiller support multi languages?
+3. Is there any constrains about budget
+4. Is there any constriants about technology?
+5. How many resources would be available
+6. Assuming that the app is meant for internal public, should we consider some sort of prizes for those who are actively posting relevant content?

scale.md

@@ -1 +1,9 @@
 # Scale
+There are a couple of alternatives that we can follow:
+
+- We can leverage Autoscaling with AWS
+- Move the server infra from Vertical Scaling to Horizontal Scaling
+- At this point, it's probably better to have the database in another server too
+- Consider moving static files (such as css, html and images) to CDN servers	
+
+Source: http://tinyurl.com/j46m9ha

solution.md

@@ -1 +1,21 @@
 # Solution.md
+For the conception of Trawiller, several architectural options were studied. Because this kind of platform is traffic intensive and the need to react fast to changes is a must, it became clear that a distributed architecture should be adopted along with an approach to deliver features constantly. 
+
+High level design
+
+- Social login
+- Microservices to accomodate organic growth in a distributed fashion
+- Responsive / Cross platform front end to cope with desktop, tablets and smartphones 
+- Continuous Delivery to promote faster releases in short spans of time
+- Robust infrastructure with AWS
+
+Technology Stack
+
+- Programming language: ES6 (through TypeScript)
+- Frameworks client: Angular 4, Gulp, Jasmine
+- Frameworks server: NodeJs with Pm2 and Seneca, Express
+- UI: Html5 (video, local storage and semantics), Angular UI
+- Native app: Cordova 
+- Storage: MongoDB
+- APIs: OpenId for SSO
+- Continuous Delivery with AWS