Devops AND
MICROApp architectureS
More than a choice of Technology
Marcus Ahnve
@mahnve
marcus.ahnve@valtech.se
About ME
● Playing agile coach
● Professional developer since 1996
● Polyglot programmer a.k.a web developer
Tldr;
● Agile methodologies require supporting technology to
reach their full potential
What is ...
Easy to implement
Applicable to all kinds of projects
Fully scalable
?
The Promise of Agile
What we forgot
Three Levels of Agility
Technology
Scrum
Management
TODAYS FOCUS
Technology
Scrum
Management
LOST XP Practices
TDD
Simple
Design
Refactoring
Continuous
Integration
Small
Releases
Lost Lean Ambitions
DEFER DECISIONS
Platforms
Platforms are oneway
deadend streets
Software lifecycle
Does not include Death
Who pays for a system that is hard to replace?
ask “How will
we replace it?”
Smaller parts
Implementation not that important
Communication however is
Split into smaller part
Login
Admin
Public
Follow the Stories and actors
Example
A B
C D
What Data To Send?
A B
C D
?
?
?
SOAP
A B
C D
B
B A
Self describing services
A B
What do you
want?
X, Y and Z
Here you go
XHTML
A B
GET
XHTML
FORM
POST
Hypermedia
Client Service
<service>
<...>
<link rel=”” href=”...” />
</service>
Fault tolerance
Login
Admin
PublicPublicPublic
Releasability
Login
Admin
Public
Scalability
Login
Admin
PublicPublicPublic
Splittability
Login Admin
Public
Login
Admin
Public
Simple vs. EASY
Time
Functionality
Simple vs. EASY
Time
Productivity
The next problem
MANUAL Deploys
It can get worseIt can get worse
The Tail is wagging the dog
The cost of late releases
DEVelopers who like operations
Operators who like development
DevOps
Server provisioning
should be repeatable
Tooling
DevOps
DevOps
Who is responsible?
Hardware
OS
Infrastructure
Application Logic
How to do it
How often can you deploy?
Weekly?
Daily?
HOURLY?
Deploys should not be Scary
How to change organizations
Use Real States
What used to be “Done” is now inventory
Agile should have
been adaptive
"Most people Will be on one
hyperproductive team in their life"
Thank you!
Marcus Ahnve
@mahnve
marcus.ahnve@valtech.se
Upcoming SlideShare
Loading in …5
×

Inspirationslunch: DevOps och mikroarkitekturer - Marcus Ahnve

751 views

Published on

Sedan agila metoder slog igenom på bred front för dryga tio år sedan har många företag radikalt förändrat sitt arbetssätt. Idag ses lättrörliga processer som en självklarhet där teknikutveckling är en kärnprocess. Det har dock visat sig svårt att uppnå löftena om hyperproduktiva team som till exempel Scrum utlovar. En viktig orsak till detta är att man inte har en teknik som stödjer en lättrörlig process.

I det här seminariumet förklarade Marcus Ahnve från Valtech översiktligt devops och mikroarkitekturer, två kärnprocesser för att åstadkomma en lättrörlig process, samt hur man kan skapa värde genom att använda dem.

Published in: Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
751
On SlideShare
0
From Embeds
0
Number of Embeds
168
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Inspirationslunch: DevOps och mikroarkitekturer - Marcus Ahnve

  1. 1. Devops AND MICROApp architectureS More than a choice of Technology Marcus Ahnve @mahnve marcus.ahnve@valtech.se
  2. 2. About ME ● Playing agile coach ● Professional developer since 1996 ● Polyglot programmer a.k.a web developer
  3. 3. Tldr; ● Agile methodologies require supporting technology to reach their full potential
  4. 4. What is ... Easy to implement Applicable to all kinds of projects Fully scalable ?
  5. 5. The Promise of Agile
  6. 6. What we forgot
  7. 7. Three Levels of Agility Technology Scrum Management
  8. 8. TODAYS FOCUS Technology Scrum Management
  9. 9. LOST XP Practices TDD Simple Design Refactoring Continuous Integration Small Releases
  10. 10. Lost Lean Ambitions DEFER DECISIONS
  11. 11. Platforms
  12. 12. Platforms are oneway deadend streets
  13. 13. Software lifecycle Does not include Death Who pays for a system that is hard to replace?
  14. 14. ask “How will we replace it?” Smaller parts Implementation not that important Communication however is
  15. 15. Split into smaller part Login Admin Public Follow the Stories and actors
  16. 16. Example A B C D
  17. 17. What Data To Send? A B C D ? ? ?
  18. 18. SOAP A B C D B B A
  19. 19. Self describing services A B What do you want? X, Y and Z Here you go
  20. 20. XHTML A B GET XHTML FORM POST
  21. 21. Hypermedia Client Service <service> <...> <link rel=”” href=”...” /> </service>
  22. 22. Fault tolerance Login Admin PublicPublicPublic
  23. 23. Releasability Login Admin Public
  24. 24. Scalability Login Admin PublicPublicPublic
  25. 25. Splittability Login Admin Public Login Admin Public
  26. 26. Simple vs. EASY Time Functionality
  27. 27. Simple vs. EASY Time Productivity
  28. 28. The next problem
  29. 29. MANUAL Deploys
  30. 30. It can get worseIt can get worse
  31. 31. The Tail is wagging the dog
  32. 32. The cost of late releases
  33. 33. DEVelopers who like operations Operators who like development DevOps
  34. 34. Server provisioning should be repeatable
  35. 35. Tooling DevOps DevOps
  36. 36. Who is responsible? Hardware OS Infrastructure Application Logic
  37. 37. How to do it
  38. 38. How often can you deploy? Weekly? Daily? HOURLY?
  39. 39. Deploys should not be Scary
  40. 40. How to change organizations
  41. 41. Use Real States What used to be “Done” is now inventory
  42. 42. Agile should have been adaptive
  43. 43. "Most people Will be on one hyperproductive team in their life"
  44. 44. Thank you! Marcus Ahnve @mahnve marcus.ahnve@valtech.se

×