In previous articles we have described how to build a REST Api with Spray and how to (de)serialize case classes with json4s. However, in order to keep things simple, we didn’t always do things as suggested by spray.io.

In this article we will redeem ourselves and we will describe how to build a REST CRUD application in Spray, taking full advantage of the tools offered by the Spray’s tool kit.

All the code shown in this tutorial can be found on GitHub.

Our CRUD Application

A REST CRUD application is an application that manipulated entities using 4 key operations: create, retrieve, update, delete.

In this tutorial we will describe how to create a simple REST CRUD application to manage question entities.

A question has the following fields: id , title , text . We are going to use json4s to translate it to the following case class (for more information on how to use json4s, have a look here):

case class Question(id: String, title: String, text: String)

Also, to keep things simple, we are not going to store the entities in a database but we will simply keep them in memory. In this tutorial the class QuestionService simulates a persistent storage by storing all the questions in a Vector (see its complete code here):

package com.danielasfregola.quiz.management.services import com.danielasfregola.quiz.management.entities.{Question, QuestionUpdate} import scala.concurrent.{ExecutionContext, Future} class QuestionService(implicit val executionContext: ExecutionContext) { var questions = Vector.empty[Question] def createQuestion(question: Question): Future[Option[String]] = ... def getQuestion(id: String): Future[Option[Question]] = ... def updateQuestion(id: String, update: QuestionUpdate): Future[Option[Question]] = ... def deleteQuestion(id: String): Future[Unit] = ... }

POST – Create a Question

Usage

The first task of our application is to define an endpoint to create a question entity.

According to the REST protocol, an entity is created through a POST request that should reply with a 201 (Created) HTTP status code. Also, a Location Header with the URI that identifies the location of the new entity should be returned.

Note that a POST request is non-idempotent: if the entity already exists or cannot be created, we should return an HTTP error status code.

For our questions application, this can be translated in the following curl command:

curl -v -H "Content-Type: application/json" \ -X POST http://localhost:5000/questions \ -d '{"id": "test", "title": "MyTitle", "text":"The text of my question"}'

The first time we make the request, we should get a reply similar to the following:

