1. Cloud Computing and Architecture
CloudArch

2. Henrik Bærbak Christensen
When I slip out of…
English…
Just please tell me 
Henrik Bærbak Christensen

3. Henrik Bærbak Christensen
Welcome to CloudArch
Me and Kasper
The core focus of this course
The ‘Lab’ Format – 1+3 hours Thu 14-18
The Exam = SkyCave Project
And why we have to talk to each other!
Henrik Bærbak Christensen

4. Henrik Bærbak Christensen
The lecturer
Henrik Bærbak Christensen
Associate professor (lektor) since 2003
Collaboration with many Danish IT companies
Systematic, Jyske Bank, Terma, B&O, KMD, Danfoss, …
Actually have complex software in production 
Faglig koordinator for Master og Diplom (SWK)
Owner of
Course development and consultancy
AU CS
Henrik Bærbak Christensen

5. … have SW in Production 
EcoSense Karibu
Henrik Bærbak Christensen

6. Henrik Bærbak Christensen
TAs
Kasper Sacharias Eenberg
PhD student in MADALGO
Will be around in the ‘Cave lab’
15-18
Will do most feedback of hand-ins
Henrik Bærbak Christensen

7. Henrik Bærbak Christensen
Learning Focus
Henrik Bærbak Christensen

8. Henrik Bærbak Christensen
Learning Goals
Learning goals from the studie ordning
Mål
Læringsmålet med kurset er, at den studerende kan designe, implementere og evaluere pålidelige, tilgængelige, og skalerbare arkitekturer for distribuerede systemer af moderat kompleksitet i en cloud computing sammenhæng 
Specifikt er målet at den studerende er i stand til at:
Designe distribuerede systemer af moderat kompleksitet ved hjælp af arkitektur patterns med henblik på at opnå specifikke kvalitetsattributter
Implementere distribuerede systemer ved hjælp af taktikker til opnåelse af pålidelighed, tilgængelighed, og skalerbarhed.
Idriftsætte og teste distribuerede systemer i virtualiserede miljøer og cloud miljøer
Anvende centrale begreber og teknikker indenfor datalagring af store datamængder
Henrik Bærbak Christensen

9. Henrik Bærbak Christensen
Learning Goals
Or paraphrasing…
Knowledge
Cloud Computing and supporting technologies
Architectures for Availability, Reliability, Performance
Skills
DevOps operational skills
Coding, configuration, deployment, monitoring
Architectural tactics implementation
Such as safe failure modes, redundancy, caching, …
Scientific process and information gathering
Systematic problem solving
Henrik Bærbak Christensen

10. … or From From ‘a server’ to ‘a lot of servers’
A 12+ grade solution of SkyCave will encompass around 20+ servers in the back tier
Henrik Bærbak Christensen

11. The Three Core Learning Goals
DevOps
Architectural Techniques
(Science Process)

12. DevOps Full stack developer Uber development
Do everything: db, code, UI, config, deploy, monitor, production
Uber development
08-12 I develop it
12-16 I deploy it
16-08 I monitor it
(pager at bed table!)
CloudArch work/exam is basically DevOps work! UI
Application Server
Team 1
Team 2
Database
Henrik Bærbak Christensen

13. Henrik Bærbak Christensen
DevOps
Charles Anderson: Docker
Henrik Bærbak Christensen

14. Architectural Tactics
Tactics and Patterns are
Tactic: Implementation technique to increase given quality attribute
Pattern: Solution to a common design problem
We will (of course) focus on solving
Availability issues
Testability issues
Scalability issues
Performance issues
But disregard
Usability
Security
Henrik Bærbak Christensen

15. Scientific Process
The only difference between screwing around and science is writing it down!
- Andy Savage / MythBusters
Apply Science in your work!
(Most likely, you will need what you’ve written down at the final individual exam gate…)
Henrik Bærbak Christensen

16. Detailed Record Keeping
Scientific Process
Observation
Observation
How does system behave?
Hypothesis
Improve/correct by doing X
Experiment
Execute
Conclusion
Hypothesis is
Detailed Record Keeping!
To avoid getting lost! To track progress! To be reproducible!
Detailed Record Keeping
Experiment
Hypothesis
TRUE:
Refine Hypo.
FALSE:
Alt. Hypo.
Finding
Theory
Henrik Bærbak Christensen

