Book Image

Building Applications with Spring 5 and Kotlin

By : Miloš Vasić
Book Image

Building Applications with Spring 5 and Kotlin

By: Miloš Vasić

Overview of this book

Kotlin is being used widely by developers because of its light weight, built-in null safety, and functional and reactive programming aspects. Kotlin shares the same pragmatic, innovative and opinionated mindset as Spring, so they work well together. Spring when combined with Kotlin helps you to reach a new level of productivity. This combination has helped developers to create Functional Applications using both the tools together. This book will teach you how to take advantage of these developments and build robust, scalable and reactive applications with ease. In this book, you will begin with an introduction to Spring and its setup with Kotlin. You will then dive into assessing the design considerations of your application. Then you will learn to use Spring (with Spring Boot) along with Kotlin to build a robust backend in a microservice architecture with a REST based collaboration, and leverage Project Reactor in your application. You’ll then learn how to integrate Spring Data and Spring Cloud to manage configurations for database interaction and cloud deployment. You’ll also learn to use Spring Security to beef up security of your application before testing it with the JUnit framework and then deploying it on a cloud platform like AWS.
Table of Contents (12 chapters)

Why is testing a crucial part of development?

Automated testing is a great way to check if the code you wrote is working. Tests check whether our software is working properly and will keep on working the way we intend it to. There are many different approaches and practices of writing tests. In this chapter, we will mention some of them.

Before the QA team starts testing the product, developers should make sure that all classes are covered with proper tests and that all of the tests are passing. When the development team does not care about writing proper tests or does not cover most (ideally all) of the codebase with tests, the QA team will most likely experience problems in testing and raise issues.

So, what are the benefits of testing? First of all, code which has been covered by tests has fewer bugs. Also, it makes it easier to keep track of documentation, and improves software...