Why you need a systems reliability engineer
How can you ensure that the software and services you build today can deliver what your customers and consumers need in the future? If this is a question you think your organization should be asking, then you might need a systems reliability engineer (SRE). SREs are software engineers who focus on the reliability and uptime of applications and services not just in the short-term, but with a focus on scalability and long-term use.Sometimes referred to as "site reliability engineer," or "services reliability engineer," this engineering role is one that's finding its footing as DevOps practices take hold in IT departments, says Jason Hand, DevOps evangelist and incident and alerting specialist with VictorOps. The roles are most prevalent in cloud services, SaaS, PaaS and Iaas companies whose clients rely on them to keep those services available 24/7/365, he says. For organizations that rely on uptime, availability and reliability, an SRE is a logical talent add, as every minute of downtime chips away at the bottom line, Hand says.To read this article in full or to leave a comment, please click here






