Communication architectures capable of ensuring service continuity in complex operational environments

Both 4G and 5G cellular networks have become enabling technologies for UAV operations. They complement traditional radio links by providing broad geographical availability, mobility support, and the ability to transport telemetry and sensor data. However, as these networks expand in coverage and complexity, ensuring communications continuity becomes an increasingly relevant challenge.

In Beyond Visual Line of Sight (BVLOS) missions, the aircraft operates beyond the pilot's visual range. In these scenarios, UAVs may fly over large areas with limited or no network coverage. The degradation or loss of supervision and data transmission links therefore represents an operational risk that must be mitigated through resilient communications architectures.

Buscando commits malos con el Inspector Gadget

Hay una situación que todo desarrollador acaba viviendo al menos una vez. Te vas un viernes a casa contento con el código funcionando, pero al día siguiente, o tres días después, o una semana más tarde, abres el proyecto y algo ya no va. Y lo peor es que no tienes ni idea de cuándo se rompió.

Lo primero que hace uno es revisar los últimos cambios. Ves que en los últimos 10 commits no se ha tocado nada relacionado con lo que falla (genial). Tendré que mirar más commits diría uno. Pero si el repo involucra a varios compañeros, el historial de commits puede ser bastante extenso. Además, un bug que encuentras hoy no tiene por qué haberse introducido hace poco, igual lleva dos meses en el repositorio.

Git bisect y el Inspector Gadget (un grande)

Para eso existe ✨git bisect ✨.

Let's get into Microservices (together)

Why would anyone define microservices as an architecture choice?

If you're already familiar to microservices, then the answer to the question above might seem quite obvious. But if you aren't, like me, then you might learn some new concept today.

So, I've recently got his book titled "Building Microservices: Designing Fine-Grained Systems" by Sam Newman and I'm going to write some content as I read, and understand, it :).

Microservices are technology agnostic; they are independently deployable; they embrace the concept of information hidding.

Here is a statement I really like and find extremely important within the confines of... software?, system? development. Whatever.

“Information that is hidden from external parties can be changed freely as long as the networked interfaces the microservice exposes don't change in a backward-incompatible fashion.”

Sam Newman

That makes the whole system modular and reliable. 

But what kind of system could it be? Are we talking about a standalone software consisting of various microservices? Perhaps, a bigger picture of a system consisting of a few softwares, each of them working over microservices at the same time? 

Well, let's get through this by describing a few illustrative examples!