Operations | Monitoring | ITSM | DevOps | Cloud

Creatives and businesses depend on programmers to fulfil their visions. The problem? Programmers are scarce. There are 230,000 unfilled jobs for programmers in the U.S. alone, and more than 90 percent of the gap is outside Silicon Valley. And, when the vast majority of the world’s great software talent resides in the halls of tech juggernauts — like Google, Amazon and Facebook — giving them an embarrassment of riches, the rest of the world is left behind.

In this article I will look at the current hosting setup of healthchecks.io, how it has evolved during the past two years, and what challenges I faced running this small but lively service.

Bleemeo has integrated the Amazon Web Services (AWS) Technology Partner program in February in order to get a closer relationship with the leader of Cloud Infrastructure market. We released at the same time our integration with AWS: CloudWatch metrics can be displayed in Bleemeo dashboards and can feed your alerts.

Last week-end, we were attending FOSDEM, in Brussels for one of the largest and maybe the largest open source conference over the world with about 8000 attendees from all over the world. Here is our recap.

Instrumental receives a lot of raw data, upwards of 1,000,000 metrics per second. Because of this, we’ve always used an event queue to aggregate the data before we permanently store it. Before switching to AWS Kinesis, this aggregation was based on many processes writing to AWS Simple Queue Service (SQS) with a one-at-a-time reader that would aggregate data, then push it into another SQS queue, where multiple readers would store the data in MongoDB.