For Developers, by Developers

GOTO Blog

[container-solutions.com] Securing Microservices by Sam Newman

Are Microservices Very Secure or Very Insecure? Unfortunately, the answer to this question is “yes”. This is a write up of the excellent webinar on securing microservices given by Sam Newman, author of “Building Microservices” and frequent speaker at GOTO Conferences.

[blog.alexellis.io] Your serverless Raspberry Pi cluster with Docker

Learn how to deploy Docker Swarm to create a Raspberry Pi cluster then turn it into a serverless super-computer with the OpenFaaS framework for Docker.

[humio.com] Logging for Systems That You Care About – Feel the Hum of Your System

With modern multi-host software systems, we are missing this feeling for normal (or lack thereof) coming from subconscious sensing — we are missing a way to touch our systems. Modern software runs in datacenters that are far away and disconnected from the developers who are creating applications. We have lost that connection. Metrics dashboards provide visibility, and it is a great place to start, but they are limited as they only provide a view. They provide means to know that something is wrong, but usually not what is wrong. And dashboards are only really good for known problems, new unknown issues are harder. To do that, you need to interact with your system — touch it in real-time and do ad-hoc analytics to see what is going on. Logs are a great place to start because they are already there but in many cases it is just too difficult to get useful information quickly out of large volumes of logs.

[githubengineering.com] Kubernetes at GitHub

Over the last year, GitHub has gradually evolved the infrastructure that runs the Ruby on Rails application responsible for github.com and api.github.com. We reached a big milestone recently: all web and API requests are served by containers running in Kubernetes clusters deployed on our metal cloud. Moving a critical application to Kubernetes was a fun challenge, and we’re excited to share some of what we’ve learned with you today.

[container-solutions.com] Going Cloud Native – Where to Even Start?

So far in this blog series on Cloud Native we’ve said a lot of nice things about it being an effective approach, but “fine words butter no parsnips”, as we used to say in the 17th century. Cool tech is not much use unless we can practically apply the concepts. So in this post we’re going to consider some ways of going cloud native-ish and ponder how even a blank slate is not actually blank.

[container-solutions.com] Microservices – Thinking Outside the Lines

In our last few posts we’ve talked about two of the architectural and operational weapons of Cloud Native: containers & dynamic management. However, when I go out and talk to Cloud Native users I find that containers and orchestrators aren’t always where they started. Many companies begin with microservices and don’t adopt containers until later. In this post we are going to look at “microservices-oriented architectures” and think about how they fit in with the other Cloud Native tools.

[increment.com] The strange geography of content delivery networks

If you contract a cloud provider’s services, you don’t have to think about the location of your data at all. But someone is thinking about it.

[container-solutions.com] Is Dynamic Management the Real Ops Disruptor?

In our last post we looked closely at container packaging – what it means and why everyone’s going crazy about it. In this post, we’re going to look at another aspect of Cloud Native – dynamic management. Dynamic infrastructure management is sometimes called programmable infrastructure and its purpose is to automate data centre tasks currently done by ops folk.

[increment.com] Case studies in cloud migration: Netflix, Pinterest, and Symantec

Chris Stokel-Walker discusses three very different companies and their migrations to the cloud.

[elastic.co] A Practical Introduction to Elasticsearch

Ready to try Elasticsearch and see results? Copy and paste these requests to get started. The goal is not to learn every single command or request in Elasticsearch (that is why we have documentation); instead, the goal is that you experiment with the joy of using Elasticsearch without prior knowledge in a 30-60 minute guided tutorial. Just copy-paste every single request to see the results, and try to figure out the solution to the proposed questions.

1 2 3 4 5 6 7 8 9 10