Alerting is so passé. Think about it. How much of an outage is spent on alerting? Two minutes, maybe 15 if you’re unlucky and the person you’re looking for is not-so-easy-to-find. There are lots of services that alert you when something broken, but what happens after that?
For the fast-growing Internet-centric and SaaS applications that you deploy weekly or even daily, you need specialized DevOps engineers who can look beyond servers to help you build the most agile and scalable platform possible.
You are pouring a sizeable portion of your life into building a world-class product. Amid the stress and passion of building out new features and fixes, it is important to also develop the discipline of automated testing and configuration management. Here’s why:
MongoDB adoption has exploded in the last few years, making it the leading NoSQL database. This widespread acceptance is largely due to its appeal among developers – MongoDB has many traits that make it the go-to option to rapidly develop applications.
This is a guest post written by Nigel Kersten, CTO of Puppet Labs, a Rackspace partner that makes IT automation software enables system administrators to deliver the operational agility and efficiency of cloud computing at enterprise-class service levels, scaling from handfuls of nodes on-premise to tens of thousands in the cloud.
MongoDB, the leading NoSQL database, incites a lot of passion on the web. There are some who love this schemaless database and others who think it’s overrun with challenges. We polled several of our Rackspace developers and operations engineers to find out what they think of MongoDB.
DevOps is a concept with different interpretations and definitions, but when you get down to it, it’s all about developers and operations teams breaking down silos and working together to innovate faster. For many companies, the ability to innovate at a rapid pace — responding to market conditions and customer feedback — is a key factor for success.
While the tech world is shifting to more of a DevOps structure, in many places the invisible wall that separates developers and operations engineers is still pretty high. Communication between both teams is necessary to make sure the application is deployed correctly and achieves high availability for end users. Here are some suggestions from different Rackers (Rackspace employees) on how to best handoff your app to the ops team instead of just throwing the code over the wall.