Why Every API Is Becoming an AI API
APIs were originally built to connect software. Today, they’re increasingly being designed to communicate with something entirely different—AI agents capable of reasoning, planning, and making decisions.
APIs were originally built to connect software. Today, they’re increasingly being designed to communicate with something entirely different—AI agents capable of reasoning, planning, and making decisions.
For years, software development rewarded the ability to write code quickly. AI is changing that equation – but not in the way many people think.
Securing AI Agents in Enterprise Systems
Artificial Intelligence has evolved remarkably over the last few years. What started as chatbots capable of answering questions has rapidly transformed into autonomous agents capable of interacting with real-world business systems.
For years, relational databases and document databases were presented as competing technologies. Looking back, that debate feels surprisingly outdated. The real winner wasn’t SQL or JSON – it was the combination of both.
Read more Why Every Modern Database Is Becoming a JSON Database
When Microsoft first introduced Copilot features into Microsoft Dynamics 365 Business Central, many developers saw it as a productivity enhancement layer — smarter suggestions, assisted text generation, improved user experience.
MongoDB Atlas integrates RAG seamlessly through its Vector Search feature, storing documents with embeddings, metadata, and application data in a single collection for hybrid semantic and keyword queries. This simplifies ingestion (chunking data, generating embeddings) and retrieval, feeding relevant context directly to LLMs without separate storage layers.
For years the default was simple: one big application where the backend (PHP, Java, .NET, Ruby…) generated full HTML pages on the server and sent them to the browser. It was fast to build, easy to deploy, and worked perfectly… until it stopped working.
If you are building a production extension (not a test extension) and you only need the core System Application (which is almost always the case), you add just this dependency:
In Business Central, tests are just special codeunits with some extra attributes.
Upgrading Microsoft Dynamics NAV to Business Central is rarely just a technical operation.
The longer a company postponed the upgrade, the more technical debt accumulated in the codebase. What often looks like a “successful upgrade” is, in reality, only the beginning of a much harder journey.
Read more Refactoring Legacy C/AL Code After Conversion to AL
If you’re a .NET developer in 2025, you already know that Dependency Injection (DI) is not an optional “nice-to-have” — it’s the default and recommended way of building maintainable, testable, and loosely-coupled applications. Microsoft made DI a first-class citizen starting with .NET Core, and with every new version (especially .NET 8 and .NET 9) the built-in container gets more powerful.
Before the release of Business Central 2023 Wave 2 (version 23.0), which became generally available on October 2, 2023. The AL development world faced a fundamental challenge: naming conflicts. Imagine two independent software vendors creating brilliant extensions for Business Central.
Interfaces were introduced to Microsoft Dynamics 365 Business Central in version 2020 Release Wave 1 (BC 16). Their arrival marked a significant step toward improving extensibility, modular design, and decoupled architecture within AL development. Before interfaces existed, implementing flexible, interchangeable logic was difficult.