In my last post about Observability with OpenTelemetry, we explored the basic components of OpenTelemetry – traces, spans, attributes – and considered tracing as a way to add context to structured logs. If you are not already familiar with the basic concepts of OpenTelemetry, I highly recommend you go back and check out that post.
I recently worked at an organization that relied heavily on the “scream test” release methodology. If you’re not familiar, it goes something like this:
Streaming allows you to move and transform data without holding the data in memory, or in a intermediary file location. This allows you to work with very large data sets, without having to scale up your hardware.
My newest toys at work are Elasticsearch and Kibana. Getting these tools to integrate with our Kubernetes-based applications was a bit of a journey
For my day job, I work at a company called Aeris Weather. Among other things, our company sells weather data services via a pretty robust data API, and a map tile server.
I’ve recently been playing around with RxJS. If you’re not familiar with RxJS, I would suggest watching this talk by Jafar Husain about how Netflix used RxJS to build it’s new front-end.
I ran into an article by Michael Schöbel titled We Don’t Need More Programmers, We Need Better Tools:
It never ceases to amaze me, how seemingly common problems start to look like they must be fringe cases…
I’m a total nerd over dependency injection, so I’ve really enjoyed using Wire.js. If you’re not familiar with Wire.js, it’s basically a dependency injection library for javascript.