DevOps has multiple hats nowadays. In today session we will identify the main competencies that a DevOp shall have in 2020. For each competency, tools that can leverage our day to day activities will be presented from Azure or Microsoft ecosystem. My today session was about DevOps, focusing on the culture and how we shall behave to support the DevOps culture in combination with the powerful tooling that Microsoft is offering for us - Azure DevOps. Besides this, attendees were able to find information related to what are the 2020 trends from a DevOps perspective and what Romanian market understand by DevOps

1. The key thing to note is that legacy systems are only legacy because they’ve been successful enough to last this long.

2. legacy systems
successful
enough to last this long

3. Dreamer, Technology Enthusiast, Speaker, Trainer, People 1st, Microsoft Azure MVP, Crafter, Endava, Dreamer

5. Avoid Prepare
ManageSurvive

9. Loosely
coupled
Deployable
independently
High
maintainable
and testable
Organized on
top of
business
needs and
capabilities

10. Loosely
coupled
Deployable
independently
High
maintainable
and testable
Organized on
top of
business
needs and
capabilities

14. Event triggered
Ephemeral
No infrastructure to
manage
Pays per
execution

15. Event triggered
Ephemeral
No infrastructure to
manage
Pays per
execution
Writing a function that incorporates a business logic and deploy it

17. Execution Time
Technology Stack
Environment Scaling

18. Microservices Serverless

19. Microservices
• Short or long
requests
• Few seconds
• Long
execution
time
Serverless
• Short life
• Few seconds
• Under 300s

20. Microservices
• Short or long
requests
• Few
secconds
• Long
execution
time
Serverless
• Short life
• Few seconds
• Under 300s

21. Microservices
• Short or long
requests
• Few
secconds
• Long
execution
time
Serverless
• Short life
• Few seconds
• Under 300s

23. Microservices Serverless
Different
stacks
Limited tech
stacks
External
dependencies
Multiple
stacks
Legacy code
Legacy
dependencies

24. Microservices
• Cluster
• Nodes type
• Container OS
• OS Updates
• Stack patches
Serverless
• No
infrastructure
configuration
• Easy
configuration
• Focus on code
• Write and
deploy

25. Microservices
• Same
environment
• Isolated from
infrastructure
Serverless
• Environment
agnostic
• No
dependencies

26. Microservices
• Node spin-up latency
• Warm-up
Serverless
• Scale on the fly
• Fast warm-up
• Dynamic scaling
• No boundaries

28. Operating
system
Maintenance and
support
(e.g. operation
system updates,
security patches)
Monitoring of
the OS
Deployment
mechanism
App
Deployment
&
Configuration
Infrastructure
management

29. Need to use external
services to be able
to deliver the same
functionality
Overcome the
limitations of disk
space, RAM and
execution duration
Legacy
dependencies to
different stacks or
systems

30. Need to use external
services to be able to deliver
the same functionality
Overcome the limitations of
disk space, RAM and
execution duration
Legacy dependencies to
different stacks or systems
Operating
system
Maintenance and
support
Monitoring of
the OS
Deployment
mechanism
App
Deployment
&
Configuration
Infrastructure
management

33. Hybrid App
Microservices Serverless
Proxy
Emit Request

34. Hybrid App
Microservices Serverless
Proxy
Emit Request

35. Microservices
Personalization
Cart
Payment
Serverless
Authentication
Authorization
Image resize

36. Microservices
Personalization
Cart
Payment
Serverless
Authentication
Authorization
Image resize
Kubeless

38. Understand how to connect multiple microservices or
functions to fulfil a business requirement
Each service or collection of functions shall be seen as
individual projects with their own team, pipeline and lifetime
Middleware and internal communication

39. Understand how to connect multiple microservices or
functions to fulfil a business requirement
Each service or collection of functions shall be seen as
individual projects with their own team, pipeline and lifetime
Middleware and internal communication

40. Understand how to connect multiple microservices or
functions to fulfil a business requirement
Each service or collection of functions shall be seen as
individual projects with their own team, pipeline and lifetime
Middleware and internal communication

41. To sum up

42. s|f
divide
partitioning
replicate/local redundancy
sync data
consistency
Cost control
tools
Code sharing
versioning
Process teams
Select interface,
middleware and channel

44. Thank you!
@RaduVunvulea
vunvulearadu.blogspot.com
https://www.linkedin.com/in/raduvunvulea/
vunvulear@outlook.com