What architecture for your IOT platform?

The aim of this article is to review the 2 possible architectural choices when talking about an IOT platform, namely “ monolithic ” or “ microservices ” and allow you to make the right choice according to your needs.

"Monolithic" architecture

This simpler and easier to implement architecture is definitely the right solution for all customers wishing to start and make a prototype to validate a use case.

In monolithic mode, all platform components are launched in a single instance and share the same OS resources. The obvious advantage of monolithic architecture is the minimization of the memory required to run the platform.

This architecture will then reach its limits when the service must go into production and meet the classic constraints of stability, quality of service, growth and resistance to load peaks, etc.

The “microservices” architecture

Since Connect V1.1, TICATAG platform supports microservices deployment mode.

This architecture is therefore composed of functional microservices distributed over multiple duplicated instances which communicate through a Kafka software bus.

Thus each hardware problem (instance restart), or software, will only impact a minimal fraction of the platform and will ensure continuity of service to the end customer.

This architecture is the only way to ensure a 99% availability rate, if this objective is requested by the service or the end customer.

Summary of differences: monolithic versus microservices

Category	Monolithic architecture	Microservices Architecture
Design	Single code base with multiple interdependent functions.	Independent software components with self-contained functionality that communicate with each other using APIs.
Development	Requires less planning up front, but becomes increasingly complex to understand and maintain.	Requires more planning and infrastructure up front, but becomes easier to manage and maintain over time.
Deployment	Complete application deployed as a single entity.	Each microservice is an independent software entity that requires individual containerized deployment.
Debugging	Track code execution in the same environment.	Requires advanced debugging tools to trace data exchange between multiple microservices.
Modification	Small changes pose greater risks because they impact the entire code base.	You can change individual microservices without affecting the entire application.
Scalability	You need to scale the entire application, even if only certain functional areas are experiencing increased demand.	You can scale individual microservices as needed, saving overall scaling costs.
Investment	Low initial investment at the cost of increased maintenance and upkeep efforts.	Investment in additional time and costs to set up the required infrastructure and build team skills. In return, savings in costs, maintenance and long-term adaptability.

Conclusion – Why choose Connect V2?

Starting with Connect V2, TICATAG is able to offer all its customers not only the possibility of using the white label solution but also, for those who wish, the deployment of the platform on their own instances in the AWS datacenter of their choice.

We offer you a turnkey platform , with an optimum architecture to manage large volumes of data, without investment and available immediately to start immediately .

Do not hesitate to contact our teams if you wish to discuss this and set up a demonstrator....