1. A solution architect’s perspective on sustainability
Steve Androulakis
Software Engineer
eResearch, Monash University

2. Tolerance for trying someone else’s (web) software solution
Trying an existing software solution is a must before considering building your own
Yet using someone else’s code is like using someone else’s toothbrush
There’s only so much punishment a developer can tolerate in evaluating someone else’s solution
A solution architect’s perspective on sustainability – Steve Androulakis

3. What I’ll be happy to tolerate when evaluating someone else’s software
A public cloud image (eg. NeCTAR or Amazon)
An image I can deploy on my own machine (eg in VirtualBox)
‘Double click installer’ or installable package
A deployment configuration (eg. SaltStack, Chef, Puppet)
Shell script
Install documentation
“Just read the code, man”
Happy… Annoyed
A solution architect’s perspective on sustainability – Steve Androulakis

4. Design for immediate use
Trend of “here’s my hastily written but working code” + blog post is an acceptable starting strategy
Design specifically then generalise as needed – no useless abstractions
To build a Tesla Model S sports car for a group of users, do that first then implement as opposed to inventing the concepts of: cars, motorised transport, moving objects, objects, the universe
A solution architect’s perspective on sustainability – Steve Androulakis

5. Thanks – questions? Steve.Androulakis@monash.edu
A solution architect’s perspective on sustainability – Steve Androulakis