We all know the potential of having Kubernetes in production. How easy is to build distributed systems and maintain them. When you want to locally test your complex application there are some tools like: minikube or microk8s what are really good, but they are one-single node cluster. What happen when I want to test my application, locally, but even closer to a real environment? To help with this issue, I have been working on a project which uses Vagrant to create a bunch of virtual machines which will work as Kubernetes nodes, and other stuffs that we will see later, and Ansible to configure them.
Opensouthcode is an event whose target is to promote open source code technologies and is based on Málaga (Spain). This year I was there talking about Infrastructure as code using Terraform and showing some examples that were deployed to AWS: from a simple server to a Kubernetes cluster. If you want to learn more, check all the sources: Githug repo with the examples Slides (Spanish)
Python is one of the most used languages because the ramp up is really low. A good example is the API of ayncio for building I/O bound applications. Creating asynchronous code could be really tough, but using asyncio could be a child’s play. We are going to try to build a simple chat server in this post using Python 3.7. As the server will be a TCP server, the clients only need to use Telnet to interact with.
Last week I felt so nostalgic about working with Mesos because I do not have more projects which work with this technology and people are only demanding Kubernetes. Mesos is a project which was born in Berkeley, now under the Apache umbrella, and whose target is the management of computer clusters. It will help us to create distributed systems with the feeling that we are only working with a really big machine.
Recently I worked in a project where I had to migrate a Mesos infrastructure to Kubernetes and one of the key requirements was to replace ELK (elasticsearch - logstash - kibana) with EFK (elasticsearch - fluentd - kibana). You can find a lot of information of how to use EFK in Kubernetes when your applications logs in the standard output putting a Fluentd agent in every node, but that did not happen with all the applications in the Mesos infrastructure.
Kubernetes is becoming the standard container orchestrator because of many reasons: Open Source Google Huge community Developed in Go and so on Today we can work in very complex projects which involved too many languages and technologies. Containers (like Docker) and orchestration tools help a lot in these cases. Elixir and Erlang are two languages that I work with, especially when I have to deal with problems of concurrency and low latency.
I like to read about everything but I like too much (yes, too much) to read about tech. Nowadays we are able to find a lot of kinds of books which are a good introductory step when you are going to begin with a new technology, however most of them are only a kind of Hello World. Although you have read a book, you probably know nothing about the technology. And when we talk about a non-mainstream technology the problem of finding a book which covers your needs grows.
New Web, let’s start again I have been offline for a lot of months, but it does not mean that I have been doing nothing (just the opposite). One of the things that I wanted to do is to move my blog from Weebly. It was not bad, but the writing experience was a bit unpleasure. After being experimenting with Hugo and writing in Markdown I decided to do the same with my blog.
Data Scientist is considered the sexiest job around the world, at least in the tech world, and it is true that sometimes the results that you can get applying Machine Learning techniques seem to be sorcery. Therefore a lot of people are trying to become data scientist. A lot of them use Python and almost all the on-line courses use also Python to teach the concepts. Python is a lovely programming language.
Two months ago I published in hex the first version of Galena , a Topic producer-consumer library built on top of GenStage for Elixir . It was initially designed to create some flows of producers , producer-consumers and consumers where the message has to be delivered as soon as possible. Each consumer or producer-consumer can receive messages from several producers and/or producer-consumers. Besides, consumers and producer-consumers can select the messages that want to receive thanks to a topic approach.