A Real-Time Cryptocurrency Ticker Dashboard
Today is March 30, 2022, and I hope laziness won't stop me from completing the first edition of this project in mid-2022...
I've just picked up basic front-end skills and I've developed a strong interest in cryptocurrencies. So I want to start with a simple project to get exposure to cryptocurrency and go deeper into front-end skills.
For these reasons, and you also saw my title above, I wanna to create a cryptocurrency ticker dashboad.
I think this a complete software project, so first of all, we should clarify the following points:
- 1.What is the core target?
- 2.The design and feature of the dashboard?
- 3.Program languages and frameworks selection?
- 4.Data source?
- 5.How to deploy?
- 6.How to test?
Here are some screenshots of "Huobi", a global cryptocurrency leader:
Realtime Market Data
I want to create a website and an app just like the screenshots above. My target will have two step:
- 1.Create a real-time cryptocurrency ticker dashboard.
- 2.Base on step 1, build a crypto trading simulator.
In the early project, I will use the design just like "Huobi", maybe in step 2 I have to design something new for my project.
Let's talk about features, I splited the above pics with several red box.
The project will be mainly made up of two pages:
- 1.The index page
- 2.The detail page of a crypto
The index page displays some summary infomation of cryptos:
- 1.Several main cryptos
- 2.More cryptos as a list
The detail page of a crypto display all infos of its market:
- 3.Orderbook & Market Trades
- 4.Other cryptos as a list
- 5.Exchange (Trading Simulator), and this will be built in step 2
Ha... This is my favourite part, maybe coding is the key to the future...
This part will be updated whenever something new used during the project.
For the frontend, I will choose these:
Now the backend, the following are my choice:
Since micro service is easy to use, I will deply my services on k8s, and I will use some SaaS or PaaS service to simplify this part. Besides, the target of this part is to use as less $ as possible.
This part will be updated after which platform to use is decided.
This part is just the opposite of the above two parts, since test is boring and will take a long time to check every possible problem.
In order to make the service stable, this part is also very important, so maybe unit test is necessay during the project. The detail should be considered before testing.