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

## The current state of the art

Within the Scala ecosystem, the [Akka-HTTP](https://doc.akka.io/docs/akka-http/current/index.html) library is a popular choice for implementing server-side backends for HTTP APIs. Another popular option is the [Play](https://www.playframework.com/) framework, but using a full-blown web framework to just provide a thin API is an overkill in most cases. As most services need a database, the [Slick](http://scala-slick.org/) library is another popular choice. This completes the picture of the current landscape. 
However, while all mentioned libraries are battle-tested and proven to work well, they still have a number of problems. 




# The current state of the art

Within the Scala ecosystem, the [Akka-HTTP](https://doc.akka.io/docs/akka-http/current/index.html) library is a popular choice for implementing server-side backends for HTTP APIs. Another popular option is the [Play](https://www.playframework.com/) framework, but using a full-blown web framework to just provide a thin API is an overkill in most cases. As most services need a database, the [Slick](http://scala-slick.org/) library is another popular choice. This completes the picture of the current landscape. 
However, while all mentioned libraries are battle-tested and proven to work well, they still have a number of problems. 




Get introduced to the current landscape for impure development in Scala and the problems associated with it.

Introduction

Impure Implementation

Pure Implementation

Testing Impure Services

Testing Pure Services

Benchmarks

Documentation

Epilogue

The State of the Art

The current state of the art