report: add initial roadmap
This commit is contained in:
parent
1e56974953
commit
0d0c2bebe6
20
report.md
20
report.md
|
@ -93,6 +93,26 @@ of them:
|
||||||
|
|
||||||
# Internship roadmap
|
# Internship roadmap
|
||||||
|
|
||||||
|
The first month was dedicated to familiarizing myself with the vocabulary at
|
||||||
|
IMC, understanding the context surrounding the team I am working in, and
|
||||||
|
learning about the different services that are currently being used in their
|
||||||
|
infrastructure. I had to write a first proof of concept to investigate what, if
|
||||||
|
any, dependencies would be needed to execute the gateway as a stand-alone system
|
||||||
|
for the benchmark. This has allowed me to get acquainted with their development
|
||||||
|
process.
|
||||||
|
|
||||||
|
After writing that proof of concept, we were now certain that the benchmark was
|
||||||
|
a feasible project, with very few actual dependencies to be run: the only one
|
||||||
|
that we needed to be concerned with it called the RDS server. The RDS server
|
||||||
|
is responsible for holding the information about all trade-able instruments at
|
||||||
|
an exchange. The gateway connects to it to receive a snapshot of the state of
|
||||||
|
those instruments, for example the mapping from IMC IDs to the ones used by the
|
||||||
|
exchange. I wrote a small module that could be used as a fake RDS server by the
|
||||||
|
benchmark framework to provide its inputs to the gateway being instrumented.
|
||||||
|
|
||||||
|
I am now currently beginning to write the benchmark framework, using what
|
||||||
|
I wrote and learned during the previous month.
|
||||||
|
|
||||||
# Engineering practices
|
# Engineering practices
|
||||||
|
|
||||||
# Illustrated analysis of acquired skills
|
# Illustrated analysis of acquired skills
|
||||||
|
|
Loading…
Reference in a new issue