Companies have different teams to create a platform, each with its rules and ways to develop an application. With the evolution of the platforms, new applications appear that have new rules for organizing the different layers, but who validates those rules are correct? How can you validate that all the applications follow?

During this talk, you will see the relevance of creating a document that explains the architecture that all the company's applications need to follow, considering the different layers and how to interact between them. Like peer reviewers, most developers use other alternatives to validate the project's structure, but not all these strategies work. You will see a short scene where you have an application where you will implement a set of tests using ArchUnit that validates the entire structure of the application and how you can extract these rules or validations into an external library to prevent duplicate code.

Target audience is mid-developers or up who have specific knowledge of testing, like unit testing. Having experience with some particular framework is unnecessary because the talk tackles the idea of creating unit tests in a way that is agnostic of which frameworks the application uses behind the scenes.

Problems that appear during the session:

How do you define a possible architecture of an application?
How do you create tests that validate the different layers in an application?
How do you validate the interaction between different layers?
How do you externalize the rules into a library to import into all your applications?

Spring Data Redis as a Failed Solution

Speakers

Valerij Toropov

Invited experts

Aleksandra Volushkova

Other talks on «Libraries and Frameworks»

Other talks on «Data and Storage»