thelostone-mc/stoker

Basically your stock broker

stoker

Basically your stock broker

Server & Client

• Express
• React
• MVC approach

Needed tools

• node
• npm
• gulp
• yarn
• mongo (enable oplog)
• Hbase / Cassandra (Yet to be added)

Setup

• Ensure mongo replSet is up (mongod --replSet rs01 )
• Run express server ./stoker using gulp. Server runs ar port 3001
• Navigate to ./stoker/stoker-client and run yarn start

Contributing

The commit message should describe what changed and why.

The first line should:

• contain a short description of the change
• be 50 characters or less
• be entirely in lowercase with the exception of proper nouns, acronyms, and the words that refer to code, like function/variable names
• be prefixed with the name of the changed subsystem and start with an imperative verb. Check the output of git log --oneline files/you/changed to find out what subsystems your changes touch.
• Keep the second line blank.
• Wrap all other lines at 72 columns.
• If your patch fixes an open issue, you can add a reference to it at the end of the log. Use the Fixes: prefix and the full issue URL. For other references use Refs:

Sample Commit

subsystem: explain the commit in one line

Body of commit message is a few lines of text, explaining things
in more detail, possibly giving some background about the issue
being fixed, etc.

The body of the commit message can be several paragraphs, and
please do proper word-wrap and keep columns shorter than about
72 characters or so. That way, `git log` will show things
nicely even when it is indented.

Fixes: https://github.com/thelostone-mc/issues/2
Refs: http://eslint.org/docs/rules/space-in-parens.html

Collaborators

• Shroff Amrith Nayak
• Aditya Anand MC

stoker's Issues

Replace handlebars with react

To enable data refresh via events emitted by socket.io, handlebars isn't suitable!
Hence proposal to replace it with react!

error: Error handling in fetchIV

• Handle error when request fails in fetchIV
• At this point, server crashes when request is null while running on forever causing server to crash

Handling Socket hangup / connection timeout

Handle connection timeouts and socket hang up in crawler
As of now, server crashes if a socket hangup happens during crawling.

Possible solution:

• Retry crawl on the URL after a timeout

Could you look into this @amrith92 ?

socket.io mongo oplog setup

Enable mongo oplog and track that to monitor changes made to the collection stocks and emit an event with the updated dataset to all connected clients via socket.io

HBase / Cassandra Support for stokerCRUD

Being a time series application , a document based DB will not work in the future.
Querying might get complicated with mongo.

Hence a proposal to support a time-series db after discussing with @amrith92 :

• Turn stockCRUD.js into an interface
• Have a mongo implementation of the interface
• Have a time series DB implementation of the needed functions in the interface.

Essentially build an adpater so switching between currently being used db mongo to hbase or cassandra becomes painless.

googleFinanceAPI : new Data Points needed

• Identify endpoints
• Fetch stock price for last 60 days & 120 days
• Calculate standard deviation and update StockLog
• Update schema of stockLog to accommodate newly calculated data points.

react: Feature to sort rows in ascending / descending

• User should be able to click on the table header and the rows should sort themselves based on the header selected ( putsIV, callsIV, stockSymbol, currentPrice)
• Changes to be be made inside stoker-client

react : modularize views in react

Modularize react components to the simplest form rather than having it in a chunk as it is now. Example: table view for showStocks

Add as collaborator

Please add me as a collaborator

Design schema for daily snapshot

• Re-design schema if needed to store daily snapshot.
• Use scheduler to run crawler by invoking fetchDataPoints()