These are a series of posts explaining how I set up my preferred Golang web API project that is ready for production. You can leave comment here or raise an issue on Github in case you think there is a better way of doing things. Part 1: Setting Up Your Dev Environment Part 2: Learning Material Part 3: Debugging Go Apps Remotely

For the last three years my main focus, mainly as my side project, is API from both technical and strategical point of view. I keep talking about how great Hypermedia is to random people in the office kitchen, writting API clients in different language, reading books (here, here, here, and here), and attending conferences. The problem is, we cannot expect people with no technical background invest heavily in something that has no user interface as well as immediate ROI....

Almost a year after my first mentoring experience, I did the second round and this time experience was very different. The difference is so obvious that I had to review and change the tune of the last year post. Here are this year’s findings: Do Lean This year, my main concern was to stay lean. The first couple of hours the team tried to come up with a good problem statement, and value proposition....

As part of a project we are doing, we decided to have a proper and low maintainance continuous deployment pipeline. We just wanted something that works. The whole pipeline is depicted below: Push code to a specific GitHub branch. CircleCI to build and run unit tests Save docker images in AWS Elastic Container Registry AWS Elastic Container Service for container and cluster management. Runscope for running API tests. Slack for notifications....