Skip to content
Yesterday I spoke about a project I wanted to revive using the Play framework for Scala and so today I’ll be going through the basics via the started pack that was provided by the documentation.
Overview What is Play? It’s a full-stack framework with all the components to build a web service or, in our case, a REST API. Some of the components involve an integrated HTTP server, form handling, Cross-Site Request Forgery (CSRF) protection, a powerful routing mechanism, I18n support, and a lot more that I cannot list here.
Back in 2016, during my second year of university I attended a 36-hour hackathon in Manchester (I went to a lot of hackathons during my days as a CS student). During those 36 hours, I and one of my fellow informatics classmates (i.e. my boyfriend) decided that we wouldn’t really focus on the given challenges by the different sponsors but instead do something of our own (because why not?).
I’ve been putting off this chapter in my red book but today, I’m just going to suck it up and get through it. I’ve decided to blog about it hoping that it’ll be more fun. So… let’s get it to it, man.
This chapter is all about creating functional APIs, i.e. API’s that will not produce any sort of side effect. It sounds a bit difficult but it’s life-changing (hopefully).
Anyway, with a combination of knowledge from some more experienced developers and a lot of Googling, let’s see what we come up with.
As I mentioned, another month has quickly passed by so it’s time to reflect on what’s happened, what’s currently happening, and all the sorts. Due to the week I missed from a terrible cold, it actually hasn’t been too long since my last reflection. However, I can say that quite a bit has changed and developed so I will write one anyway.
The Good Firstly, let’s talk about how everything is going with Scala.