utf8mb4In this blog post, we’ll look at options for migrating database charsets to utf8mb4.

Migrating charsets, in my opinion, is one of the most tedious tasks in a DBA’s life. There are so many things involved that can screw up our data, making it work is always hard. Sometimes what seems like a trivial task can become a nightmare very easily, and keeps us working for longer than expected.

Rehcing GmbH
An der Mühle 39
DE 35745 Herbornseelbach

Despite overall Elasticsearch stability, it is still possible for a cluster to get into a "red" state. One of the reasons for that to happen is if an index becomes corrupt. This can be caused by an abrupt loss of power, hardware failure or—more commonly—running out of disk space. In this post we'll discuss how to bring the cluster to a healthy state with minimal or no data loss in such situation.

SavvyCAN is a cross platform QT based C++ program. It is a CAN bus reverse engineering and capture tool. It was originally written to utilize EVTV hardware such as the EVTVDue and CANDue hardware. It has since expanded to be able to use any socketCAN compatible device as well as the Macchina M2 and Teensy 3.x boards. It can capture and send to multiple buses and CAN capture devices at once.

Kayak is an application for CAN bus diagnosis and monitoring. Its main goals are a simple interface and platform independence. It is implemented in pure Java and has no platform specific dependencies. Kayak is based on SocketCAN and the connection to a SocketCAN bus takes place using TCP/IP and a socketcand server. Therefore the bus access is network transparent and can be shared with multiple users.
Kayak uses the open CAN definition format kcd. Existing .dbc CAN definitions can be converted to kcd using CANBabel.

Shell script to test the performance of the most popular DNS resolvers from your location.

Includes by default:

CloudFlare 1.1.1.1
Google 8.8.8.8
Quad9 9.9.9.9
OpenDNS
Norton
CleanBrowsing
Yandex
AdGuard
Neustar
Comodo

Via Daijiro Kato, 10 - 47843 Misano Adriatico (RN)
Ufficio REA n.121696
Reg. Imp. Rimini
C.F. - P.I. 00378530406
C.S. € 14.817.499,71 i.v.
numero verde 800 214 728

This guide describes how to use the protocol buffer language to structure your protocol buffer data, including .proto file syntax and how to generate data access classes from your .proto files. It covers the proto2 version of the protocol buffers language: for information on the newer proto3 syntax, see the Proto3 Language Guide.

This is a reference guide – for a step by step example that uses many of the features described in this document, see the tutorial for your chosen language.

This tutorial provides a basic Python programmer’s introduction to working with gRPC.

By walking through this example you’ll learn how to:

Define a service in a .proto file.
Generate server and client code using the protocol buffer compiler.
Use the Python gRPC API to write a simple client and server for your service.

It assumes that you have read the Overview and are familiar with protocol buffers. Note that the example in this tutorial uses the proto3 version of the protocol buffers language, which is currently in beta release: you can find out more in the proto3 language guide and Python generated code guide, and see the release notes for the new version in the protocol buffers Github repository.

This tutorial provides a basic Python programmer's introduction to working with protocol buffers. By walking through creating a simple example application, it shows you how to

Define message formats in a .proto file.
Use the protocol buffer compiler.
Use the Python protocol buffer API to write and read messages. 

This isn't a comprehensive guide to using protocol buffers in Python. For more detailed reference information, see the Protocol Buffer Language Guide, the Python API Reference, the Python Generated Code Guide, and the Encoding Reference.

Elixir ❤️ Embedded

Nerves is an open-source platform that combines the rock-solid BEAM virtual machine and Elixir ecosystem to easily build and deploy production embedded systems.

Simon Sinek presents a simple but powerful model for how leaders inspire action, starting with a golden circle and the question "Why?" His examples include Apple, Martin Luther King, and the Wright brothers -- and as a counterpoint Tivo, which (until a recent court victory that tripled its stock price) appeared to be struggling.

Design and implementation of an open-hardware, open-software Uninterruptible Power Supply unit.

A few days back my reMarkable paper tables arrived. A couple of friends asked me to do a review of this device, so here we go.

The Device

It is a E-Ink tablet for reading, writing and sketching using a small stylus. It is very thin (approx. 7mm) and with its 360 gramm it is very lightweight and fits into every laptop bag. Like any common mobile device today it uses micro USB for charging its 3000mAh battery. Its build in wireless can be used to sync with the vendors cloud, and with its 8GB internal storage it provides space for several thousand of pages of documents.

A minimalistic and focused guide with common use cases, patterns, principles and practises for developing Cloud Native applications on Kubernetes.

Jolokia is remote JMX with JSON over HTTP.
It is fast, simple, polyglot and has unique features. It's JMX on Capsaicin.

Jolokia is a JMX-HTTP bridge giving an alternative to JSR-160 connectors. It is an agent based approach with support for many platforms. In addition to basic JMX operations it enhances JMX remoting with unique features like bulk requests and fine grained security policies.

“Cloud native” is a term used to describe applications designed specifically to run on a cloud-
based infrastructure. Typically, cloud-native applications are developed as loosely coupled
microservices running in containers managed by platforms. These applications anticipate
failure, and they run and scale reliably even when their underlying infrastructure is experiencing outages.
To offer such capabilities, cloud-native platforms impose a set of contracts and
constraints on the applications running on them. These contracts ensure that the applications
conform to certain constraints and allow the platforms to automate the management of the
containerized applications. Many organizations understand the necessity and importance of
becoming cloud native, but do not know where to start. Ensuring that cloud-native platforms
and the containerized applications that run on them work seamlessly together provides the
ability to anticipate failure and the reliability to run and scale even when the underlying
infrastructure experiences outages. This whitepaper describes a number of principles that
containerized applications must comply with in order to become good cloud-native citizens.

Adhering to these principles will help ensure that your applications are suitable for
automation in cloud-native platforms such as Kubernetes.