How does the email validation work internally?
590 karma · joined May 20, 2009
http://artursoler.com
How does the email validation work internally?
I use Cassandra with just 1 node for the moment.
It's kind of that, although the client doesn't talk to the exchange directly, it only talks to the backend. The backend consumes events from the different exchanges, transforms it to a common format, stores it and serves it to the client (in brief terms).
I may in the future, but if I do it will not be charging for basic functions or inserting obstrusive advertising.
Hosting is cheap these days. I'm using a Hetzner machine at about 30€/month which is handling load quite well.
There are different markets available, indicated by the white dropdown at the top.
Currently supporting GDAX and Gemini, but many more coming soon!
I want to make clear that the user can write in there in order to filter entries.
GDAX does the fade-in and fade-out animation on the order book, which helps give it dynamism. It may have a bit more render frequency, as OhMyCoin orderbook is rendered every 200ms. I considered that fast enough, given it's nature nobody is going to read and process the data faster than that, and it consumes much less CPU than GDAX dashboard.
Regarding the orderbook positioning, everyone has their preferences. It's on the plans to make all panels configurable so that they can be moved around, but it's not going to happend on the short term, sorry - many other things on the TODO list!
But I first needed a foundation that, is true, does not differentiate it too much yet from alternatives.
I haven't spent too much time on it yet, but I will.
The backend is built with Scala too, mostly using Akka Streams for the data handling. As a database it uses Cassandra.
edited - word choice
Perhaps I should look into some way of making that more clear.
This being a new tool the feature set is currently quite limited, and I'm exploring differentiation possibilities in there too.