Yes. Blaze is the name of the binary inside Google. 90% of the code is in common. Differences are 1. integration with Google-internal tools, and 2. legacy misfeatures we plan to remove.
(I work on Bazel)
What kind of internal integrations, if I may ask? Does it automatically deploy code for you on a successful build or something like that?
For example, blaze has integration with Google's build cache. Most of the time it takes 0 seconds to compile a given file, when someone else has compiled it before with the exactly same contents, dependencies and compiler flags.
Blaze is the internal version, such as borg vs kubernetes
Except that Blaze/Bazel share code, are very similar and converging over time. The plan is for Google to use Bazel+extensions at some point in the future. Borg and Kubernetes don't share code (they are written in different languages: C++ and Go), look similar only from a very high level perspective and are diverging over time.
Right. It's better to say that kubernetes was designed by people who were heavily influenced by borg.
Bazel started from open sourced parts of Blaze but also added its own features. What I understand from public sources is that Blaze doesn't support external dependencies which Bazel does.