Book Image

Software Architecture with Spring 5.0

By : René Enríquez, Alberto Salazar
Book Image

Software Architecture with Spring 5.0

By: René Enríquez, Alberto Salazar

Overview of this book

Spring 5 and its ecosystem can be used to build robust architectures effectively. Software architecture is the underlying piece that helps us accomplish our business goals whilst supporting the features that a product demands. This book explains in detail how to choose the right architecture and apply best practices during your software development cycle to avoid technical debt and support every business requirement. Choosing the right architecture model to support your business requirements is one of the key decisions you need to take when a new product is being created from scratch or is being refactored to support new business demands. This book gives you insights into the most common architectural models and guides you when and where they can be used. During this journey, you’ll see cutting-edge technologies surrounding the Spring products, and understand how to use agile techniques such as DevOps and continuous delivery to take your software to production effectively. By the end of this book, you’ll not only know the ins and outs of Spring, but also be able to make critical design decisions that surpass your clients’ expectations.
Table of Contents (21 chapters)
Title Page
Copyright and Credits
Packt Upsell
Contributors
Preface
Index

Summary


In this chapter, we reviewed what client-server architectures are and how to implement them using the Spring Framework. One important aspect to remember is that when we are building applications following this architectural style, it's always worth providing an SDK to make the server resources easy to consume.

Providing proper documentation can help clients to write their own code to interact with the server, if necessary. In this case, we will avoid introducing a conformist relationship among the server and clients. We also explored spring actuator, a library that can be used to add endpoints that provide information about the application. Furthermore, we reviewed how to use Postman to create tests that can regularly assess the application's health.

In the end, we created a couple of clients using a library implemented with Retrofit, which drastically reduced the effort required to consume the resources exposed by the server.

In the next chapter, we will review MVC architectures and...