Microservices and the future on Infrastructure
•Transferir como PPTX, PDF•
7 gostaram•2,187 visualizações
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Semelhante a Microservices and the future on Infrastructure
Semelhante a Microservices and the future on Infrastructure (20)
Mais de Pini Reznik
Mais de Pini Reznik (8)
Último
Último (20)
Microservices and the future on Infrastructure
- 1. Microservices and Future of Infrastructure Pini Reznik continuousdelivery.uglyduckling.nl
- 2. Evolution of IT Image courtesy of Docker Inc./ docker.io
- 3. Silod Application Architecture Image courtesy of martinfowler.com/articles/microservices.html
- 5. Architecture around Business Capabilities Image courtesy of martinfowler.com/articles/microservices.html
- 6. Principles • Smart endpoints and dumb pipes • Decentralized Governance • Design for Failure • Infrastructure Automation • Evolutionary Design • Decentralized Data Management
- 7. Decentralised Data Management Image courtesy of martinfowler.com/articles/microservices.html
- 8. Data Lakes Image courtesy of http://www.pwc.com/techforecast
- 9. Disadvantages ??? • Operational overhead • Highly skilled operations • Duplication Of Effort • Distributed System Complexity • Asynchronicity Is Difficult! • Testability Challenges My answer: Tough s***, building software is hard! http://highscalability.com/blog/2014/4/8/microservices-not-a-free-lunch.html
- 10. From Monolithic to Multi-Cloud
- 11. Network-centric Architecture Image courtesy of n-e-r-v-o-u-s.com
- 12. Future Challenges Image courtesy of n-e-r-v-o-u-s.com
- 13. Conway’s Law organizations which design systems ... are constrained to produce designs which are copies of the communication structures of these organizations
- 14. Network-centric Organizations Image courtesy of n-e-r-v-o-u-s.com
- 15. Antitude at Startup Weekend http://antitude.io/swams/
Notas do Editor
- Opening question: how many developers? Sys-admins? DevOps? Other?
- I would like to start with a bit of history 1995: Single HW server -> Well-Defined Middleware and OS -> Thick SW 2015: Variety of HW, clouds -> Middleware based on dozens/hundreds of 3rd party components -> Thin application Since 90s we learned how to reuse existing technologies and by that increase the speed of development of new features. But increase of reliance on growing number of components made the deployment process pain in the ass.
- Before we can answer the question about the future we need to address the two forces trying to be in balance. Application and Infrastructure performance. We see on-going optimisation of App followed by optimisation of Infra and then App again … When one of them is out of balance we see a new technological break through In the last year containers took this out of balance in favour on Infra enabling introduction of microservices
- If we look at IT systems at the last two decades we can see that these systems are moving from a monolithic architecture running on physical hardware to clusters of smaller services that are often served in a cloud. During the last 10 years we saw the physical hardware abstracted away to allow creation of clouds. the question is what will we see in the future?
- And if we want to do microservices well, we need to continue moving towards the network-centric organisational structures. Such networks already widely used in our world if you take all the companies into account. The next step for the companies doing microservices would be to introduce this within the organisation. Or maybe the other way around, you first change your organisation and as a result you get the microservices architecture.
- And if we want to do microservices well, we need to continue moving towards the network-centric organisational structures. Such networks already widely used in our world if you take all the companies into account. The next step for the companies doing microservices would be to introduce this within the organisation. Or maybe the other way around, you first change your organisation and as a result you get the microservices architecture.
- The Conway’s law suggests that we can only build software systems resembling our organisational structure. Or in other words – if you have four team for building a compiler you will get a 4 steps compiler. This is the reason for the creation of monolithic applications by a hierarchical development organisation and also the reason behind the DevOps movement. Organisational division between Dev and Ops is now forcing to take a side and either merge them to build a single app or clearly divide them to define a clear API
- And if we want to do microservices well, we need to continue moving towards the network-centric organisational structures. Such networks already widely used in our world if you take all the companies into account. The next step for the companies doing microservices would be to introduce this within the organisation. Or maybe the other way around, you first change your organisation and as a result you get the microservices architecture.