17. Example: Experiments Keep the diary/logbook at hand! Make notes!
Goal, hypothesis, experiment, conclude [loop]
Tool evaluation for Akhera
SonarQube setup for CloudArch Auto eval
Henrik Bærbak Christensen

18. Example: Guides (Conclusions)
Update the Cave Registration service
Setting fixed IPs on AUIT
Henrik Bærbak Christensen

19. Henrik Bærbak Christensen
A note
Detailed record keeping saves your sanity!
Christmas vacation: MQ update lead to total reinstall
Guides helped me reestablish full working environment
Extending Mongo DB disks
Involves repeating steps in three differently configured machines
And a wrong step may crash 4 TB data 
Henrik Bærbak Christensen

20. Henrik Bærbak Christensen
Learning Format
Henrik Bærbak Christensen

21. Henrik Bærbak Christensen
Learning Format
Lecrure Lab Seven Thursdays 14-18
Hour 1: Overview lecture
I present key topics
Hour 2-3-4: The Cave Lab session/Study Cafe
You code on SkyCave
I and TA act as consultants…
Henrik Bærbak Christensen

22. Henrik Bærbak Christensen
The Exam
Practical Exam
Henrik Bærbak Christensen

23. Henrik Bærbak Christensen
The Exam
It starts today…
No oral exam, no written exam, no multiple-choice, just executing software…
You are evaluated by the strength of your deployment, measured by its architectural quality attributes…
Functional correctness, availability, testability, modifiability, scalability, performance
Henrik Bærbak Christensen

24. Henrik Bærbak Christensen
More concrete
The exam consists of two components
Core component
A large set of exercises on SkyCave, solved in groups (2-3 pers)
Few are mandatory for a passing grade [marked by (*)]
Rest are pick as you like
Each valid solution means points (e.g. 20 points)
Hand-ins are either
Evaluated by Me/TA (testability/modifiability/ design time view)
Evaluated by Crunch3 (availability/ run time view)
(if it works out ok!)
Individual component
1½ hour individual practical defense
Practical exercise, solve small assignment/demo
Defends your achieved group score
Difficulty level adjusted to group score
Henrik Bærbak Christensen

25. SkyCave
The Exam

26. Henrik Bærbak Christensen
SkyCave
SkyCave is a
Massive multi-user online, exploration and creation experience with a bit of social networking
… with a horrible user interface
Inspired by the first adventure game, from 1972
”You are in a maze of twisty passages, all different”
SkyCave is functionally complete!
Exercises will revolve around back-tier stuff
‘Production hardening’
Increase availability and performance
Keeping testability and modifiability high
Henrik Bærbak Christensen

27. Henrik Bærbak Christensen
The Final Component
Individual grades versus group work?
1½ hour individual exam
Build upon last group SkyCave system
Bring you ‘detailed record keepings’ from your daily work
A) F…!!! We did that five weeks ago but how the h… did we do it??? Panic
B) Ok, we did that in the xxx exercise, let me find the detailed records of what we did and then apply them to this problem…
Individual exam in week 44.
Mon 24 Oct
Henrik Bærbak Christensen

28. … where we have not walked before
Boldly walk…
… where we have not walked before

29. Henrik Bærbak Christensen
Why we must talk…
Henrik Bærbak Christensen

30. A lot of things will go wrong and needs to be fixed!
Morale
A lot of things will go wrong and needs to be fixed!
We need you to give us feedback so we can fix stuff as we go along!
Henrik Bærbak Christensen

31. Henrik Bærbak Christensen
Our contract
We promise to guard you from our mistakes as best possible, fix problems as fast as possible
You need to promise us to tell us of problems!
We do not understand this exercise?
Most others will not either, and we must correct it
We have no clue as where to start on this exercise?
Ask us! Ask your fellow students! Google stack-overflow!
This score of our hand-in is completely wrong!!!
Tell us and explain why!
Henrik Bærbak Christensen

32. Henrik Bærbak Christensen
Frustration?
Developing software is frustrating !
Remember the TDD patterns
Break: what to do when tired? Take a break
Do over: what to do when in a blind alley? Restart
And talk to each other, search the web, talk to us!
And TimeBox your efforts – how to distribute your 15 hours weekly?
Software in production is frustrating!
What is working today, breaks down tomorrow
”shit happens in a connected world”
Henrik Bærbak Christensen