Download to read offline
Uploaded byRightScale
Software Engineering at RightScale
1) RightScale builds cloud analytics software to help users monitor, forecast, and optimize their cloud spending. 2) The company uses agile development practices like Scrum and emphasizes automated testing, continuous integration, and code reviews. 3) RightScale aims to provide a fun work environment with opportunities for learning new technologies and experimenting on projects.
More Related Content
Similar to Software Engineering at RightScale
![谷歌留痕技术教程[ 𝙩𝙤𝙥 𝟮𝟯𝟯. 𝙘 𝙤𝙢 ]](https://cdn.slidesharecdn.com/ss_thumbnails/top233-260130173900-2eb784f9-thumbnail.jpg?width=640&height=640&fit=bounds)
Software Engineering at RightScale
- 1. Software Engineering at RightScale Ali Khajeh-Hosseini @AliKhajeh Oct 2014, University of St Andrews
- 2. I’m here totalk about RightScale Cloud Analytics… and how we build it
- 3. Jan 2009: Startedresearching cloud cost forecasting in St Andrews Dec ‘11: With Hassan, we launched PlanForCloud Jul ‘12: Acquired by RightScale Nov ‘13: Launched Private-Beta of Cloud Analytics Mar ‘14: Cloud Analytics goes into Public-Beta Oct ‘14: Cloud Analytics is Generally Available The story so far…
- 4. What the heckis… a cloud?
- 5.
- 6.
- 7.
- 8.
- 11. Taken from oneof Dave Cliff’s talk on Cloud Computing
- 12.
- 13.
- 14. Cloud Analytics helpsusers make decisions Cloud Management helps users take actions
- 15. Cloud spending isgrowing rapidly Cloud pricing is complicated… we scrape over 12,000 prices Need to monitor, forecast and optimize cloud spend The challenge
- 16. Connect to acloud We regularly collect data
- 17. Slice and dicethe data
- 18.
- 19. Forecast costs basedon switching clouds or increased growth
- 20. Who buys ourproducts? Enterprises like Sony, EA Games, PBS, Pearson Publishing, Zynga…
- 21. Our Scale How manydev teams? How many code repos? How many instances? How much VC funding?
- 22. RightScale Engineering You’re shippingtoo late if you’re comfortable with what you’re shipping
- 23. Engineering Roles Product Manager:what should we build? Engineering Manager: how should we build it? Architects: design the systems UX: design the user experience Operations: deploy, scale and monitor systems Escalations: something just broke, who can fix it? Support/Docs: help customers use it Engineers: work with everyone to build and test it
- 24. Dev Process: Scrum 2week sprints 1 day planning End of sprint demo Release Retro 2 weeks
- 25.
- 26. Planning Story:As a user Iwant to export report as PDF So that I can share it with others • Refactor simulation engine to… • Switch from Google charts to Highcharts • Generate PDF in background queue • … • Write tests • Code review Engineers breakdown stories into tasks Granularity: less than a day to complete
- 27.
- 28. Sprint calculations ================= Sprint Summary ================= Sprint Begins: 02/06/2014 Sprint Ends: 10/06/2014 Sprint Dura=on: 9 days Team: John, Joe, Jeff, Jack Development: Vaca=on: 0 days Total Capacity: 200 hours -‐-‐ release issues: 10 -‐-‐ priority bugs: 30 -‐-‐ tech debt: 50 -‐-‐ backlog: 110 Start sprinting…
- 29. Daily standup (9:30amsharp) Answer: 1. What did you do yesterday? 2. What are going to do today? 3. Is anything blocking you?
- 30. Weekly release trains Mergeyour feature if it’s ready to ship that week
- 31.
- 32. Good tests Positive tests Negativetests Fast tests
- 33.
- 34.
- 35.
- 36.
- 37.
- 38.
- 39.
- 40.
- 41.
- 42.
- 43.
- 44.
- 45.
- 46.
- 47.
- 48.
- 49.