Topic: 🔥🌟🔥【ANN】【ICO】【PRE-SALE】 🚀 QURREX 🚀| THE FIRST HYBRID CRYPTO EXCHANGE🔥🌟🔥 - page 69. (Read 28956 times)

How can i order a pre-sale and how much does it cost?

Ok, we will think about this question.

If the dev team do more interview session, with Q&A sessions giving the bounty team more resources to post, it will go a long way to improve PR activities.

At the middleware level Qurrex is delivered as a package of microservices. Each microservice is integrated in the systems operating by Redis MQ (text or GZipped) or UDP channel. Messages received through one of these channels are processed in parallel threads

sure

It would be succeed only if we will be able attract more people as an investors and bounty member. We should spread info about QURREX between our friends.

Is Qurrex legal in all countries ?

Yeah bro, i've already advised it to my friend and he wants to order a pre-sale. I'll think about it too

Nice project. I hope you will do your best! I'll advice Qurrex to my friends, they are interested in cryptocurrency

Ok, got it! Thank you.

Each Qurrex gateway to the core of CEX is a multi-threaded service, and each thread has its message loop, which can process many  client connections. There are two types of gateways – optimized for good scalability for supporting vast number of connections and optimized for low latency for less number of HFT clients. Gateway services can be connected to Matching or Risk Engines using many-to-many relationship using Qurrex Routing Logic components and can reside both at the same or at different compute nodes, providing horizontal scalability.

Vertical scaling. Each middleware microservice can be hosted on a separate server. Each database (presently middleware owns 4 database schemes: configuration, dealing, market data and statistics) can also be hosted on a separate server.

Horizontal scaling. The dealing microservice deals with the highest payload among other microservices. The service processes trading orders and performs basic risk management. The payload grows with the growth in end customers numbers. The dealing microservice can be installed several times on several servers while the payload is being balanced evenly (as a function of trading account identificator). Load balancing function is updated on plugging / unplugging one of the dealing microservices with downtime less than 1 minute.

How can Qurrex server handle requests in batch manner?

How the Qurrex gateway can support vertical/horizontal scalability?

Thanks,your sistem inspires trust

More services of the CEX define their data formats (messages formats) in our in-house YAML-based format. Every message has frame, containing message class unique identifier, sequence number and actual length of message. Each messages set (set of messages belonging to the same logical data stream) we call  a scheme. Scheme can be used both for dynamically unpacking messages from incoming stream and (preferably for low-latency services) generating C++ code for creating and reading messages using statical (for better performance) or dynamical approach: latter approach allows not to recompile client even is case of some changes in the messages scheme, while former ensures virtually no overhead for decoding messages. Variable-length messages, nested messages and lists are supported. We find our approach having some features similar to Google Protobuf. Bindings for Python language are also generated from messages schemes. Data stream (“link”) can expose its scheme to clients, making data stream self-described.
Middleware / presentation layer are widely using DTO structures. These classes are being serialized in JSON format. When DTO is routed through communication channels, Redis MQ or UDP, it may be packed by GZip algorithm - depending on the channel’s settings.

All the Qurrex software layers (exchange, middleware, presentation layer) are unit tested.
Middleware unit tests are conducted in Continuous Integration software (TeamCity). A part of unit tests are written in Behaviour Driven Development pattern (given - then).
We also write tests for Data Access layer. For these tests we automatically creating (and destroying after) test databases with some initial data. We conduct load tests in Apache JMeter.

How do you define the (packet) data format for the transaction in the exchange system?

In a current prototype of Qurrex(CEX), exchange features are implemented in a modular manner and can be tested separately/independently? And for this test, what kind of TDD (test driven development) methodology Qurrex development team exploit?

Please write the messages in the thread bounty  https://bitcointalksearch.org/topic/annbounty-ico-qurrex-the-first-hybrid-crypto-exchange-3185579

#JOIN
Twitter campaign
Twitter url: https://twitter.com/islakevinlester
Telegram url: https://t.me/islakevin

#JOIN

Facebook campaign

Facebook url: https://www.facebook.com/islakevin
Telegram url: https://t.me/islakevin