Browse articles - codeboje

Let's Build an API together - Part 9

Last Update: 01.01.2018. By Jens in API Series | APIs | Newsletter

Now that we have defined our API in RAML and generated the Spring MVC controllers, etc. it is implementation time. Before we write our code, we should consider if we go with a classic 3 tier design or skip some of them.

Let's Build an API together - Part 8

Last Update: 22.12.2017. By Jens in API Series | APIs | Newsletter

Last time I wrote the RAML spec for the Kanban API and now we are going to generate some Spring MVC controller for it. So, I setup a Spring Boot project on GitHub and used the Spring MVC - RAML Spec Synchroniser Plugin for Maven.

Let's Build an API together - Part 7

Last Update: 21.12.2017. By Jens in API Series | APIs | Newsletter

I was going to use API Blueprint for designing the API and later use tools for generating a Spring MVC endpoint with it. However, as I had a basic version of the API spec, I noticed that the tool would need to run in Javascript either by hand or as a task in the build tool Grunt. Image red lights and a nice beep now :-) it becomes complicated when using two build systems in one deliverable. Also, it’s a completely different tech stack and I sometimes have trouble with nodejs tools because yeah, js devs love living on the edge. Me not, I love stable techs as it saves me headaches.

Let's Build an API together - Part 6

Last Update: 20.12.2017. By Jens in API Series | APIs | Newsletter

Now that we have covered the essentials, we could go and hack our MVP together. However, we will look at other options first.

Let's Build an API together - Part 5

Last Update: 19.12.2017. By Jens in API Series | APIs | Newsletter

The next thing we should consider in building our API is a versioning scheme. It is inevitable that we are going to change an API and at some point will face backward-incompatible changes. You might ignore it if you only have one client. But trust me, if you don’t consider it from the start, it will ruin your day in the future.

Let's Build an API together - Part 4

Last Update: 18.12.2017. By Jens in API Series | APIs | Newsletter

Now that we have settled on using REST, we face the next decision with naming our endpoints. It seems easy, but I’ve found three way so far, and I believe all claim to be best practice. Which I find funny.

Let's Build an API together - Part 3

Last Update: 15.12.2017. By Jens in API Series | APIs | Newsletter

We finished with 4 endpoints and the question if we could use REST for the API last time.

Let's Build an API together - Part 2

Last Update: 14.12.2017. By Jens in API Series | APIs | Newsletter

What we got so far:

Let's Build an API together - Part 1

Last Update: 13.12.2017. By Jens in API Series | APIs | Newsletter

In the center of Kanban is the so-called Kanban Board; yes, it is an actual board. On it, there are usually 3 columns, called swim lanes. The lanes represent the state of a task and are named Ready, Doing and Done; starting on the left. Each individual todo aka task is written on a post-it note and depending on its state, put in a column. Usually, a task will start on the left in Ready.