Archives: backend development

Adventures of a First Time Junior Dev

Being on the verge of employment for me was a rather scary situation as a wannabe developer. There were so many doubts in my mind – most of which in retrospect were absolutely irrational. As of now, I’ve been working at Wanari for 3 months. Here I will write about my fears as a student, […]

Working with Microservices in an Ideal World

Generally, microservices are great. In theory, they are divided up well, they are scalable, and they can be maintained easily. With one word, they are great. However, there are some challenges you will most probably encounter when working with microservices. This post will help you get a grip on the world of microservice-development, its challenges, and […]

Play Framework WebSocket in Java

What is WebSocket? When should I use it? WebSocket is an amazingly fast, easy to use and full-duplex way to communicate between client and server. WebSocket is recommended if you want a fast real-time application like a bid application, or a real time poker game. It’s easy to broadcast messages between users (or just send […]

Java8 orElse versus orElseGet – easily misused

So, the Java8 Optional has two really cool (and similar) functions: the orElse() and the orElseGet(). If we quickly read the javadoc for each, we will only see a small difference; one of them has a T type as a parameter and the other has a function which must return with T (as a parameter). […]

A Crash Course on YAML

This post will tell you how we use a simple YAML file to insert the initial data (like roles, privileges, admin user, and all the other necessary data) into our database. We use Play! Framework (Java) with Hibernate. The important part is how we make Objects from the YAML description using SnakeYAML (Play framework’s integrated YAML parser) though.

I’ll give you some tricks on how to use YAML easily in order to create the initial data for your application.

JavaScript Routing in Play! Framework

I was working on a Play! Framework project and I was wondering why our whole API was available in one piece. It got me thinking whether there is a way to hide at least some parts of the API from the clients. Precisely because some of the clients didn’t have the privilege/permission to execute given operations, e.g. visiting restricted pages. I thought there should be a way to hide at least the operations that are on these restricted pages. I’ve found a way to do so and below it is.

Single Responsibility and Code Organization Best Practices in Web Applications

I guess if you are reading this, you are working with web applications or web services. There are a number of posts on the internet that explain what shouldn’t be in a controller or in a model, but I didn’t find any proper summary of what should be in the MVC. So here is this blog post to collect our concepts.

Single responsibility & code organization in Web Apps title

Subject, Role, Privilege – DeadBolt in Play! Framework

If you have a website on which users can register and login, then you also want to protect your application from attackers. We recommend you to protect your application’s actions not only from attackers, but from users, too. For example, if you want to make a user who can upload Excel files on a specific UI, then that user should neither see other UIs, nor should s/he be allowed to take any other actions.

Play framework modularization: everything you wish you had been told

There are many tutorials and articles describing basic module functionality and how you can build it. These articles sometimes leave blanks of the needed information, so this post will do an in-depth tour of the topic applied in the Play framework. What is a module? In Play framework the modules are small functionality packages. These […]