* Trying ::1... * Connected to localhost (::1) port 5000 (#0) > POST /questions HTTP/1.1 > Host: localhost:5000 > User-Agent: curl/7.43.0 > Accept: */* > Content-Type: application/json > Content-Length: 68 > * upload completely sent off: 68 out of 68 bytes < HTTP/1.1 201 Created < Server: Quiz Management Service REST API < Date: Sat, 21 Nov 2015 11:37:11 GMT < Location: http://localhost:5000/questions/test < Content-Length: 0 < * Connection #0 to host localhost left intact

If we repeat the request again, we will get an HTTP response with a 409 (Conflict) status code as the entity already exists:

* Trying ::1... * Connected to localhost (::1) port 5000 (#0) > POST /questions HTTP/1.1 > Host: localhost:5000 > User-Agent: curl/7.43.0 > Accept: */* > Content-Type: application/json > Content-Length: 68 > * upload completely sent off: 68 out of 68 bytes < HTTP/1.1 409 Conflict < Server: Quiz Management Service REST API < Date: Sat, 21 Nov 2015 11:53:34 GMT < Content-Length: 0 <

Implementation

Spray has several methods to complete a generic result and convert it into a Route (see the Spray Documentation for more information). However, there isn’t a standard function to transform a result into a Location Header ….so we are going to write one! 😀

Note that our implementation is tailored to the behaviour of our system: when QuestionService creates a question, it returns a Future[Option[T]] and, if the returned option is not defined, we want to return a different HTTP status code.

package com.danielasfregola.quiz.management.routing import com.danielasfregola.quiz.management.serializers.JsonSupport import spray.http.HttpHeaders import spray.routing._ import scala.concurrent.{ExecutionContext, Future} trait MyHttpService extends HttpService with JsonSupport { implicit val executionContext: ExecutionContext def completeWithLocationHeader[T](resourceId: Future[Option[T]], ifDefinedStatus: Int, ifEmptyStatus: Int): Route = onSuccess(resourceId) { maybeT => maybeT match { case Some(t) => completeWithLocationHeader(ifDefinedStatus, t) case None => complete(ifEmptyStatus, None) } } def completeWithLocationHeader[T](status: Int, resourceId: T): Route = requestInstance { request => val location = request.uri.copy(path = request.uri.path / resourceId.toString) respondWithHeader(HttpHeaders.Location(location)) { complete(status, None) } } }

We can now put everything together and define the endpoint to create a question entity:

package com.danielasfregola.quiz.management.resources import com.danielasfregola.quiz.management.entities.{QuestionUpdate, Question} import com.danielasfregola.quiz.management.routing.MyHttpService import com.danielasfregola.quiz.management.services.QuestionService import spray.routing._ trait QuestionResource extends MyHttpService { val questionService: QuestionService def questionRoutes: Route = pathPrefix("questions") { pathEnd { post { entity(as[Question]) { question => completeWithLocationHeader( resourceId = questionService.createQuestion(question), ifDefinedStatus = 201, ifEmptyStatus = 409) } } } ~ ... } }

GET – Retrieve a Question

Usage

Now that we have created a question, we can retrieve it by performing a GET request to the URI that identifies the entity (i.e.: the one returned in the Location Header ). The request should respond with either a 200 (OK) HTTP status code with a body containing the question entity or a 404 (NotFound) HTTP status code with empty body.

For example, we can get an existing question with the following curl command…

curl -v http://localhost:5000/questions/test

…and it should return something similar to the following:

* Trying ::1... * Connected to localhost (::1) port 5000 (#0) > GET /questions/test HTTP/1.1 > Host: localhost:5000 > User-Agent: curl/7.43.0 > Accept: */* > < HTTP/1.1 200 OK < Server: Quiz Management Service REST API < Date: Sat, 21 Nov 2015 12:23:34 GMT < Content-Type: application/json; charset=UTF-8 < Content-Length: 64 < * Connection #0 to host localhost left intact {"id":"test","title":"MyTitle","text":"The text of my question"}

Moreover, if we request an entity that doesn’t exists…

curl -v http://localhost:5000/questions/non-existing-question

….we should get a 404 error code:

* Trying ::1... * Connected to localhost (::1) port 5000 (#0) > GET /questions/non-existing-question HTTP/1.1 > Host: localhost:5000 > User-Agent: curl/7.43.0 > Accept: */* > < HTTP/1.1 404 Not Found < Server: Quiz Management Service REST API < Date: Sat, 21 Nov 2015 12:25:43 GMT < Content-Length: 0 < * Connection #0 to host localhost left intact

Implementation

This behaviour can be easily be achieved with Spray as it will automatically complete optional values:

– if the option is defined, complete will transform it in a HTTP response with status 200 (OK) status code and a body containing the entity json representation.

– if the option is empty, it will just return a HTTP response with status 404 (NotFound) status code.

package com.danielasfregola.quiz.management.resources import com.danielasfregola.quiz.management.entities.{QuestionUpdate, Question} import com.danielasfregola.quiz.management.routing.MyHttpService import com.danielasfregola.quiz.management.services.QuestionService import spray.routing._ trait QuestionResource extends MyHttpService { val questionService: QuestionService def questionRoutes: Route = pathPrefix("questions") { ... ~ path(Segment) { id => get { complete(questionService.getQuestion(id)) } ~ ... } } }

PUT – Update a Question

Usage

When updating an entity, we should use a PUT request . Also, we should send only the fields that we want to update, not the whole object. Not only this will make the usage of our API easier, but it will also reduce potential concurrency issues.

If the update goes through, we should get a HTTP response with a 200 (OK) status code with the updated entity in the body. On the other side, if the update was not possible, for example because the entity no longer exists, we should get a HTTP response with status 404 (NotFound) and an empty body.

Note that a PUT request is idempotent : performing the update multiple times should already return the same result.

In our application we can update the question entity with the following curl command…

curl -v -H "Content-Type: application/json" \ -X PUT http://localhost:5000/questions/test \ -d '{"text":"Another text"}'

….and get the following reply:

* Trying ::1... * Connected to localhost (::1) port 5000 (#0) > PUT /questions/test HTTP/1.1 > Host: localhost:5000 > User-Agent: curl/7.43.0 > Accept: */* > Content-Type: application/json > Content-Length: 23 > * upload completely sent off: 23 out of 23 bytes < HTTP/1.1 200 OK < Server: Quiz Management Service REST API < Date: Sat, 21 Nov 2015 12:44:03 GMT < Content-Type: application/json; charset=UTF-8 < Content-Length: 53 < * Connection #0 to host localhost left intact {"id":"test","title":"MyTitle","text":"Another text"}

Similarly, if we try to update a resource that doesn’t exist…

curl -v -H "Content-Type: application/json" \ -X PUT http://localhost:5000/questions/non-existing-question \ -d '{"text":"Another text"}'

…we should get a 404 (NotFound) error code:

* Trying ::1... * Connected to localhost (::1) port 5000 (#0) > PUT /questions/non-existing-question HTTP/1.1 > Host: localhost:5000 > User-Agent: curl/7.43.0 > Accept: */* > Content-Type: application/json > Content-Length: 23 > * upload completely sent off: 23 out of 23 bytes < HTTP/1.1 404 Not Found < Server: Quiz Management Service REST API < Date: Sat, 21 Nov 2015 12:46:15 GMT < Content-Length: 0 < * Connection #0 to host localhost left intact

Implementation

As explained in the previous section, we want the client of our API to send just the fields to update, not the whole entity. In order to achieve this, we will deserialize the body of our PUT request to the following case class:

case class QuestionUpdate(title: Option[String], text: Option[String])

Note that we decided not to allow our clients to update the field id , as it is used to locate the entity.

Similarly to what we did for the GET request , Spray does all the work for us:

package com.danielasfregola.quiz.management.resources import com.danielasfregola.quiz.management.entities.{QuestionUpdate, Question} import com.danielasfregola.quiz.management.routing.MyHttpService import com.danielasfregola.quiz.management.services.QuestionService import spray.routing._ trait QuestionResource extends MyHttpService { val questionService: QuestionService def questionRoutes: Route = pathPrefix("questions") { ... ~ path(Segment) { ... ~ put { entity(as[QuestionUpdate]) { update => complete(questionService.updateQuestion(id, update)) } } ~ ... } } }

DELETE – Delete a Question

Usage

Finally, we want to have an endpoint to delete a question entity. This can be achieved by sending a DELETE request to the URI that identifies the entity that should reply with a 204 (NoContent) status code once the operation has been completed. Note that DELETE is idempotent, so deleting a resource that has been already deleted should still return an HTTP response with a 204 (NoContent) status code and an empty body.

For example, we can delete the question test with the following…

curl -v -X DELETE http://localhost:5000/questions/test

…and get the following result back:

* Trying ::1... * Connected to localhost (::1) port 5000 (#0) > DELETE /questions/test HTTP/1.1 > Host: localhost:5000 > User-Agent: curl/7.43.0 > Accept: */* > < HTTP/1.1 204 No Content < Server: Quiz Management Service REST API < Date: Sat, 21 Nov 2015 12:58:30 GMT < Content-Type: application/json; charset=UTF-8 < Content-Length: 2 < * Excess found in a non pipelined read: excess = 2 url = /questions/non-existing-question (zero-length body) * Connection #0 to host localhost left intact

Implementation

Once again, Spray makes our life really easy as all we have to do in order to define an endpoint to delete a question is just to reuse already defined functions in the Spray’s tool kit:

package com.danielasfregola.quiz.management.resources import com.danielasfregola.quiz.management.entities.{QuestionUpdate, Question} import com.danielasfregola.quiz.management.routing.MyHttpService import com.danielasfregola.quiz.management.services.QuestionService import spray.routing._ trait QuestionResource extends MyHttpService { val questionService: QuestionService def questionRoutes: Route = pathPrefix("questions") { ... ~ path(Segment) { id => ... ~ delete { complete(204, questionService.deleteQuestion(id)) } } } }

Summary

In this article we have described what a REST CRUD application is. Also, we have provided a simple tutorial on how to create a simple CRUD application using Spray. The code of the application analysed can be found on GitHub.