What people recommend, in their own words, with the receipt.
Audio streaming and sharing platform; its Backstage blog covers its engineering.
7 things
FinagleSoftware
While Finagle does an excellent job at abstracting away the tedious details behind communication protocols, connection management, and concurrency
SoundCloud on building its microservices on Finagle
developers.soundcloud.com ↗·2017-07-28Wrong?
PrometheusSoftware
These services benefit from world-class telemetry capabilities provided by Prometheus
SoundCloud on its microservices platform and moving off the monolith
developers.soundcloud.com ↗·2016-08-26Wrong?
TwirpSoftware
Twirp seemed like a great fit: It enabled us to start introducing IDLs to simplify microservice development in a way that incrementally “slotted into” a complex backend.
Why SoundCloud adopted Twirp and built Twinagle for Finagle
developers.soundcloud.com ↗·2020-06-12Wrong?
FinagleSoftware
Finagle does very well in our three requirements, and its design is based on a familiar and extensible Pipes-and-Filters meets Futures model.
Why SoundCloud picked Finagle over a pure Netty implementation and the Netflix stack
developers.soundcloud.com ↗·2014-06-13Wrong?
ScalaSoftware
All our services are written in Scala and built on top of Finagle with the help of a few light-weight, shared internal libraries
Inside a SoundCloud microservice
developers.soundcloud.com ↗·2017-07-28Wrong?
KubernetesSoftware
confidence in deployments thanks to Docker , Kubernetes and the work we do to improve testing of service interactions
SoundCloud on its microservices platform and moving off the monolith
developers.soundcloud.com ↗·2016-08-26Wrong?
Ruby on RailsSoftware
In the first two parts of this series, we talked about how SoundCloud started breaking away from a monolithic Ruby on Rails application into a microservices architecture.
SoundCloud breaking its Rails monolith into microservices
developers.soundcloud.com ↗·2014-06-13Wrong?
gRPCSoftware
We looked at gRPC but decided against it, and our reasons for this decision match very well with those stated in the original Twirp blog post
SoundCloud passing on gRPC in favour of Twirp
developers.soundcloud.com ↗·2020-06-12Wrong?
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.