Then provide an implementation for `IStudentApi` on the server:
```fs
open SharedTypes

let getStudents() =
async {
return [
{ Name = "Mike"; Age = 23; }
{ Name = "John"; Age = 22; }
{ Name = "Diana"; Age = 22; }
]
}

let findStudentByName name =
async {
let! students = getStudents()
let student = List.tryFind (fun student -> student.Name = name) students
return student
}

let studentApi : IStudentApi = {
studentByName = findStudentByName
allStudents = getStudents
}
```
Now that we have the implementation `studentApi`, you can expose it as a web service from different web frameworks. We start with [Suave](https://github.com/SuaveIO/suave)

Install the library from Nuget using Paket:

```
paket add Fable.Remoting.Suave --project /path/to/Project.fsproj
```
Create a [WebPart](https://suave.io/composing.html) from the value `studentApi`
```fs
open Suave
open Fable.Remoting.Server
open Fable.Remoting.Suave

let webApp : WebPart =
Remoting.createApi()
|> Remoting.fromValue studentApi
|> Remoting.buildWebPart

// start the web server
startWebServer defaultConfig webApp
```
Yes, it is that simple.
You can think of the `webApp` value as if it was the following in pseudo-code:
```fs
let webApp =
choose [
POST
>=> path "/IStudentApi/studentByName"
>=> (* deserialize request body (from json) *)
>=> (* invoke studentApi.getStudentByName with the deserialized input *)
>=> (* give client the output back serialized (to json) *)

// other routes
]
```
You can enable diagnostic logging from Fable.Remoting.Server (recommended) to see how the library is doing it's magic behind the scenes :)
```fs
let webApp =
Remoting.createApi()
|> Remoting.fromValue studentApi
|> Remoting.withDiagnosticsLogger (printfn "%s")
|> Remoting.buildWebPart
```
### AspNetCore Middleware
Install the package from Nuget using paket
```
paket add Fable.Remoting.AspNetCore --project /path/to/Project.fsproj
```
Now you can configure your remote handler as AspNetCore middleware
```fs
let webApp =
Remoting.createApi()
|> Remoting.fromValue studentApi

let configureApp (app : IApplicationBuilder) =
// Add Remoting handler to the ASP.NET Core pipeline
app.UseRemoting webApp

[]
let main _ =
WebHostBuilder()
.UseKestrel()
.Configure(Action configureApp)
.Build()
.Run()
0
```

### Giraffe

You can follow the Suave part up to the library installation, where it will become:
```
paket add Fable.Remoting.Giraffe --project /path/to/Project.fsproj
```

Now instead of a WebPart, by opening the `Fable.Remoting.Giraffe` namespace, you will get a [HttpHandler](https://github.com/giraffe-fsharp/Giraffe/blob/master/DOCUMENTATION.md#httphandler) from the value `server`:
```fs
open Giraffe
open Fable.Remoting.Server
open Fable.Remoting.Giraffe

let webApp : HttpHandler =
Remoting.createApi()
|> Remoting.fromValue studentApi
|> Remoting.buildHttpHandler

let configureApp (app : IApplicationBuilder) =
// Add Giraffe to the ASP.NET Core pipeline
app.UseGiraffe webApp

let configureServices (services : IServiceCollection) =
// Add Giraffe dependencies
services.AddGiraffe() |> ignore

[]
let main _ =
WebHostBuilder()
.UseKestrel()
.Configure(Action configureApp)
.ConfigureServices(configureServices)
.Build()
.Run()
0
```

### Saturn

You can use the same `webApp` generated by the Giraffe library.

```fs
open Saturn
open Fable.Remoting.Server
open Fable.Remoting.Giraffe

let webApp : HttpHandler =
Remoting.createApi()
|> Remoting.fromValue studentApi
|> Remoting.buildHttpHandler

let app = application {
url "http://127.0.0.1:8083/"
use_router webApp
}

run app
```

### Azure Functions (isolated)

To use Azure Functions in isolated mode with custom HttpTrigger as serverless remoting server, just install:
```
dotnet add package Fable.Remoting.AzureFunctions.Worker
```
or using paket
```
paket add Fable.Remoting.AzureFunctions.Worker --project /path/to/Project.fsproj
```

Since Azure Functions don't know anything about [HttpHandler](https://github.com/giraffe-fsharp/Giraffe/blob/master/DOCUMENTATION.md#httphandler) we need to use built-in `HttpRequestData` and `HttpResponseData` objects. Luckily we have `Remoting.buildRequestHandler` and `HttpResponseData.fromRequestHandler` functions to the rescue:
```fs
open Fable.Remoting.Server
open Fable.Remoting.AzureFunctions.Worker
open Microsoft.Azure.Functions.Worker
open Microsoft.Azure.Functions.Worker.Http
open Microsoft.Extensions.Logging

type Functions(log:ILogger) =

[]
member _.Index ([] req: HttpRequestData, ctx: FunctionContext) =
Remoting.createApi()
|> Remoting.withRouteBuilder FunctionsRouteBuilder.apiPrefix
|> Remoting.fromValue myImplementation
|> Remoting.buildRequestHandler
|> HttpResponseData.fromRequestHandler req
```

Of course, having one implementation per Function App is not ideal, so `HttpResponseData.fromRequestHandlers` is here to the rescue:

```fs
type Functions(log:ILogger) =

[]
member _.Index ([] req: HttpRequestData, ctx: FunctionContext) =
let handlerOne =
Remoting.createApi()
|> Remoting.withRouteBuilder FunctionsRouteBuilder.apiPrefix
|> Remoting.fromValue myImplementationOne
|> Remoting.buildRequestHandler

let handlerTwo =
Remoting.createApi()
|> Remoting.withRouteBuilder FunctionsRouteBuilder.apiPrefix
|> Remoting.fromValue myImplementationTwo
|> Remoting.buildRequestHandler

[ handlerOne; handlerTwo ] |> HttpResponseData.fromRequestHandlers req
```

## Fable Client
Install `Fable.Remoting.Client` from nuget using Paket:
```
paket add Fable.Remoting.Client --project /path/to/Project.fsproj
```
Reference the shared types to your client project
```

```
Start using the library:
```fs
open Fable.Remoting.Client
open SharedTypes

// studentApi : IStudentApi
let studentApi =
Remoting.createApi()
|> Remoting.buildProxy

async {
// students : Student[]
let! students = studentApi.allStudents()
for student in students do
// student : Student
printfn "Student %s is %d years old" student.Name student.Age
}
|> Async.StartImmediate
```
Finally, when you are using `webpack-dev-server`, you have to change the config from this:
```js
devServer: {
contentBase: resolve('./public'),
port: 8080
}
```
to this:
```js
devServer: {
contentBase: resolve('./public'),
port: 8080,
proxy: {
'/*': { // tell webpack-dev-server to re-route all requests from client to the server
target: "http://localhost:5000",// assuming the backend server is hosted on port 5000 during development
changeOrigin: true
}
}
```
That's it!

## Dotnet Client
You can also use client functionality in non-fable projects, such as a console, desktop or mobile application.

Install `Fable.Remoting.DotnetClient` from nuget using Paket:
```
paket add Fable.Remoting.DotnetClient --project /path/to/Project.fsproj
```
Reference the shared types in your client project
```

```
Start using the library:
```fs
open Fable.Remoting.DotnetClient
open SharedTypes

// studentApi : IStudentApi
let studentApi =
Remoting.createApi "http://localhost:8085"
|> Remoting.buildProxy

async {
// students : Student[]
let! students = studentApi.allStudents()
for student in students do
// student : Student
printfn "Student %s is %d years old" student.Name student.Age
}
|> Async.StartImmediate
```
Notice here, that unlike the Fable client, you will need to provide the base Url of the backend because the dotnet client will be deployed separately from the backend.

## Adding a new route
- Add another record field function to `IStudentApi`
- Implement that function
- Restart server and client

Done! You can now use that function from the client too.

See the following article if you are interested in how this library is implemented (a bit outdated but gives you an overview of the mechanism)
[Statically Typed Client-Server Communication with F#: Proof of Concept](https://medium.com/@zaid.naom/statically-typed-client-server-communication-with-f-proof-of-concept-7e52cff4a625#.2ltqlajm4)