Bazel vs Kubernetes

Need advice about which tool to choose?Ask the StackShare community!

Bazel

212
413
+ 1
119
Kubernetes

37.8K
32K
+ 1
623
Add tool

Bazel vs Kubernetes: What are the differences?

Bazel: Correct, reproducible, fast builds for everyone. Bazel is a build tool that builds code quickly and reliably. It is used to build the majority of Google's software, and thus it has been designed to handle build problems present in Google's development environment; Kubernetes: Manage a cluster of Linux containers as a single system to accelerate Dev and simplify Ops. Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.

Bazel belongs to "Java Build Tools" category of the tech stack, while Kubernetes can be primarily classified under "Container Tools".

Some of the features offered by Bazel are:

  • Multi-language support: Bazel supports Java, Objective-C and C++ out of the box, and can be extended to support arbitrary programming languages.
  • High-level build language: Projects are described in the BUILD language, a concise text format that describes a project as sets of small interconnected libraries, binaries and tests. By contrast, with tools like Make you have to describe individual files and compiler invocations.
  • Multi-platform support: The same tool and the same BUILD files can be used to build software for different architectures, and even different platforms. At Google, we use Bazel to build both server applications running on systems in our data centers and client apps running on mobile phones.

On the other hand, Kubernetes provides the following key features:

  • Lightweight, simple and accessible
  • Built for a multi-cloud world, public, private or hybrid
  • Highly modular, designed so that all of its components are easily swappable

"Fast" is the primary reason why developers consider Bazel over the competitors, whereas "Leading docker container management solution" was stated as the key factor in picking Kubernetes.

Bazel and Kubernetes are both open source tools. Kubernetes with 55K GitHub stars and 19.1K forks on GitHub appears to be more popular than Bazel with 12.4K GitHub stars and 2.02K GitHub forks.

Google, Slack, and Shopify are some of the popular companies that use Kubernetes, whereas Bazel is used by Google, Asana, and Square. Kubernetes has a broader approval, being mentioned in 1046 company stacks & 1096 developers stacks; compared to Bazel, which is listed in 11 company stacks and 7 developer stacks.

Advice on Bazel and Kubernetes

Hello, we have a bunch of local hosts (Linux and Windows) where Docker containers are running with bamboo agents on them. Currently, each container is installed as a system service. Each host is set up manually. I want to improve the system by adding some sort of orchestration software that should install, update and check for consistency in my docker containers. I don't need any clouds, all hosts are local. I'd prefer simple solutions. What orchestration system should I choose?

See more
Replies (1)
Mortie Torabi
Recommends
Docker Swarm

If you just want the basic orchestration between a set of defined hosts, go with Docker Swarm. If you want more advanced orchestration + flexibility in terms of resource management and load balancing go with Kubernetes. In both cases, you can make it even more complex while making the whole architecture more understandable and replicable by using Terraform.

See more
Decisions about Bazel and Kubernetes
Michael Roberts

We develop rapidly with docker-compose orchestrated services, however, for production - we utilise the very best ideas that Kubernetes has to offer: SCALE! We can scale when needed, setting a maximum and minimum level of nodes for each application layer - scaling only when the load balancer needs it. This allowed us to reduce our devops costs by 40% whilst also maintaining an SLA of 99.87%.

See more
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 28 upvotes · 3.1M views

Our whole DevOps stack consists of the following tools:

  • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
  • Respectively Git as revision control system
  • SourceTree as Git GUI
  • Visual Studio Code as IDE
  • CircleCI for continuous integration (automatize development process)
  • Prettier / TSLint / ESLint as code linter
  • SonarQube as quality gate
  • Docker as container management (incl. Docker Compose for multi-container application management)
  • VirtualBox for operating system simulation tests
  • Kubernetes as cluster management for docker containers
  • Heroku for deploying in test environments
  • nginx as web server (preferably used as facade server in production environment)
  • SSLMate (using OpenSSL) for certificate management
  • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
  • PostgreSQL as preferred database system
  • Redis as preferred in-memory database/store (great for caching)

The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

  • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
  • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
  • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
  • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
  • Scalability: All-in-one framework for distributed systems.
  • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Bazel
Pros of Kubernetes
  • 26
    Fast
  • 18
    Deterministic incremental builds
  • 15
    Correct
  • 13
    Enforces declared inputs/outputs
  • 13
    Multi-language
  • 9
    High-level build language
  • 8
    Scalable
  • 5
    Multi-platform support
  • 4
    Sandboxing
  • 3
    Dependency management
  • 2
    Flexible
  • 2
    Windows Support
  • 1
    Android Studio integration
  • 155
    Leading docker container management solution
  • 124
    Simple and powerful
  • 100
    Open source
  • 75
    Backed by google
  • 56
    The right abstractions
  • 24
    Scale services
  • 18
    Replication controller
  • 9
    Permission managment
  • 7
    Simple
  • 7
    Supports autoscaling
  • 6
    Cheap
  • 4
    Self-healing
  • 4
    Reliable
  • 4
    No cloud platform lock-in
  • 3
    Open, powerful, stable
  • 3
    Scalable
  • 3
    Quick cloud setup
  • 3
    Promotes modern/good infrascture practice
  • 2
    Backed by Red Hat
  • 2
    Runs on azure
  • 2
    Cloud Agnostic
  • 2
    Custom and extensibility
  • 2
    Captain of Container Ship
  • 2
    A self healing environment with rich metadata
  • 1
    Golang
  • 1
    Easy setup
  • 1
    Everything of CaaS
  • 1
    Sfg
  • 1
    Expandable
  • 1
    Gke

Sign up to add or upvote prosMake informed product decisions

Cons of Bazel
Cons of Kubernetes
  • 3
    No Windows Support
  • 2
    Bad IntelliJ support
  • 1
    Poor windows support for some languages
  • 1
    Constant breaking changes
  • 1
    Learning Curve
  • 1
    Lack of Documentation
  • 13
    Poor workflow for development
  • 11
    Steep learning curve
  • 5
    Orchestrates only infrastructure
  • 2
    High resource requirements for on-prem clusters

Sign up to add or upvote consMake informed product decisions

What is Bazel?

Bazel is a build tool that builds code quickly and reliably. It is used to build the majority of Google's software, and thus it has been designed to handle build problems present in Google's development environment.

What is Kubernetes?

Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.

Need advice about which tool to choose?Ask the StackShare community!

What companies use Bazel?
What companies use Kubernetes?
See which teams inside your own company are using Bazel or Kubernetes.
Sign up for Private StackShareLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Bazel?
What tools integrate with Kubernetes?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

+2
2
1007
Mar 24 2021 at 12:57PM

Pinterest

+7
3
1607
Dec 8 2020 at 5:50PM

DigitalOcean

+11
2
1813
+4
4
1805
+7
3
681
May 21 2020 at 12:02AM

Rancher Labs

+12
3
1215
What are some alternatives to Bazel and Kubernetes?
Pants
Pants is a build system for Java, Scala and Python. It works particularly well for a source code repository that contains many distinct projects.
Webpack
A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows to load parts for the application on demand. Through "loaders" modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.
Ansible
Ansible is an IT automation tool. It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates. Ansible’s goals are foremost those of simplicity and maximum ease of use.
Buck
Buck encourages the creation of small, reusable modules consisting of code and resources, and supports a variety of languages on many platforms.
CMake
It is used to control the software compilation process using simple platform and compiler independent configuration files, and generate native makefiles and workspaces that can be used in the compiler environment of the user's choice.
See all alternatives