Everybody uses AI for almost everything these days. If you’ve been paying attention to the backend space recently, you’ve probably heard of RAG (Retrieval-Augmented Generation)…
fullstack thoughts
Carlos Rodrigues Posts
Everybody uses AI for almost everything these days. From helping shaping ideas to the recommendation systems that tells us which movie to watch next, it’s almost omnipresent. But for many of us (myself included), what happens “under the hood” remains a complete mystery, seeming, at times, almost magical.
This post is the first in the AI for Dummies series, where we’ll try to demystify AI, by learning what it is and how it works, starting from simple use cases and concepts and evolving into more complex and real-world scenarios. This post also serves as an introduction to a few key tools, such as Tensorflow and Keras, as well as a brief introduction to important concepts in this domain.
Event-driven systems have well-known advantages and most modern distributed system architectures leverage events to reduce latency, improve scalability, and overall, make everybody’s life a little bit easier.
But what happens when integration with a legacy system (non-event-driven) needs to happen? Are we ready to sacrifice the benefits of event-driven architectures, or will we spend time, effort and money to build and event source based on the legacy system?
Spotify’s backstage is a widely used developer portal framework. When properly configured, it is very powerful and integrates with dozens of other tools that are used daily by developers, managers and devops teams.
One of the first aspects to consider when setting up backstage is the user access and authentication. Although Backstage provides a few out-of-the-box identity provider integrations, Keycloak is not one of them, and the process to configure it can be a bit daunting, especially if one is new to Backstage and how it is structure.
This article aims to provide a step-by-step guide on how to create a Keycloak OiDC client and how to configure Backstage to use it.
Apache Kafka has, over the past few years, become the go-to platform for building scalable, and fault-tolerant data pipelines and event-driven applications. Unlike other messaging…
Tired of Visual Studio prompting for the credentials of your Nuget Sources every time?
This method uses the nuget.exe to add sources and store its credentials.
Hi and welcome to the 4th article on the MQTT series. Today we’ll see how to deal with fragile connections and how consumers can survive…
Hi and welcome to the 3rd article of the MQTT Series. In this article we’ll start looking into more advanced, yet very commonly found scenarios in IoT workloads. We’ll discuss the scalability and availability of consumers and we’ll see different ways to implement a load balanced consumption layer, namely by implementing Worker Pattern / Competing Consumers Pattern with MQTT shared subscriptions.
Hi and welcome back to the MQTT series, where we’ll go from the protocol basics, to real-world implementations of different use cases, using different brokers and clients. In this article we’ll see how to setup secure a Mosquitto MQTT Broker with TLS and Access Control.
In the previous article we’ve covered the protocol basics, saw how it compares to HTTP and why it is so relevant for IoT.
Today we’ll explore one of most used brokers: Eclispe Mosquitto. We’ll discuss the role of a broker in a MQTT-based architecture and while covering some advantages and disadvantages of Mosquitto, which should help you understand if this is the suitable broker for your use case.
MAUI Blazor Hybrid is a great way to leverage web development skills to target multiple platforms, including iOS and Android. As with most recent platforms,…