Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
arc42 by Example

You're reading from   arc42 by Example Software architecture documentation in practice

Arrow left icon
Product type Paperback
Published in Oct 2019
Publisher
ISBN-13 9781839214356
Length 236 pages
Edition 1st Edition
Arrow right icon
Authors (4):
Arrow left icon
Michael Simons Michael Simons
Author Profile Icon Michael Simons
Michael Simons
Ralf D. Müller Ralf D. Müller
Author Profile Icon Ralf D. Müller
Ralf D. Müller
Stefan Zörner Stefan Zörner
Author Profile Icon Stefan Zörner
Stefan Zörner
Gernot Starke Gernot Starke
Author Profile Icon Gernot Starke
Gernot Starke
Arrow right icon
View More author details
Toc

Table of Contents (9) Chapters Close

About the Book Acknowledgements
I - Introduction FREE CHAPTER II - HTML Sanity Checking III - Mass Market Customer Relationship Management IV - biking2 V - DokChess VI - docToolchain VII - macOS Menu Bar Application

IV.4 Solution Strategy

At the core of biking2 is a simple yet powerful domain model based on a few entities, of which a "Bike" and its "Milage" are the most important.

Although data-centric, the application refrains from using too much SQL to create reports, summaries, and so on, but tries to achieve that with new Java 8 features related to streams, lambdas, and map/reduce functions.

Building the application with Spring Boot is an obvious choice as one of the main quality goals is learning about it. Furthermore, using Spring Boot as a "framework" for Spring Framework allows us to concentrate on the business logic. On the one hand, there is no need to understand a complex XML configuration, while on the other, all of the building blocks are still put together using dependency injection.

Regarding dependency injection and testability, all injection should be done via constructor injection; setter injection is only allowed when there's no other technical way...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image