Systems | Development | Analytics | API | Testing

It's not even 9 AM, and the day's already started. A customer can't reset their password. The product team just found a bug in the app. A partner bank needs data synced ASAP. Oh, and the CEO wants to know when the mobile app can do instant loans. Sounds about right? Yeah, for banking leaders, this is just another Tuesday. Customers want everything to be easy and digital. Stakeholders want things done well, safely, and by the book. And nobody has time for old-school stuff.

Choosing the right IoT protocol for edge microservices can save energy, reduce latency, and improve efficiency. Here's a quick guide: MQTT: Lightweight and energy-efficient, ideal for resource-constrained devices. AMQP: Reliable and secure, great for mission-critical applications but resource-intensive. CoAP: Best for low-power, low-bandwidth devices with minimal energy needs. HTTP/REST: Widely compatible but consumes more energy and bandwidth.

In this tutorial, we will build a Flask app with Docker, create a background worker with Celery, and use RabbitMQ as the message broker between the two services. This (relatively) simple example will be used to demonstrate how Docker makes it easier to run multiple services and share configuration details between developers. In the last section, we will also build and optimize our app for deployment to Render, so we can avoid some of the common gotchas it is easy to fall victim to along the way!

Technical debt is a sneaky hang-up that organizations and teams often ignore until it becomes unmanageable. It creeps in slowly, undermines your team’s productivity, and builds up until your product is hard to maintain and scale. Software systems and development cycles are increasingly being driven and supported by AI, continuous delivery, and cloud-native environments, making it critical to adopt a clear strategy for identifying and reducing technical debt.

At NodeSource, we live and breathe Node.js and are passionate about performance and security. We understand that for developers and platform teams, managing the security and compliance of dependencies is a mission-critical task. However, the tools designed to help can sometimes become part of the problem. Today, we’re proud to introduce NodeSource Certified Modules v3 (NCM v3): a complete rearchitecture of our module scanning and observability engine.

If you have spent any time working with Elixir in a production setting — or even just building a side project — you've likely encountered a stack trace. Stack traces can appear intimidating at the outset, especially since Elixir's error messages are often more detailed than those in other languages. However, they are a powerful tool for understanding what went wrong in your code. Early in my Elixir journey, I found stack traces to be a bit overwhelming.

Software development isn’t what it used to be, and that’s a good thing. What was once a linear code-and-release process has evolved into a dynamic, AI‑powered, security-first ecosystem spanning cloud, edge, and compliance workflows. In 2024, the global software development market reached $403.6 billion and is expected to climb further, driven by AI, cloud-native architectures, and embedded automation.

Our Advanced CI team is always trying to push what we have further, which often means we have to support APIs and code that are not yet fully stable. On the other hand, we are bound to support projects that are using deprecated code to a certain extent. This is particularly true for build systems that are rapidly changing to support the needs of application developers, such as Gradle.

Large Language Models (LLMs) like ChatGPT and Claude have revolutionized how we think about business automation and conversational interfaces. So it’s no surprise that many organizations are considering building their own LLM-powered chatbot. But here’s the truth: creating a secure, scalable, and intelligent chatbot from scratch is harder than it looks.