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

## Maintaining referential transparency 

In the previous lesson, we saw how important referential transparency is for functional programming. If we want referential transparency, we must push the side effects to the boundaries of our system (program). This can be done by using **lazy evaluation**. 

Let’s see what lazy evaluation is by repeating the example from the previous lesson in a different way. 

# Maintaining referential transparency 

In the previous lesson, we saw how important referential transparency is for functional programming. If we want referential transparency, we must push the side effects to the boundaries of our system (program). This can be done by using **lazy evaluation**. 

Let’s see what lazy evaluation is by repeating the example from the previous lesson in a different way. 

Learn how the problems of impure implementation can be solved with pure implementation.

Introduction

Impure Implementation

Pure Implementation

Testing Impure Services

Testing Pure Services

Benchmarks

Documentation

Epilogue

An Alternate Way

Maintaining referential transparency