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

## Libraries used
Below is a list of libraries that we will be using for pure implementation. 

### 1. `http4s`
*http4s* allows for functional and typeful HTTP streaming. It employs the *_Cats_* IO to ensure referential transparency.

### 2. `Doobie`
*Doobie* will be our database layer. It is the pure functional JBDC layer for Scala. It has a monadic API, with programs in it being valued, which can be composed to form larger programs.
### 3. `Flyway`

We will once again be using Flyway for database migrations/evolutions.

### 4. _`Circe`_

We will use *Circe* for JSON codecs.

### 5. `Refined` for using refined types 
We will again be using *Refined* for using refined types.
### 6. `PostgreSQL JDBC driver`
PostgreSQL JDBC is an open-source driver that allows Java programs to connect to a PostgreSQL database using standard, database-independent Java code.

### 7. `PureConfig`

We will use *PureConfig* to help in the proper configuration loading. *PureConfig* will let us load objects directly from configuration files because it does the type conversions for basic types and case classes.


# Libraries used
Below is a list of libraries that we will be using for pure implementation. 

## 1. `http4s`
*http4s* allows for functional and typeful HTTP streaming. It employs the *_Cats_* IO to ensure referential transparency.

## 2. `Doobie`
*Doobie* will be our database layer. It is the pure functional JBDC layer for Scala. It has a monadic API, with programs in it being valued, which can be composed to form larger programs.
## 3. `Flyway`

We will once again be using Flyway for database migrations/evolutions.

## 4. _`Circe`_

We will use *Circe* for JSON codecs.

## 5. `Refined` for using refined types 
We will again be using *Refined* for using refined types.
## 6. `PostgreSQL JDBC driver`
PostgreSQL JDBC is an open-source driver that allows Java programs to connect to a PostgreSQL database using standard, database-independent Java code.

## 7. `PureConfig`

We will use *PureConfig* to help in the proper configuration loading. *PureConfig* will let us load objects directly from configuration files because it does the type conversions for basic types and case classes.


Get introduced to the building blocks of pure service.

Introduction

Impure Implementation

Pure Implementation

Testing Impure Services

Testing Pure Services

Benchmarks

Documentation

Epilogue

Getting Started

Libraries used

1. `http4s`

Getting Started

Libraries used

1. http4s

1. `http4s`