RAG with ElasticSearch
Elasticsearch isn’t just a search engine anymore – it’s evolved into a complete AI-ready platform. According to Elastic’s documentation, it provides native support for the entire RAG workflow
Elasticsearch isn’t just a search engine anymore – it’s evolved into a complete AI-ready platform. According to Elastic’s documentation, it provides native support for the entire RAG workflow
MariaDB emerged in 2009 as a fork of MySQL to maintain an independent, fully open-source database system. Over the years, it has diverged from MySQL, offering unique storage engines and flexible configuration options, making it suitable for everything from transactional systems to analytical workloads.
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.
This platform changes everything by providing a powerful yet accessible platform that democratizes backend development. Let’s explore what makes Xano a game-changer.
If you want to enter the world of mobile game development quickly, Godot Engine is one of the best tools to start with. It’s completely free, open source, and offers everything you need right out of the box.
In the rapidly evolving world of search, analytics, and observability, OpenSearch has emerged over the last few years as a prominent open-source alternative to Elasticsearch.
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
Microsoft Dynamics 365 Business Central (BC) is a modern ERP solution that has always prioritized flexibility and extensibility. One of the core mechanisms enabling customization is the extensions model, introduced in 2018 with BC 13 (formerly Dynamics NAV 2018). Extensions allow developers to modify standard objects such as tables, pages, and codeunits without altering Microsoft’s base code.
We live in times where many companies and developers don’t stop to consider whether sending code to large cloud-based AI models is safe.
In both Navision (Dynamics NAV) and Business Central (BC), a field is the fundamental unit of data in a table. Fields define what kind of information is stored, how it is used in business processes, and how other objects—such as pages, reports, and codeunits—interact with it.
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.