Building Operable Systems

Update: There has been a location change. There was a mixup in scheduling and we've had to change the meetup to WebAssign from Bronto. The meetup is now at WebAssign in Raleigh at 7pm, with doors opening at 6:45pm. All other details remain the same. Please update your RSVP if this affects your plans. Sorry for any inconvenience this causes.

Over two years ago (https://www.meetup.com/Triangle-DevOps/events/70312362/) we had Mark Imbriaco (https://twitter.com/markimbriaco) speak to the group where he shared some of his wisdom gained from a life time of working in operations.

Mark has agreed to come back and speak to the group again, this time reprising one of his talks from Velocity Beijing (http://velocity.oreilly.com.cn/2014/index.php?lang=en) this past year, titled "Building Operable Systems". The abstract is available below.

Building Operable Systems

The software development world has a wealth of information available about how to build good software. It is very easy to find advice on framework selection, testing methodologies, pros and cons of language selection, and a myriad of other topics. One area that is frequently neglected, however, is operability.
In this talk we will explore some practical techniques that can be used by software and operations engineers to build systems that are manageable in production.

Some of the topics we will survey include things like:

• Runtime Consistency

• Resilience patterns: Feature flags, circuit breakers, and more.

• Practical logging tips

• Simple process inspection

• Monitoring patterns

For those of you who don't know, Mark lives in Wake Forest and his career spans a large number of companies, including 37Signals, LivingSocial, Heroku, and GitHub. His current position is with Digital Ocean, where he is VP of Technical Operations.

We're at WebAssign. Doors open at 6:45pm, with pizza and drinks being provided.

I look forward to seeing everyone who can make it out.

• Mark Mzyk