Version 3.0.0: New and updated features, bug fixes, new protocol support...

Leverage the power of Kubernetes to build an efficient software delivery pipeline.

An effort to create an open standard for transmitting metrics at scale, with support for both text representation and Protocol Buffers.

At a time of soaring corporate profits and plenty of HR lip service about "wellness," millions of workers--in virtually every industry--are deeply unhappy. Why did work become so miserable? Who is responsible? And does any company have a model for doing it right?

Gerade im Bereich der IT halten externe Berater (und auch Mitarbeiter) sich oft mehr oder weniger an den Vorgaben der Aufsicht fest. So manch einer hat keine Ahnung, ob das eigentlich zielführend ist - und von was redet der Techniker am anderen Ende des Tisches da eigentlich?!?!!!??? Garniert mit eigenen Anekdoten, kleinen fiktiven Beispielen und absolut tauglich für Anfänger: Informationssicherheit & IT-Risikomanagement am Beispiel der Bank B!

The Red Hat Product Security risk report reviews the state of security for our products in 2018.

The Erlang Ecosystem Foundation is a new non-profit organization dedicated to furthering the state of the art for Erlang, Elixir, LFE, and other technologies based on the BEAM.

Common Voice is Mozilla's initiative to help teach machines how real people speak.

SecBSD is an UNIX-like operating system focused on computer security based on OpenBSD.

Clayton Christensen demonstrates how successful, outstanding companies can do everything "right" and yet still lose their market leadership – or even fail – as new, unexpected competitors rise and take over the market. There are two key parts to this dilemma.

In Rework, Jason Fried and David Heinemeier Hansson introduced a new path to working effectively. Now, they build on their message with a bold, iconoclastic strategy for creating the ideal company culture—what they call "the calm company." Their approach directly attack the chaos, anxiety, and stress that plagues millions of workplaces and hampers billions of workers every day.

Enterprise IT (Information Technology) is a $3.8 trillion per year industry worldwide. Most of it is waste.

For twenty-five years Dan Lyons was a magazine writer at the top of his profession--until one Friday morning when he received a phone call: Poof. His job no longer existed. "I think they just want to hire younger people," his boss at Newsweek told him. Fifty years old and with a wife and two young kids, Dan was, in a word, screwed. Then an idea hit. Dan had long reported on Silicon Valley and the tech explosion. Why not join it? HubSpot, a Boston start-up, was flush with $100 million in venture capital. They offered Dan a pile of stock options for the vague role of "marketing fellow." What could go wrong?

My takeaway from these stories is this: Once you’ve learned enough that there’s a certain distance between the current version of your product and the best version of that product you can imagine, then the right approach is not to replace your software with a new version, but to build something new next to it — without throwing away what you have.

Conclusions:

1. Network performance and utilization will affect the general application throughput.
2. Check if you are hitting network bandwidth limits
3. Protocol compression can improve the results if you are limited by network bandwidth, but also can make things worse if you are not
4. SSL encryption has some penalty (~10%) with a low amount of threads, but it does not scale for high concurrency workloads.

• Collect all the materials related to the ancient Linux for historic testimony;
• Rebuild the oldest Linux system that couldn't found anywhere nowaday ;
• Provide an easiest way to learn the basics of Linux for newbies;
• For fun :-)

First off – not trying to kindle any flame wars here, just trying to broaden my (your) horizons a bit, gather some ideas (maybe I’m missing out on something cool, it’s the most used Open Source RDBMS after all) and to somewhat compare the two despite being a difficult thing to do correctly / objectively. Also I’m leaving aside here performance comparisons and looking at just the available features, general querying experience and documentation clarity as this is I guess most important for beginners. So just a list of points I made for myself, grouped in no particular order.

Dstat is a beloved tool by many, and a staple when diagnosing system performance issues. However, the original dstat is no longer actively developed. This poses an immediate problem for distributions like Fedora moving to a Python 3 stack, as it lacks a Python 3 implementation (both the tool itself, and its many plugins). It is also problematic in that the plugin system was relatively simplistic and in need of a significant redesign and rewrite to add new desired features.

Hopefully, this blog helped you understand the landscape of Distributed Tracing a bit better and clarified some of the confusions about where we are with OpenTracing today.