I wonder why Twitter doesn't do consulting. They have developed a lot of the big data frameworks that we use today and understand how to scale.
They have the talent and are in a unique position of being Twitter.
They have the talent and are in a unique position of being Twitter.
[1] Heron, a realtime, distributed, fault-tolerant stream processing engine - https://github.com/twitter/heron
[2] Finagle, a fault tolerant, protocol-agnostic RPC system - https://github.com/twitter/finagle/
[3] FlockDB, a distributed, fault-tolerant graph database - https://github.com/twitter/flockdb
[4] Gizzard, a flexible sharding framework for creating eventually-consistent distributed datastores - https://github.com/twitter/gizzard
[5] Twemcache, a Twitter fork of Memcached - https://github.com/twitter/twemcache
[6] Twemproxy, a fast, light-weight proxy for memcached and redis - https://github.com/twitter/twemproxy
Mesos was invented at UC Berkeley but developed and battle tested at Twitter.
In the light of this news was any of this time well spent?
Or is it just engineers hoping that dev-facing work is actually of value to a company when the wolves are circling?