You are welcomed by the TKEY development team, we have not been in touch for a long time, and the publications were prepared by the editorial staff based on the submitted abstracts.
We did not make any direct appeals, except for the publication of “riddles” in 2018. Today we have a direct dialogue with you, dear users. We inform you: — “We have achieved our goal, which we have been implementing for several years.”
It is time to understand all the issues in detail, to understand the true meaning and idea of the TKEY project. Plunge into the obvious advantages and advantages of such approaches, and realize the full power of the new ecosystem. And, most importantly, to understand why there was such a “protracted” start, when, it would seem, others launch something similar in a few months.
What is an ecosystem?
For a better understanding and disclosure of imaginative thinking, let’s start with the origins. The term “ecosystem” comes from biology. An ecosystem is a functional unity of living organisms and their environment. It is already possible to understand that this is a single living organism, in which millions of processes are carried out, and each component complements the other. Now we will translate these principles into the field of information technology.
An IT ecosystem is a set of technologies and services developed by one company, as well as services and services of other companies, which are inextricably linked into a single network by specific and technological processes.
Large IT companies and professional developers are well aware that creating an ecosystem is a difficult task. First, you need to build a competent architecture that will scale easily. Secondly, it is necessary to create a bi-directional integration system for a new generation.
Long play or fast launch
Today, literally everyone talks about “scaling,” but not every company, and even more so, not every project is ready for this process. Let’s explain why.
Deviation from the architecture during application development or omission of nuances during the design phase. Yes, this is a common problem that is present in the market. The team set a time limit for the development and launch of the application (deadline). Implementation begins, then during testing, a “bugs” is discovered, and the developer has a choice: to have time to release the application, strictly observing the deadline, or to rewrite part of the project.
More often, the choice is made in favor of the first one: to have time to release the application according to the deadline. With this approach, edits made that deliberately ignore the initial architecture. Simply, “patches” are made to meet the deadlines.
What do you think is it possible to scale such a product in the future? We answer — no, it is impossible.
Imagine: you are making tailoring of business suits. During the manufacture of one of them, you had a problem with the cut, however, you are a “jack of all trades” and decide to make patches and hide them with the inner cut of the suit-jacket. “Brilliant!” — you say, naively thinking that such changes will not be noticeable after several months of operation.
It is clear that this is a conditional example, but it perfectly captures the essence. The competitor wins at the start when he hurries up and launches a non-scalable system, and the user, like a jack of all trades, naively believes that such a system has a huge-future.
First, with such a “short-sighted” approach, the competitor will run into the point of scaling, it will be impossible for technical reasons. Second, to scale, a competitor will take years (4–6 years) to create a high-quality ecosystem. Thirdly, the creations of an ecosystem is a very expensive process, both in terms of finances and time.
It is easiest to imagine a similar situation in the example of “racing” competitions. There is car X, and car A. X is a competitor, A is your project (scalable).
Car X (competitor) in 4 seconds gains a speed of more than 100 km / h, and overtakes you at the start, but after 600 meters, your car A overtakes the competitor and significantly breaks away from the competitor.
Such an example perfectly reflects the whole truth of the “long game” or “long-distance race” approach. When you have a solid “foundation” — you will win, always lead.
We emphasize that the “basis” is the source, the main thing on which something is built, which are the essence of something. In construction, the “main” is understood as an array of soils that take the load from buildings and structures.
When creating TKEY, the founders initially understood that a reliable foundation was required. This principle is important to use in everything, it builds a powerful, reliable system that can scale to any task.
Moving away from the imagery that were given for understanding, let’s move on to the technical part. As mentioned above, creating an ecosystem requires the implementation of bidirectional integration of technologies.
Companies that become part of this system are connected to the ecosystem. Companies, projects, in turn, use different technologies and approaches; the goal of the ecosystem is to combine these technologies and provide the end user with effective tools, leaving the most complex processes behind the scenes.
Bidirectional integration is dynamic and takes place in real time, and this process can take place with one or more partners, or with thousands of companies. In addition, a huge number of users interact with the ecosystem at the same time, which also increases the load on the system and makes it difficult to build a competent architecture.
And to support all these processes, it is necessary to introduce best practices, create a new generation of integration system. During the creation of the architecture-form the necessary integration standards, take into account the various types of data transmitted, rationalize, standardize, pay attention to application programming, etc.
It is one thing when we are working in a small project, passing data types that are easily supported by the system, then classical APIs are enough for such an implementation. Another thing is when interaction with the ecosystem is required, and for integration with it to take days, at most weeks, and not months or years, it requires the creation of progressive solutions.
Moreover, it is one thing to quickly integrate and transfer data, and another to be able to quickly process this data, and easily scale at any time, and do it without large investments. And in general, do it, because if you do not have such an opportunity, you just stay in one place, your race has come to an end.
Advantages of launching an ecosystem
Easy integration makes it easy for partners to interact with the ecosystem, which creates a large market for services, services that are added to it through rapid integration. Thus, a huge list of functions is covered, from instant transfers, payment solutions, trading functions, and industrial tasks. Millions of technical operations, thousands of data, all processed in seconds.
Connection to the system occurs for several reasons — the speed of implementation of a service or service for a partner is a matter of days, and to save money on long-term develops software.
The partner uses the TkeyNet system as a backend, implementing on its side the competitive functions it needs. It is worth noting that by connecting to the ecosystem, the partners complement each other. Everything connects to the system, and there is no need to carry out long iterations, negotiations, or allocate time to create code when everything is already done for you.
Thus, thanks to the ecosystem, its functionality, and dynamic, partners can connect, integrate their technologies even in real-time, and add new features as needed, which will immediately become available to the end-user. The approach is aimed at creating internal information systems.
The business uses the external capabilities of the ecosystem, thereby improving its internal processes for customer service.
The ecosystem is created for various sectors of the economy. If you look at it from the point of view of the user, then unlimited possibilities open up for him. Using TKEY products, there is a continuous integration of partner functions.
As mentioned in previous materials, for example, when you connect any asset to the system, it becomes available in all the company’s products, regardless of whether it is “TKEY Online” or “TkeyPay.” The same goes for any investment products. Given the implementation, there is no need to create your backend, allocate a lot of time for development, it is enough to implement an interface or an additional tab for a function, which significantly speeds up the addition of new functions.
Besides, any connected function to TkeyNet becomes available in all applications. For example, a partner created an application based on an ecosystem, and another partner connected investment services, therefore, partner A has the opportunity to include Partner B’s services in the application, and do it quickly; in turn, the user has access to all these functions.
If using the Core 1.0 intermediate system this was not possible, and it was not a means of scaling now scaling the system is an easy task, not to mention the release of new applications, and any other services.
In particular, the material is more of a method to convey the basic meanings. Having spent time developing the ecosystem now, we are leading after its launch and are always competitive.
Documentation, information about the system and its functions, solutions for business, financial institutions — will be published and supplemented on the ecosystem website after the launch of TKEY Online.
At the time of the creation of the system, its development, we still had nothing to share with you, dear users. Yes, there was the release of the intermediate link Core 1.0, then the listing and the subsequent transition to the ecosystem were planned. But, everything has accelerated, and the transition to the ecosystem will take place now, and as you understand, we have something to share with you.
Firstly, the application “TKEY Online,” in which trading will begin, a universal, secure product that uses best practices. Secondly, documentation, SDKs, new generation APIs are being prepared for developers. Thirdly, industry-specific ones are prepared for companies and financial institutions’ solutions. And one more thing.
And in order not to be unfounded, after the release of “TKEY Online” we will begin to update the “dusty” repositories — there is something to surprise, there is something to capture in history.
On the coming Wednesday, we will publish a short presentation about the “TKEY ecosystem.” On Friday or Saturday — we will publish material about TKEY Online. Pay particular attention: “The testing period is coming to an end. Time to shop for champagne soon. Our way out, gentlemen!”
Best regards, TKEY team! Thank you for your patience and faith in our just cause.