|| श्री || Scanner App Diagram Long time back I have a plan to execute the scanner for finding the right stock utilizing OHLC information. I couldn't make sense of how I should process the information on various stocks as numerous stocks should sweep and discover a chance to exchange. I attempted various methodologies however somehow it couldn't function. While executing application I was confronting issue to telling if any open door is found. On the off chance that any open door discovered, at that point, my scanner simply tells UI and proceeds with the pending checking. Past I couldn't make it approximately coupled things yet I just went over where they utilizing arbiter design which helps me to break tight coupling. TradingDB - SQL database to store OHLC information. Data Access Layer - This layer is going to operate on DB using Dapper Library. As we have multiple entities like OHLC, Instruments, Watcher List, etc. Data Services - Multip
|| श्री || Ticks to usable Time Frame Tick data is raw data that we need to process into the usable time frame. As I am using Zerodha ticker service it gives me data every tick. If we need to find an opportunity for trading, required to process the data to make it usable. Here I am saving data into mssql data base to store tick data. Below is my table structure. You can use below script to use table. I am storing only current day data for Nifty50 stock and Nifty50Index. In my table End of the day will move this data into my historical table which store 1 min data. and truncate table. CREATE TABLE [dbo].[TickerData]( [TimeStamp] [datetime] NULL, [Open] [decimal](9, 2) NULL, [High] [decimal](9, 2) NULL, [Low] [decimal](9, 2) NULL, [Close] [decimal](9, 2) NULL, [Volume] [bigint] NULL, [InstrumentID] [bigint] NULL, [recordid] [bigint] IDENTITY(1,1) NOT NULL, CONSTRAINT [PK_TickerData] PRIMARY KEY CLUSTERED ( [reco