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

```
Type StudentName = String Refined NonEmpty
```

```
Type StudentName = String Refined MatchesRegex[W."^[a-zA-Z ]*$".T]
```

Suppose we were to make another service involving student records. What is the best possible option for a model of a student's name?

*Remember, names are not necessarily unique.*

Suppose we were to make another service involving student records. What is the best possible option for a model of a student’s name?
Remember, names are not necessarily unique.

```
Type StudentNames = NonEmptyList[StudentName]
```

```
Type StudentNames = List[StudentName]
```

```
Type StudentNames = NonEmptySet[StudentName]

Adding to the service mentioned in Q1, we want a model for a list that holds all student names.

*Remember, names are not necessarily unique.*

Adding to the service mentioned in Q1, we want a model for a list that holds all student names.
Remember, names are not necessarily unique.

A database layer should provide:

1) Programmatic access to a database
2) One table for every main data type
3) Ability to manage database changes

A database layer should provide:
<ol>
<li>Programmatic access to a database</li>
<li>One table for every main data type</li>
<li>Ability to manage database changes</li>
</ol>

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

Introduction

Impure Implementation

Pure Implementation

Testing Impure Services

Testing Pure Services

Benchmarks

Documentation

Epilogue

Quiz on Impure Service Implementation