By this Integration service it is possible to make the complete adaptation of the proprietary system that the customer has, with minimal changes and for multiple database systems or customer environments in their facilities, as part of the management of their internal processes.
Its ITF features are:
The integration component is fully configurable through XML, and allows you to model the transformations of the different entities between XOne and the client’s solution.
It runs as a Windows or Linux service, totally unassisted, monitoring the environments, according to the established periodicity, guaranteeing the equivalence of both systems with the desired frequency.
The information sending generated by the terminals can be practically in real time, once that data has been received in the mobility server. Integration frequency: Client-XOne or XOne-Client.
In this way we can get information from different sources and integrate it into the mobility app itself.
The opposite process, sending to different systems, is also possible.
With an error report integrated in the O.S. in which it is installed, it allows to give a complete follow-up to each executed step, as well as making decisions quickly and accurately .
In addition, it is also possible to manage that this log information is stored in the DB itself.
The microservice infrastructure is a set of tools and runtime services that facilitates the design, development, testing, packaging, implementation, operation, monitoring and administration of microservices and microservice apps, with the guarantee that services can be carried out continuously and without interruptions.
Each microservice can be designed, developed and implemented independently of other microservices, which provides agility since it is easier to carry out new versions of microservices frequently.
Each microservice is relatively small, easy to administer and develop.
The IDE can load smaller projects with more speed, increasing the productivity of the developers.
There are two key aspects of microservices.
One of them, is the packaging and deployment of apps to be portable through cloud providers.
Another is to distribute the app in weakly coupled, single-function components that use REST for communication.
If a problem occurs in a service, initially only that service is affected and the other services can continue to control the requests.
In addition, when a problem is solved in a microservice, the involved microservice can be implemented without impacting the rest of the app.
As you can start to develop the services independently and run them in parallel, you can use the cutting-edge technologies and platforms.
