Book Image

Scala Programming Projects

By : Mikael Valot, Nicolas Jorand
Book Image

Scala Programming Projects

By: Mikael Valot, Nicolas Jorand

Overview of this book

Scala Programming Projects is a comprehensive project-based introduction for those who are new to Scala. Complete with step-by-step instructions and easy-to-follow tutorials that demonstrate best practices when building applications, this Scala book will have you building real-world projects in no time. Starting with the fundamentals of software development, you’ll begin with simple projects, such as developing a financial independence calculator, and then advance to more complex projects, such as a building a shopping application and a Bitcoin transaction analyzer. You’ll explore a variety of Scala features, including its OOP and FP capabilities, and learn how to write concise, reactive, and concurrent applications in a type-safe manner. You’ll also understand how to use libraries such as Akka and Play. Furthermore, you’ll be able to integrate your Scala apps with Kafka, Spark, and Zeppelin, along with deploying applications on a cloud platform. By the end of the book, you’ll have a firm foundation in Java programming that’ll enable you to solve a variety of real-world problems, and you’ll have built impressive projects to add to your professional portfolio.
Table of Contents (18 chapters)
Title Page
Copyright and Credits
Packt Upsell
Contributors
Preface
Index

The REST API


The objective of the REST API is to interact with the shopping cart from the user interface in the browser. The main interactions are as follows:

  • Creating the cart
  • Adding, removing, and updating products in the cart

We will design our API by following REST architecture principles which was defined in 2000, by Roy Fielding.

Note

A formal description of the REST API can be found in Fielding Dissertation, CHAPTER 5, Representational State Transfer (REST), at http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm.

The main principles of the architecture are as follows:

  • It is based on client-server architecture, which means that a server can serve multiple clients.
  • It should be stateless—the server should not keep any context between client calls. The context should be kept by the client. All of the information required for the processing on the server should be part of the message sent.
  • As no context is kept on the server, it should be possible to cache responses at the server...