Keeping the Stakes Low while Breaking Production

This page summarizes the projects mentioned and recommended in the original post on dev.to

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
  • forem

    For empowering community šŸŒ±

  • To insulate from upstream libraries, we often wrap those libraries in our own implementations. This helps with the principle of least exposure; rely on the narrowest interface possible. I wrote the AbExperiment class to be the wrapper around Field Test. With the wrapper, I allowed for the system to set an ENV variable and thus force all requests to use the same experiment. This helped with running local tests.

  • flipper

    šŸ¬ Beautiful, performant feature flags for Ruby. (by flippercloud)

  • The next step came about when I learned more about our use of Flipper; a Ruby gem for dynamically toggling on and off features. I didnā€™t know when the feature would roll out, but I wanted control over the feature. I also wanted admins of other Forems to have control as well. This was trivial with Flipper. Once I deployed the code, Foremā€™s got the original behavior unless they turned ā€œflippedā€ on the feature.

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
  • Blazer

    Business intelligence made simple

  • We then pasted that into Blazer and started looking at the SQL. As we moved around the massive SQL statement, we saw the culprit. A very narrow range for allowed articleā€™s publication dates.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts