Explore creating robust HTTP services in Scala's functional programming paradigm. Gain insights into pure vs. impure implementations, their pros and cons, and effective tool usage.

scala-platform.tar.gz

Scala-Pure

Scala-Impure

Scala-Tapir

Scala-Impure-Test

Scala-Pure-Test

Scala-Tapir-Test

Test

Scala - Run Code Widget 

Scala-Pure-copy

Scala is one of the most popular general-purpose languages that supports both object-oriented and functional programming. In this course, you will learn how to create back-end HTTP services using Scala's functional programming paradigm.

You will also learn how to develop, test, and document the service using both pure and impure ways. You will be exposed to the differences between pure and impure implementation, their respective pros and cons, and how pure implementation can be more robust in terms of performance, understandability, testability, and type safeness. 

By the end of the course, you will have a clear idea of how functional programming works in Scala and how you can use the available tools more effectively.

Pure Functional HTTP APIs in Scala


# What is left to test? 

We have no tests for our `Repository` class, which handles all the database work. We also don’t have tests for our routes. 

We have several options for testing here, but we have to do some refactoring before we can test either of them. For starters, we should move our routes out of our main application into separate classes to test them more easily. 
But should we refactor code only to gain better testability? 
> The answer is yes, we should. There are, of course, pros and cons to that, but in general, this approach makes sense. Regardless of pure or impure, we want our code to have a clean structure. 


Learn how to refactor repository code and test routes.

Introduction

Impure Implementation

Pure Implementation

Testing Impure Services

Testing Pure Services

Benchmarks

Documentation

Epilogue

Refactor the Code

What is left to test?