Behaviour-Driven Development in practice
Behaviour-Driven Development (BDD) is a software development process. As the name implies, it is based on the idea that the expected behavior of a system is defined before the source code for that system is written.
The behavior is documented in the form of a suit of tests that can be executed to validate how the system responds to a set of examples that cover the use cases of that system.
Design your events granularity
What events should my component publish? Not always an easy question to answer.
Software design is a continuous task. You never finish a software project, because it needs to evolve as the team’s knowledge about the problem it solves grows. This is why one of the principal characteristics of good software is being easy to change.
In an asynchronous software architecture, the events that a component publishes define its contract with the other components in the system. And a good interface contract is one that lets the component be useful to the other components, while making it easy enough to modify as the project grows.
Java Streams are not for Seniors
A few days ago I stumpled upon this LinkedIn post (in Spanish, but easily understandable) including this image with two solutions to the same problem:
Multitenant Services with Micronaut
A software system is considered Multitenant when it can serve multiple clients with different data. Each registered user is part of one tenant, and will have access to the data that their tenant owns only.
In this article I will be covering how the Micronaut framework supports the creation of multi-tenant applications, as well as many other useful features for general development.
Spec-Driven Development in practice
There are no new concepts in Spec-Driven Development. The idea of treating formal specification documents as the authoritative source of truth in software development has been around since the beginning of modern computing.
In the 1960s and 1970s, computer scientists developed formal methods to write mathematically verifiable specifications before implementing software. In the 1980s, Design by Contract introduced new metaphors to describe how the different components collaborate in a software system.
Behavior-Driven Development in the early 2000s established executable specifications (Given-When-Then) as living documentation that drives code development. And in the 2010s, API-First / Schema-Driven Design tools pioneered static code generation from contract definitions.