Recently, the dev-team to which I belong decided to abandon Jira in favor of GitHub as the sole platform for the project management. You can argue that Jira and GitHub are not really comparable, and I’d agree with you if not because - let’s be honest to each other - the former is also very very slow and clunky. As a matter of fact you will eventually find yourself dealing with unannounced UI/UX updates and a constant feeling of slowness followed by a sense of frustrastion, which is like a trademark when using a mastodon. What is more, you have to pay to use it and you need another set of credentials to remember/store.

In this post we’ll go through all the essential steps that will eventually lead you to the construction of a new self-contained web application based on a RESTful API built with the Scala Play framework and consumed by an Angular 7 front end. We will build the API from scratch putting the front end code in the same repository (within the /ui folder).

In this post we’re going to see what is a Category and in particular a Monoid, and to dive into this subject we’ll take advantage of the Scala programming language. So let’s start from the beginning and let’s try to keep the things simple and clear, because as we’ll see in a moment, the Monoid is a very simple structure defined only by its algebra.

Start programming and experimenting with a functional programming language like Scala might not seem simple at first sight. So, to get your feet wet it’s useful to have the very essential in a single place. I started writing this post in the form of a gist, but then I realized that maybe it was better to share it with the community.

S.O.L.I.D. principles