The latest News and Information on DevOps, CI/CD, Automation and related technologies.
Moving full speed ahead into 2021, a year that is slated to be marked by unpredictability, fast-paced change, and (still) a lot of disruption – no organization can afford to allow such disorder to impact productivity, operations, and the business overall.
IT structures across organizations are bound to get complicated one way or another. If you’ve been in business for at least a decade, chances are you’ve acquired a complex, layered system of technology that’s a hodge-podge of old and new. This complexity brings new challenges for infrastructure monitoring. It goes without saying that any enterprise needs effective IT infrastructure monitoring. But when technology is evolving at the pace it is, things can get difficult.
For quick, scalable, highly-available web services, few options compare to AWS Lambda. Just provide your code, add a little configuration, and you're done! In this article, Milap Neupane will introduce us to Lambda, show us how to get it working with Ruby and the Serverless Framework, and discuss reasons to use — or to not use! — Lambda in production.
2020 was, needless to say, not the best. Looking on the brighter side, in December, FireHydrant turned 2, and in spite of it all, we grew quite a bit. We raised our $8M Series A in May, our team grew nearly 4x in size, added some amazing features such as making FireHydrant Runbooks even more powerful with conditions, and great integrations, which you can find here. But even better, we got to work with all of you!
Both Graphite and InfluxDB are time-series monitoring data platforms, both of which have high levels of adoption throughout many industries. Both of them are suitable for enterprise use, are scalable, and are stable. That being said, there are some benefits and drawbacks to each. While InfluxDB has many benefits, many developers still prefer Graphite due to its large community, stability, and reliability.
