Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Tools and competences on DevOps for 2020

59 views

Published on

Tools and competences on DevOps for 2020

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Tools and competences on DevOps for 2020

  1. 1. The key thing to note is that legacy systems are only legacy because they’ve been successful enough to last this long.
  2. 2. legacy systems successful enough to last this long
  3. 3. Dreamer, Technology Enthusiast, Speaker, Trainer, People 1st, Microsoft Azure MVP, Crafter, Endava, Dreamer
  4. 4. Avoid Prepare ManageSurvive
  5. 5. Loosely coupled Deployable independently High maintainable and testable Organized on top of business needs and capabilities
  6. 6. Loosely coupled Deployable independently High maintainable and testable Organized on top of business needs and capabilities
  7. 7. Event triggered Ephemeral No infrastructure to manage Pays per execution
  8. 8. Event triggered Ephemeral No infrastructure to manage Pays per execution Writing a function that incorporates a business logic and deploy it
  9. 9. Execution Time Technology Stack Environment Scaling
  10. 10. Microservices Serverless
  11. 11. Microservices • Short or long requests • Few seconds • Long execution time Serverless • Short life • Few seconds • Under 300s
  12. 12. Microservices • Short or long requests • Few secconds • Long execution time Serverless • Short life • Few seconds • Under 300s
  13. 13. Microservices • Short or long requests • Few secconds • Long execution time Serverless • Short life • Few seconds • Under 300s
  14. 14. Microservices Serverless Different stacks Limited tech stacks External dependencies Multiple stacks Legacy code Legacy dependencies
  15. 15. Microservices • Cluster • Nodes type • Container OS • OS Updates • Stack patches Serverless • No infrastructure configuration • Easy configuration • Focus on code • Write and deploy
  16. 16. Microservices • Same environment • Isolated from infrastructure Serverless • Environment agnostic • No dependencies
  17. 17. Microservices • Node spin-up latency • Warm-up Serverless • Scale on the fly • Fast warm-up • Dynamic scaling • No boundaries
  18. 18. Operating system Maintenance and support (e.g. operation system updates, security patches) Monitoring of the OS Deployment mechanism App Deployment & Configuration Infrastructure management
  19. 19. 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
  20. 20. 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
  21. 21. Hybrid App Microservices Serverless Proxy Emit Request
  22. 22. Hybrid App Microservices Serverless Proxy Emit Request
  23. 23. Microservices Personalization Cart Payment Serverless Authentication Authorization Image resize
  24. 24. Microservices Personalization Cart Payment Serverless Authentication Authorization Image resize Kubeless
  25. 25. 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
  26. 26. 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
  27. 27. 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
  28. 28. To sum up
  29. 29. s|f divide partitioning replicate/local redundancy sync data consistency Cost control tools Code sharing versioning Process teams Select interface, middleware and channel
  30. 30. Thank you! @RaduVunvulea vunvulearadu.blogspot.com https://www.linkedin.com/in/raduvunvulea/ vunvulear@outlook.com

×