The concept of evolutionary architecture is a good fit for game server development. Game servers are complex enough to warrant a disciplined focus on building a good architecture. Yet, game development is very subjective, and making a great game is an exercise in evolution. The five principles of evolutionary architecture discussed in this podcast can help us in evolving a solid game server architecture.
Johannes Thönes talks to Rebecca Parsons, Chief Technology Officer at ThoughtWorks, about evolutionary architecture. The practice of evolutionary software architecture means making decisions as late as possible (last responsible moment) and setting up cross-functional requirements that the architecture has to meet (architectural fitness function).
In the beginning, Parsons and Thönes introduce the term evolutionary architecture and explain the difference to emergent design. Parsons also explains why big design upfront is a bad idea and why we still need architecture even in Agile projects.
Parsons then describes five principles of evolutionary architecture (last responsible moment, architect and develop for evolvability, Postel’s law, architect for testability, and Conway’s law). She goes on to highlight three techniques of evolutionary architecture (database refactoring, continuous delivery, and microservices). 1)“SE-Radio Episode 236: Rebecca Parsons on Evolutionary Architecture.” Software Engineering Radio. IEEE Computer Society, 21 Aug. 2015. Web. 14 Oct. 2015.
- Duration: 54:59
- Published: 8/21/15 12:25:37 PM
- Episode Download Link (76 MB): http://feedproxy.google.com/~r/se-radio/~5/V19_mvETmx0/se_radio_236-parsons_final.mp3
- Show Notes: http://feedproxy.google.com/~r/se-radio/~3/ptl7QT_BAz4/
- Episode Feed: Software Engineering Radio – the podcast for professional software developers – http://feeds.feedburner.com/se-radio?format=xml