Downloaded 12 times
![[WSO2Con EU 2018] Enabling Agile Integration Teams](https://cdn.slidesharecdn.com/ss_thumbnails/wso2coneupzfkeynotenov2018olddonotuse1-181114085938-thumbnail.jpg?width=640&height=640&fit=bounds)
![[APIdays INTERFACE 2021] Now that we have K8s, can we stop re-inventing API p...](https://cdn.slidesharecdn.com/ss_thumbnails/apidaysk8platform-210708083659-thumbnail.jpg?width=640&height=640&fit=bounds)
![[WSO2Con EU 2017] Microservices for Enterprises](https://cdn.slidesharecdn.com/ss_thumbnails/buildingapragmaticmicroservicearchitecture-171108114640-thumbnail.jpg?width=640&height=640&fit=bounds)
Microevent
- 1. Microservices Lead Software Architect,Angelo Agatino Nicolosi September 2017
- 2. 11 Agenda What is a µservice? We wantit! How can we get it? How does it look like? How do we work with µservices? How do we secure µservices? Coding! Q&A About Final Q&A
- 3. 22 Agenda What is a µservice? We wantit! How can we get it? How does it look like? How do we work with µservices? How do we secure µservices? Coding! Q&A About Final Q&A <<
- 4. 33 About Angelo Agatino Nicolosi LeadSoftware Architect Digital Customer Experience Personal Banking IT Danske Bank DCX in numbers Around 150 employees 4 Locations - 3 Countries 10 customer facing applications 60K logons per hour 6K transfers per hour 3M + customers
- 5. 44 Agenda What is a µservice? We wantit! How can we get it? How does it look like? How do we work with µservices? How do we secure µservices? Coding! Q&A About Final Q&A
- 6. 55 What is aMicroservice? Microservices are small, autonomous services that work together. “ ”
- 7. 66 Small, independent andfocused on doing one thing well Gather together those things that change for the same reason, and separate those things that change for different reasons “ ” Single Responsibility Principle Robert C. Martin
- 8. 77 Small, independent andfocused on doing one thing well Gather together those things that change for the same reason, and separate those things that change for different reasons “ ” Single Responsibility Principle Robert C. Martin
- 9. 88 Why microservices? Becausewe need agility! The ability of an organization to sense environmental change and respond efficiently and effectively to that change. “ ” The ability of an organization to renew itself, adapt, change quickly, and succeed in a rapidly changing, ambiguous, turbulent environment “ ”
- 10.
- 11. 1010 Stop trying topredict what the business and technology will look like in the future Refocus resources and efforts in building a future-proof architecture.
- 12. 1111 Stop trying topredict what the business and technology will look like in the future Refocus resources and efforts in building a future-proof architecture.
- 13. 1212 Monolith Agility Simplicity ScalabilityPerformanceReliabilit y Deployment Testability
- 14. Where we are Microservices AgilitySimplicity ScalabilityPerformance Reliabilit y Deployment Testability
- 15.
- 16. 1515 Agenda What is a µservice? We wantit! How can we get it? How does it look like? How do we work with µservices? How do we secure µservices? Coding! Q&A About Final Q&A
- 17. 1616http://martinfowler.com/bliki/BoundedContext.html By subdomain Decompose yoursystem Anti-Corruption Layer
- 18. 1717 By business capability Decomposeyour system Feature A Feature B Feature C
- 19. 1818 Migrating from amonolith? The Thing
- 20. 1919 Migrating from amonolith? The Thing API Gateway
- 21. 2020 Migrating from amonolith? The Thing API Gateway MS
- 22. 2121 Migrating from amonolith? The Thing API Gateway MS MS
- 23. 2222 Migrating from amonolith? MS MS MS MS MSMS API Gateway
- 24. 2323 Migrating from amonolith? MS MS MS MS MSMS API Gateway The Strangler pattern
- 25. 2424 Microservice patterns -Packages Business Logic Business Logic Wiring 80% 20%
- 26. Application 1 Application2 Application N Application 1 Application 2 Application N Shared Functionality1 Shared Functionality3 Shared Functionality2 Outages because of changes Large regeression tests High Complexity Loosely coupled systems Isolated changes Contained regression tests Low complexity Microservice patterns - Packages
- 27. Microservice patterns -Packages
- 28. 2727 Microservice patterns –Zero-Share Architecture Don’t Repeat Your-self
- 29. 2828 Microservice patterns –Zero-Share Architecture Don’t Repeat Your-self Do Repeat If Needed, K? Why so DRY?
- 30. 2929 Microservice patterns –Zero-Share Architecture Project MS 1 Project MS 2 Project Shared Functionality Microservice patterns – Zero-Share Architecture MS1 MS2 Shared Projects
- 31. 3030 Microservice patterns –Zero-Share Architecture Project MS 1 Project MS 2 Microservice patterns – Zero-Share Architecture MS1 MS2 Shared Libraries Package
- 32. 3131 Microservice patterns –Zero-Share Architecture Project MS 1 Project MS 2 Microservice patterns – Zero-Share Architecture MS1 MS2 Shared Libraries Package Dependency Hell
- 33. 3232 Microservice patterns –Zero-Share Architecture Project MS 1 Project MS 2 Microservice patterns – Zero-Share Architecture Consolidate services Project MS X
- 34. 3333 Reactive Manifesto Producer Consumer Messagedriven Elastic Supervisor New Consumer Supervisor Consumer Consumer New Consumer New Consumer Workflow Processor Flow monitor Resiliant Responsive Microservice patterns – Self-healing systems
- 35. 3434 Agenda What is a µservice? We wantit! How can we get it? How does it look like? How do we work with µservices? How do we secure µservices? Coding! Q&A About Final Q&A
- 36. 3535 A microservice architecture MSMS MS MS MSMS API Gateway Independently Deployable Unit
- 37. 3636 A microservice architecture– The reporting microservice MS MS MS MS MSMS API Gateway R
- 38. 3737 A microservice architecture– The reporting microservice MS MS MS MS MSMS API Gateway R Thight-coupling!
- 39. 3838 API Gateway A microservicearchitecture – The reporting microservice MS MS MS MS MSMS API Gateway R God-Service!
- 40. 3939 A microservice architecture– The reporting microservice MS MS MS MS MSMS API Gateway R Sync-Pull (Slow)
- 41. 4040 Controller of business processmay roll back A microservice architecture – The reporting microservice MS MS MS MS MSMS API Gateway R Event-Driven The Saga pattern Eventual Consistency
- 42. 4141 Microservice patterns –Smart endpoints, dumb pipes MS MS MS MS MS MS
- 43. 4242 Microservice patterns –Smart endpoints, dumb pipes MS MS MS MS MS MS ESB
- 44. 4343 Microservice patterns –Smart endpoints, dumb pipes MS MS MS MS MS MS
- 45. 4444 Microservice patterns –Smart endpoints, dumb pipes Be conservative in what you do, be liberal in what you accept from others. “ ” Tolerant Reader Pattern John Postel
- 46. 4545 Microservice patterns –Complex queries AccountsTransactions API Gateway Account Balance 123456789 5678 DKK 098765432 678 DKK 1. Get all the accounts2. Get all transactions for each account and calculate balance Very complex application
- 47. 4646 Microservice patterns –Complex queries AccountsTransactions API Gateway Account Balance 123456789 5678 DKK 098765432 678 DKK New materialized view 1. Command (new payment) 3. Update materialized view 2. Emit event 4. Query CQRS
- 48. 4747 Microservice patterns –Complex queries AccountsTransactions API Gateway Event Store Event sourcing • Complete Rebuild • Temporal Query • Event Replay • Possibility of persisting state in memory
- 49. 4848 Microservice patterns –What happens when something breaks? AccountsTransactions API Gateway Circuit breaker Accounts Flow Monitor
- 50. 4949 Microservice patterns –What happens when something breaks? APIGateway MS MS MS MS MS MS MS MS MS MS MS MS MS MS Logging Monitoring Centralized Logging Centralized Monitoring
- 51. 5050 Agenda What is a µservice? We wantit! How can we get it? How does it look like? How do we work with µservices? How do we secure µservices? Coding! Q&A About Final Q&A
- 52. 5151 Agenda What is a µservice? We wantit! How can we get it? How does it look like? How do we work with µservices? How do we secure µservices? Coding! Q&A About Final Q&A
- 53. You need… RapidProvisioning
- 54. You need… Rapidand Safe Application Deployment
- 55. You need… Devopsculture
- 56. 5555 Agenda What is a µservice? We wantit! How can we get it? How does it look like? How do we work with µservices? How do we secure µservices? Coding! Q&A About Final Q&A
- 57. 5656 NIST Cyber SecurityFramework
- 58. 5757 • A compromiseof a single point often means compromise of the entire application or network • Authentication requirements are global in scope • Security is often difficult to tailor Monolithic AppSec vs Microservices AppSec The Thing • building and operating are well understood and a ‘known known’ • the architecture is often relatively simple • well-established existing culture and responsibilities around development, business and compliance, etc. MS MS MS MS • Single responsibility principle • exposed attack surface is typically reduced • services can be independently patched • easier to apply the principle of least privilege and service- specific tailored security • cultural changes may be required for successful operation (such as DevOps and DevOpsSec) • a good understanding of the overall system functionality is required • legacy systems are not easily adapted • complexity (at scale) breeds insecurity
- 59.
- 60. 5959 Practicalities: Build asecure edge Single point of entry
- 61. 6060 Practicalities: Do notallow unwanted network communication Single point of entry Microsegment of network
- 62. 6161 Practicalities: Use alwaysTLS and whenever possible Mutal Authentication over TLS Single point of entry Microsegment of network Mutual Auth over TLS
- 63. 6262 Practicalities: Use alwaysTLS and whenever possible Mutal Authentication over TLS Single point of entry Dynamic and Static Security Analysis Mutual Auth over TLS Check-in Build TestDeploy Microsegment of network
- 64. 6363 Practicalities: Use alwaysTLS and whenever possible Mutal Authentication over TLS Single point of entry Dynamic and Static Security Analysis Mutual Auth over TLS Check-in Build TestDeploy Microsegment of network
- 65. 6464 Centralize Logging andMonitoring in order to analyse data APIGateway MS MS MS MS MS MS MS MS MS MS MS MS MS MS Logging Monitoring Centralized Logging Centralized Monitoring
- 66. 6565 The Confused Deputyproblem APIGateway UserInf o AuthN 1. AuthN as Eve 2. Request Alice Information
- 67. 6666 JWT: Authorization indistributed systems
- 68. 6767 The Confused Deputyproblem APIGateway UserInf o AuthN AuthZ 1. AuthN as Eve 2. Request Alice Information JWT JWT
- 69. 6868 Agenda What is a µservice? We wantit! How can we get it? How does it look like? How do we work with µservices? How do we secure µservices? Coding! Q&A About Final Q&A
- 70.
- 71. 7070 Agenda What is a µservice? We wantit! How can we get it? How does it look like? How do we work with µservices? How do we secure µservices? Coding! Q&A About Final Q&A
- 72. 7171 https://dk.linkedin.com/in/anicolosi …any questions ?Don’t hesitate to contact me:
Editor's Notes
- #15 Make it better through tooling!
- #26 Wiring = RabbitMQ instead of ZeroMQ, Cassandra instead of SQL, and so on Results from our experience
- #35 Message driven: loose coupling, independence, grow with the business with no change to existing functionalities Elastic: scaling Resilient: faults do not scare us. Apply back pressure to ensure scaling will be always on time. Responsive: All this together creates a responsive system This is a self healing system and we can build this today.
- #54 Extra: A/B Testing, Canary releases, Blue/Green deployments
- #55 Extra: A/B Testing, Canary releases, Blue/Green deployments
- #56 Extra: A/B Testing, Canary releases, Blue/Green deployments