Wow. We’re one. We’re just one. But, oh my, we made it to our first birthday. And so we’ve been thinking, what to do for our first birthday? Why not share some of the top posts for the past year?
The New Stack really started more than a year ago. It came about as Docker emerged as a symbol of the new stack, and we realized the world did not need another blog that hopped from one breaking news story to the next. More so, the new stack seemed to be the story for us. That is really what people are building — services built on sophisticated, fast and distributed infrastructure.
So we launched with that focus in mind, and since then we’ve followed this stream with stories that had sights on the news, but made a more pointed effort to explain the technology and provide perspective about it.
The stories we list here are based on page views, so it’s no surprise that Docker and Go are representative of the top posts, but they do point to the direction of the community and the interest in application development and management at scale.
In any case, thanks for your support and we look forward to another year providing deeper perspectives about the world of the new stack.
Here’s our top 10 list:
The Go programming language served as one of the most popular topics on The New Stack. This post from last year’s Gophercon is the most popular story we have run on The New Stack. It features Kelsey Falter, CEO and Founder of PopTip, who made the case for choosing Go over Node.js for her company’s backend servers. Palantir acquired PopTip last July.
A testament to the richness of open source data mining tools that are now available.
What a well-behaved API should look like.
Ansible’s ease of use shines in comparison to other configuration management tools.
By Adrian Cockcroft of Battery Ventures, the post explores what makes Docker an example for how to build a viral, developer-oriented product.
The story provides several ways to build an HTTP web server in Go, and then offers an analysis about how and why these different approaches all work effectively.
John Minnihan discusses the paradox of the Docker cache:
With regard to Docker itself, using it on a daliy basis has produced a few insights about the cache that others may find helpful. Docker will cache the results of the first build of a Dockerfile, allowing subsequent builds to be super fast. That’s no secret and it is well documented. But using the cache successfully requires the engineer to understand how it works.
Making apps work the right way in the cloud.
Mainstream IT didn’t get excited about the potential of Linux containers until quite recently, Andrew Clay Shafer writes. But Docker has changed that thinking.
Distributed systems and the quest for the source of truth.
Feature image via Flickr Creative Commons.