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

Which of the following is best in terms of both efficiency and ease?

Which of the following is best in terms of both efficiency and ease?

Because of significant compile-time overhead.

Things will get broken if an attribute name is changed.

Why is it not recommended to use semi-automatic derivation in the case of a public API?

Why is it not recommended to use semi-automatic derivation in the case of a public API?

An `IO Monad` will:

1) Defer side-effects
2) Stop code from throwing exceptions

An <code>IO Monad</code> will:
<ol>
<li>Defer side-effects</li>
<li>Stop code from throwing exceptions</li>
</ol>

Test your knowledge and understanding by taking a quiz on pure service implementation.

Introduction

Impure Implementation

Pure Implementation

Testing Impure Services

Testing Pure Services

Benchmarks

Documentation

Conclusion

Quiz on Pure Service Implementation