What people recommend, in their own words, with the receipt.
UK digital bank.
7 things
CassandraSoftware
We've made a big bet on Cassandra because it can scale linearly, which has let us nearly quadruple our customer base every year without an issue.
Monzo on betting on Cassandra for almost all persistent data
monzo.com ↗·2019-12-17Wrong?
KubernetesSoftware
Deploying Kubernetes in a highly available configuration on AWS is not for the faint of heart and requires you to get familiar with its internals, but we are very pleased with the results.
Monzo on running its backend on Kubernetes after leaving Mesos
monzo.com ↗·2016-09-19Wrong?
HashiCorp VaultSoftware
We've been running Vault for several years, and use it extensively for secret management and credential issuance.
Monzo on running Vault for secrets and credentials
monzo.com ↗·2019-12-17Wrong?
GoSoftware Google
Go makes it easy to build low-latency, high-concurrency servers, but no one language ecosystem has everything we need to build a bank.
Monzo on building its bank backend in Go
monzo.com ↗·2016-09-19Wrong?
KafkaSoftware
With all the other message queues out there, Kafka seemed like a natural fit for these requirements.
Monzo on choosing Kafka for asynchronous messaging
monzo.com ↗·2016-09-19Wrong?
LinkerdSoftware
As luck would have it, linkerd – an out-of-process proxy built on Finagle – was released earlier this year, meaning we could take advantage of all of these features without having to write our applications on the JVM.
Monzo on using linkerd as its RPC proxy
monzo.com ↗·2016-09-19Wrong?
CassandraSoftware
The Cassandra backend wasn't scaling well We designed the data model of the Cassandra backend to avoid indexes, as these are a feature of Cassandra that we generally avoid for performance reasons.
Monzo on Cassandra as a Vault storage backend not scaling
monzo.com ↗·2019-12-17Wrong?
MesosSoftware
After a year or so of using Mesos and Marathon, we decided to switch to Kubernetes, which we run on a fleet of CoreOS machines.
Monzo on moving from Mesos and Marathon to Kubernetes
monzo.com ↗·2016-09-19Wrong?
Every entry is a verbatim quote and a link to the public post it came from. Nothing is paraphrased. If it is not on record somewhere public, it is not here.
The verdict is what they actually said: loved and liked are explicit; recommended means they told others to get it; uses means they only say they use it; read is a book on their public shelf with no verdict; mixed and disliked are kept too.
A dashed affiliate link, sponsored or their own label means the post disclosed a relationship. It is shown, never hidden.
The small bar beside a date shows how dated a recommendation is for its kind of thing.
The bar shows how dated a recommendation is, for its kind of thing. Full and green is recent. It drains, and turns amber and then grey, as the post gets older.
What counts as old depends on the thing. A laptop praised four years ago has been replaced twice; a book loved twenty years ago is probably still loved. The bar is empty after about:
A striped bar means the post carries no date and the date shown is an estimate. No date at all, no bar.