Articles

Running LLMs locally has become a surprisingly useful part of my development workflow.

REST is probably the most common communication mechanism between microservices.

It is simple, familiar, easy to debug, and well supported by virtually every technology stack.

But sometimes, using REST between services starts creating more problems than it solves.

Most production systems have logs.

But as discussed in The Difference Between “We Have Logs” and “We Can Debug an Incident”, having logs does not necessarily mean that we can understand what happened during an incident.

A green CI/CD pipeline is one of the most satisfying things in software engineering.

One of the most common statements during a production incident is:

“Don’t worry, we have logs.”

Running large language models locally has become a practical option for developers who want:

Most Spring Boot projects start in a very similar way:

• Controller layer
• Service layer
• Repository layer

The @Transactional annotation is one of the most useful features in Spring Boot applications.

Modern software teams have better tools than ever:

• CI/CD pipelines
• Infrastructure as Code
• Container orchestration (Kubernetes)
• Monitoring and alerting systems
• Cloud-native architectures

When building Spring Boot applications, one of the first decisions you’ll make is choosing the HTTP client for communicating with other services.

For years, RestTemplate was the standard solution. Today, WebClient is the recommended choice for new applications.