Simon Lasselsberger shares diagrams that illustrate the evolution of the architecture of the eight-year-old Runtastic microservice backend. You’ll discover how Runtastic gradually moved from two monolithic services with lots of design flaws to a modern microservices architecture using several database technologies and see the pitfalls, mission-critical challenges, and technology and topology decisions faced along the way.
Simon also details the company’s team structure as the deployment changed over the years—particularly how switching from departments to Agile feature teams impacted the design of microservices and caused the company to rethink its deployment strategy completely. In the early days, it rented its servers from a hosting company in Germany; then it bought its own servers and ran them in two different data centers. The company’s newest strategy is to switch from virtual servers to containers running in an on-premises OpenShift cluster.
Simon Lasselsberger is lead system architect at Runtastic, where he works on the Rails web page and Ruby backend. The company’s fourth full-time employee, Simon helped to scale the technical system and the development teams, was in charge of the backend development team for several years, and was part of the project team to transition the development process from departments to Agile feature teams. He started his professional life in chip design but always loved software a little bit more—not just because software is more agile than hardware development but also because he enjoys being able to tackle bigger problems at higher abstraction levels. That’s why he also fell in love with Ruby when he first tried it out.
Help us make this conference the best it can be for you. Have questions you'd like this speaker to address? Suggestions for issues that deserve extra attention? Feedback that you'd like to share with the speaker and other attendees?
Join the conversation here (requires login)
©2018, O’Reilly UK Ltd • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • email@example.com