Well I had originally planned to write it in go and rust, with go as the single api interface and rust workers like a blackbox that took the live ticker stream and gave back signals with confidence.
However the development time with rust especially with a lot of multi threaded increased the development time a lot, since I am kinda new to it, then I migrated that module to java...wanted to see the performance gains with the recent gc optimizations in Java 21 and 23
Yeah, that's the rep it has. Fairly solid software at the end, but takes longer to develop, iteration speed is lower (due to long dev and compile time), and the supply chain probably isn't super robust due to not having an extensive stdlib.
Its very experimental rn.
On a very high level it is just a function scheduler. It is very good at handling thousands of tickers and then can schedule and what functions to run when. The functions have defined templates from which they inherit so they can use the cache and send signals.
Then there are os threads who are querying the schedules for tickets and what functions to run.
Why both Go and Java?
Isn't it usually an either/or thing with those two, as the Java is the "old" enterprise play and Go is the newer one?
Well I had originally planned to write it in go and rust, with go as the single api interface and rust workers like a blackbox that took the live ticker stream and gave back signals with confidence.
However the development time with rust especially with a lot of multi threaded increased the development time a lot, since I am kinda new to it, then I migrated that module to java...wanted to see the performance gains with the recent gc optimizations in Java 21 and 23
> However the development time with rust
Yeah, that's the rep it has. Fairly solid software at the end, but takes longer to develop, iteration speed is lower (due to long dev and compile time), and the supply chain probably isn't super robust due to not having an extensive stdlib.
So, is Tyche a performance test tools for trading platformers like kind of JMeter?
Its very experimental rn. On a very high level it is just a function scheduler. It is very good at handling thousands of tickers and then can schedule and what functions to run when. The functions have defined templates from which they inherit so they can use the cache and send signals. Then there are os threads who are querying the schedules for tickets and what functions to run.