Language Selection

English French German Italian Portuguese Spanish

Seesaw Liberated

Filed under
Google
  • Google’s ‘Seesaw’ Load Balancer Goes Open Source

    If you’re a network or systems administrator, you’re likely familiar with the concept of a load balancer. It’s a hardware device or software stack that distributes network application load across all the machines and servers connected to it in order to help mitigate network congestion. Google’s software solution, called Seesaw, was created in 2012 in response to a lack of adequate load balancing software for Google’s own use. Coded in Google’s own Go language, the software boasted a flexible Linux backbone and was used to manage Google’s own network needs, which entailed things like automated deployment and ease of use and maintenance.

  • Google Open Sources Its Seesaw Load Balancer

    Google announced today that it is open-sourcing Seesaw — a Linux-based load balancing system. The code for the project, which is written in Google’s Go language, is now available on GitHub under the Apache license.

    As Google Site Reliability Engineer Joel Sing, who works on the company’s corporate infrastructure, writes in today’s announcement, Google used to use two different load balancing systems back in 2012. Both, however, “presented different sets of management and stability challenges.” So to fix this, he and his team set out to find a new solution and because the ones available at the time didn’t meet Google’s needs, they started writing their own.

More in Tux Machines

Feral Interactive Ports Life Is Strange to Linux and Mac, Episode 1 Is Now Free

Feral Interactive has recently announced that they have managed to successfully port the popular, award-winning Life Is Strange game to GNU/Linux and Mac OS X operating systems. Read more

Introduction to Modularity

Modularity is an exciting, new initiative aimed at resolving the issue of diverging (and occasionally conflicting) lifecycles of different “components” within Fedora. A great example of a diverging and conflicting lifecycle is the Ruby on Rails (RoR) lifecycle, whereby Fedora stipulates that itself can only have one version of RoR at any point in time – but that doesn’t mean Fedora’s version of RoR won’t conflict with another version of RoR used in an application. Therefore, we want to avoid having “components”, like RoR, conflict with other existing components within Fedora. Read more

Our First Look at Linux Mint 18 Cinnamon

Now that I’ve had about a week to play around in Mint 18, I find a lot to like and have no major complaints. While Cinnamon probably isn’t destined to become my desktop of choice, I don’t dislike it and find it, hands down, the best of the GNOME based desktops I’ve tried so far. Anybody looking for a powerful, all purpose distro that’s designed to work smoothly and which can be mastered with ease would be hard pressed to find anything better. Read more

The subtle art of the Desktop

The history of the Gnome and KDE desktops go a long way back and their competition, for the lack of a better term, is almost as famous in some circles as the religious divide between Emacs and Vi. But is that competition stil relevant in 2016? Are there notable differences between Gnome and KDE that would position each other on a specific segment of users? Having both desktops running on my systems (workstation + laptop) but using really only one of them at all times, I wanted to find out by myself. My workstation and laptop both run ArchLinux, which means I tend to run the latest stable versions of pretty much any desktop software. I will thus be considering the latest stable versions from Gnome and KDE in this post. Historically, the two environments stem from different technical platforms: Gnome relies on the GTK framework while KDE, or more exactly the Plasma desktop environment, relies on Qt. For a long time, that is until well into the development of the Gnome 3.x platform, the major difference was not just technical, it was one of style and experience. KDE used to offer a desktop experience that was built along the lines of Windows, with a start center on the bottom left, a customizable side bar, and desktop widgets. Gnome had its two bars on the top and bottom of the screen, and was seemingly used as the basis for the first design of Mac OS X, with the top bar offering features that were later found in the Apple operating system. Read more