/blog

Choosing a model is only half the story. This guide explains why agent workloads need a governed cloud runtime—and maps the main platform patterns so you can compare options without drowning in vendor names.

While coding agents proved that file system access works, the benefits extend far beyond development. Discover how AI agents with direct file system access transform all knowledge work—from writing and research to project management and analysis—by intelligently discovering templates, documentation, and context. Learn why file system access is the universal key to unlocking true AI agent potential.

Discover Agent Skills, an open standard format for creating custom, reusable AI capabilities that work across different AI platforms. Learn how to build, share, and leverage skills following the SKILL.md specification for enhanced productivity in development workflows, code generation, and complex problem-solving.

Learn how to configure AI coding assistants (Cursor, Claude Code, GitHub Copilot) to work effectively across multiple repositories in microservices and micro-frontend architectures. Discover a practical solution that provides full codebase context without requiring a monorepo migration.

Learn how to leverage Model Context Protocol (MCP) to connect AI coding assistants to GitHub, Azure DevOps, Jira, and databases. Discover how to automate bug fixes, create PRs, query databases, and configure agent workflows in Cursor and Claude Code.

Learn how to leverage Cursor's powerful AI agents to streamline your software development workflow, from initial setup to best practices for maximizing productivity.

Relational databases are known for their reliability, data integrity and ability to optimize queries joining many tables. On the other hand, a NoSQL database may appear very limiting at first. It requires a new mindset to work with NoSQL.

Today’s expectations of modern applications are growing and if you think of creating a new application you will have to make lots of decisions that are not related to the problem you’re trying to solve.

Logging is one of the central aspects in a Microservices application. Through logging you understand how the application is behaving, which service is causing the others to go down, and what caused a specific error in one of the services. So in the next paragraphs, I’ll go through the lifecycle of adding logging to a microservices application.