Waliot SaaS

Software architecture

When launching SMT on your own infrastructure, you should consider the architecture of the selected software. Most systems are represented by a classic three-tier monolith (client application, server and database). The main advantage of this architecture is ease of administration. But among the disadvantages, we can highlight the impossibility of horizontal scaling when the load on the system increases and a single point of failure in service, since if the only server with monolithic software is unavailable, nothing will work.

Load testing

When choosing a CMT for implementation in the company’s business processes, it is necessary to conduct a pilot project with a launch in an environment as close to production as possible. Including with a server that meets the requirements and the target number of online objects. It is not correct to test the CMT on 100 monitoring objects if you plan to use it for several thousand. Also, do not forget about the size of the database; at least several months of telemetry with real data from the navigation equipment (NE) of all vehicles (TV) should be loaded into the CMT.

Most systems specify minimum server requirements depending on the number of objects to be monitored. But these requirements are specified for “typical” loads, which often do not take into account possible API integrations with related systems, routine tasks for automatically sending emails and messages, and other computing processes. For example, Wialon’s typical load is considered to be receiving data from each NO no more than 170 messages per hour and a server state when all users only monitor objects on the map and do not generate any reports or other complex computing tasks.

Migration

Often, the main criteria for choosing a CMT are its cost and “similarity” to the previously used system. Saving money on acquisition and time on employee training is obvious. But do not forget about the complexity of data migration from one system to another, since a similar user interface will not help in any way when transferring information about thousands of cars, trackers, configured equipment and the rest from one system to another. Do not forget about possible problems with the equipment. Not all CMT support all protocols of navigation devices. Some equipment has proprietary protocols that cannot be implemented within third-party systems. In this case, common protocols are used, which may be limited to a basic set of parameters.

Software Components

Modern software systems are not developed from scratch. Most of them use ready-made components, such as DBMS, message brokers, web servers, etc. It is important that when purchasing a license for commercial software, there are no violations in the licenses of the components used, and there are no components with proprietary code.

The optimal solution is a full launch of the considered SMT in parallel with the already operating one, migration of all data from one system to another and setting up retransmission of incoming telemetry in real time. In this case, all problems and difficulties in implementing a specific software solution will be detected even at the stage of selecting the SMT. And the volume of data and the load on the system will allow us to evaluate its real performance and potential for implementation and integration with related systems of the Customer.