Learn how to create, test, and compare the back-end HTTP services in Scala.

Become a Scala Developer

In this module, we will explore the functional aspects of Scala. We will start by looking at a small use case. We will then learn the difference between pure and impure implementations by looking into referential transparency and how functional programming relies on it. We will then gradually implement the use case in both pure and impure ways. Moving ahead, we will simultaneously build, test, and document the implementations and point out the tools required along the way. By the end of this module, we will have a substantial understanding of how these techniques work, their pros and cons, and how pure implementation can be more robust.

Pure Functional HTTP APIs in Scala

<div style="margin-top:30px;"></div>

In the domain of strong static typing (not necessarily functional), we might hear phrases like “It compiles, therefore, it must be correct , and thus we don’t need tests!”

While it is true that certain kinds of tests can be omitted in favor of strong static typing, such a stance overlooks that even a correctly-typed program may produce the wrong output. 



<div></div>

In the domain of strong static typing (not necessarily functional), we might hear phrases like “It compiles, therefore, it must be correct , and thus we don’t need tests!”

While it is true that certain kinds of tests can be omitted in favor of strong static typing, such a stance overlooks that even a correctly-typed program may produce the wrong output. 



Learn about testing and its different types.

Introduction

Impure Implementation

Pure Implementation

Testing Impure Services

Testing Pure Services

Benchmarks

Documentation

Conclusion

About Tests

Do we need tests?