Enterprise Service Bus (ESB)

The XOne Integration Bus, with smart selectivity, connects with the customer’s system and makes it possible to mobilize virtually any system with minimal resources.

This integration service makes it possible to fully adapt the customer’s proprietary system, with minimal changes and for multiple database systems or customer on-premises environments, as part of the management of their internal processes.

Information is sent immediately using push technology.

Its simple XML-based programming integrates with all systems on the market.

See integration types

Adaptability for large deployments

It offers better adaptability and is designed for large deployments.

The integration component is fully configurable through XML and allows you to model the transformations of the different entities between XOne and the customer’s solution.

It runs as a Windows or Linux service, fully unattended, monitoring the environments at the established intervals and ensuring both systems are in sync at the desired frequency.

Real-time information delivery

Information generated by the devices can be sent practically in real time once that data has been received on the mobility server. Integration frequency: customer-XOne or XOne-customer.

Several systems for one app

Several systems can be integrated for the same app. This way we can obtain information from different sources and integrate it into the mobility app itself.

The reverse process, sending to different systems, is also possible.

Tracking and management

With error reporting integrated into the operating system on which it is installed, it allows full tracking of every step executed, as well as fast, accurate decision-making.

In addition, this log information can also be configured to be stored in the database itself.

Manage communication between systems

The features of its ITF are:

• Configurable through XML
• Unattended service
• Configurable frequency
• Middleware
• Data exchange reporting
• Back-end migration without affecting mobility
• Use of time-stamp

Microservices

Microservices are becoming the preferred way to build cloud-native apps.

They are changing not only how organizations launch new apps, but also app architectures.

With a microservices architecture, apps are built from independent components that run each application process as a service. These services communicate through a well-defined interface using lightweight APIs.

Service scaling

As a set of runtime tools and services, they make it easier to design, develop, test, package, deploy, operate, monitor and manage microservices and microservice apps, with the assurance that services can run continuously and without interruption.

Independence

Each microservice can be designed, developed and deployed independently of other microservices, which provides agility, since it is easier to release new versions of microservices frequently.

Speed and productivity

Each microservice is relatively small and easy to manage and develop. The IDE can load smaller projects faster, increasing developer productivity.

Deployment

There are two key aspects of microservices. One is packaging and deploying apps so they are portable across cloud providers. The other is splitting the app into loosely coupled, single-function components that use REST to communicate.

Problem isolation

If a problem occurs in one service, initially only that service is affected and the others can continue serving requests. In addition, when a problem in a microservice is fixed, the affected microservice can be deployed without affecting the rest of the application.

Emerging technologies

Since services can be developed independently and run in parallel, the most modern technologies and platforms can be used.