Thoughts on technology, web development and software engineering.
Discover how to design a Flow Service capable of running complex automations on an omnichannel platform without blocking queues, while maintaining high availability, scalability, and low coupling. In this article we explore a state-based architecture, RabbitMQ, independent modules, and asynchronous execution.
After identifying the conversation and the automation flow associated with the channel, the Flow Service takes over control of the entire automation execution.
The Validation Service receives incoming events from various channels and ensures they are valid before forwarding them to the other microservices (support, chatbot, CRM, analytics, etc.).
Circuit is Nexo's first module: it lets companies create and manage virtual running championships for their customers, with automatic result tracking via Strava webhooks.
A case study comparing availability and latency of CPU-bound and memory-bound microservices, with and without retries, circuit breakers, load balancing, and scaling.
When we think about an AI chat for a system, we usually picture a giant model answering any question. In practice, the goal is often much more specific.
One of the great advantages of Node.js is its ability to handle thousands of simultaneous connections using an event-based model and asynchronous operations.
Distributed systems inevitably face failures. Unavailability of external services, network latency, infrastructure overload, and temporary errors are all part of the reality of any production environment.
Building an omnichannel messaging platform goes far beyond simply sending and receiving messages.
WebChat has become one of the main tools for interaction between companies and customers in the digital environment.