TagoDB handle large amounts of data in excess of terabytes with a very fast access rates, supporting data from multiple hybrid sources, designed to provide availability and high scalability at the same time without compromising system performance, software and hardware alike, ensures a database that can be counted on for high volume of mission-critical real-time data, with a very low latency regional outages - perfect to deal with massive data feeds from multiple exchanges across the globe, at the same time, in real-time. TagoDB contains: Object oriented, Hierarchical, Relational & Flat file based database capabilities all together, and capable of running on Linux, Windows, and some UNIX based workstations. TagoDB is using the Tago Real-Time Archive® technology.
An algorithm based technology that provides a solution for scenario-calculations that require true random data. A more effective random calculation solution to replace the pseudo-randomness computers usually generate.
A technology that shows the state of the main interest between potential liquidity providers in relation to an open position in real time, including a unique visual display that can perform complex and effective calculations regarding the open position management, according to the risk manager and other parts of the software which signals an event of conclusion or action.
A technology to simulate an exchange behavior by referring directly to an existing market situation (not an open position), provides the system with clear instructions regarding the direction of the market at any given moment, AI processes included.
The general encryption system that protects all components of the software in real time, including the real-time data that flows between the various programs in the entire TagoTrader software suite, using cryptographic algorithms, without slowing down the system, providing a very high level of security, available by in-house internal encryption not known to any hacker. In addition to that, the whole system is highly secured, backed by Tago's Cyber Security model where the system is always offline to the outside world, running from a local server machine, in an OGRTI mode (only getting real-time information) built-in the receiving pipeline of the TagoTrader Framework. There is no threat and there is no hacker who could break into such a system simply because even at runtime it is never connected to anywhere by definition.
TagoRT is TagoTrader's proprietary codding syntax that works on the TagoTrader Framework only, where the TagoTrader Softwares communicate with each other on the internal network, meaning that instructions can be given and performed across the entire computer network, all in accordance with predetermined instructions set into the entire system using the TagoRT codding syntax. The TagoRT code syntax is applied on all TagoTrader softwares, and is also the language used to manipulate features, customization options and editing or adding new algorithms in the AI components of the entire softwares suite. Using TagoRT codding commands, the system accepts and implements Big Data volume changes in real time (employing on-the-fly compilation technics) to make progress and provide conclusions for the next Nano second (internally), or for tomorrow (tomorrow in a certain sense) gaining BI (Business Intelligence) for the next execution request received mostly by Tago RT Trader and Tago Risk Manager softwares.
One-Step methodology was developed for the TagoTrader framework mechanism which basically says "one step only" or "one step than explain" or "100% true or get help", this means that the entire system (framework) allows all softwares to come back with 2 kind of answers: 1 - that is 100% true, OR 2 - the whole system switched to RDM (Receiving Data Mode) which is like "receiving data by force", the system is now evolving (learning) and it will output the new algorithm that is missing or need adjustment by itself - this is where the fundamental premise of the entire system is reflected the most (that it cannot draw conclusions without introducing some capital to the market). The longest time to receive a final answer throughout the entire life of the system was 14 hours and twenty-two minutes, which eventually opened a huge liquidity window of over X10 on one electronically traded financial instrument.
Tago RDN (Receiving Data Mode) is the main situation in which the system goes automatically into a research mode. When all components outputs stops call for an RDM mode in an internal research project, is in simple words, where the AI RDM's events in the system are only signaling for Enlargement-Tasks (actions to evolve and find new conclusions), rather than answering unresolved Risk-Manager questions for example. It's basically generates the algorithm and say when it relies on it (temporary certificate) by automated research processes, once the algorithm has received a temporary certificate, it is automatically injected into all necessary system components that are using that algorithm - the old version of the algorithm is already saved by the database of the TagoCR software. Part of the system's intelligence is based on Dependent-Data or Independent-Data, according to definitions and goals set by TagoRT syntax commands, a good example to explain this would be - like when a child asks, is 1 hour a lot of time? How much is 1 hour? The system is giving the answer a child should receive = that it depends, it may be a lot, and maybe 1 hour would be considered a bit. This is applied when the system is asking a question of 2 channels, "One-Step", and the answer will be one of two, either 100% true or false (calling for RDM mode). So, does the current position risk is 100% a true answer? if the answer by any of the system's components is: "it depends on: 1,2,3,X,Y,Z,etc." than RDM mode is activated and so on.
Tago_NENI refers to "new_Exchange_new_Instrument" and used for information that has entered the system and has not yet pass several days and algorithmic calculation rounds in the required AI components of the entire frameworks and softwares, so that it will evolve and learn enough to perform execution with real capital. Tago_NENI in TagoRT syntax includes on-the-fly implementation without stopping any real time process in the system. When all components outputs stops calling the RDM mode for a specific NENI property, the NENI mode is deactivated automatically, for the reason that events are no longer calling an unresolved issue that needs to go into AI processes, NENI can't accept enlargement algorithmic jobs, only evolving jobs.