�ݺ�ߣshows by User: spnewman

�ݺ�ߣshows by User: spnewman / http://www.slideshare.net/images/logo.gif �ݺ�ߣshows by User: spnewman / Wed, 10 Jun 2020 14:13:08 GMT �ݺ�ߣShare feed for �ݺ�ߣshows by User: spnewman Hiding The Lead: Coupling, cohesion and microservices /slideshow/hiding-the-lead-coupling-cohesion-and-microservices/235344836 couplingcohesionandmicroservices-200610141308
The terms coupling and cohesion come from the world of structured programming, but they are also thrown about in the context of microservices. In this session, I look at the applicability of these terms to microservice architecture, and also do a deep dive into the different types of coupling to explore how ideas from the 1970s still have a lot of relevance to the types of systems we build today.]]>
The terms coupling and cohesion come from the world of structured programming, but they are also thrown about in the context of microservices. In this session, I look at the applicability of these terms to microservice architecture, and also do a deep dive into the different types of coupling to explore how ideas from the 1970s still have a lot of relevance to the types of systems we build today.]]> Wed, 10 Jun 2020 14:13:08 GMT /slideshow/hiding-the-lead-coupling-cohesion-and-microservices/235344836 spnewman@slideshare.net(spnewman) Hiding The Lead: Coupling, cohesion and microservices spnewman The terms coupling and cohesion come from the world of structured programming, but they are also thrown about in the context of microservices. In this session, I look at the applicability of these terms to microservice architecture, and also do a deep dive into the different types of coupling to explore how ideas from the 1970s still have a lot of relevance to the types of systems we build today. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/couplingcohesionandmicroservices-200610141308-thumbnail.jpg?width=120&height=120&fit=bounds" /> The terms coupling and cohesion come from the world of structured programming, but they are also thrown about in the context of microservices. In this session, I look at the applicability of these terms to microservice architecture, and also do a deep dive into the different types of coupling to explore how ideas from the 1970s still have a lot of relevance to the types of systems we build today.

Hiding The Lead: Coupling, cohesion and microservices from Sam Newman

]]> 747 0 https://cdn.slidesharecdn.com/ss_thumbnails/couplingcohesionandmicroservices-200610141308-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 It's a trap! /slideshow/its-a-trap-176000461/176000461 itsatrap-190925144944
The growth of the public cloud market is obvious to everyone. But what’s less well known is that enterprises are still growing the infrastructure and services they run for themselves. A common reason cited for the continual growth in private cloud rather than adopting public cloud offerings are concerns about being locked in to a specific vendor. This talk analyses the concerns about vendor lock-in with respect to the adoption of public cloud. Sam will share with you not only whether or not the concerns of lock-in have merit in the real world, but will also present some tools you can use to help your own thinking in this regard. ]]>
The growth of the public cloud market is obvious to everyone. But what’s less well known is that enterprises are still growing the infrastructure and services they run for themselves. A common reason cited for the continual growth in private cloud rather than adopting public cloud offerings are concerns about being locked in to a specific vendor. This talk analyses the concerns about vendor lock-in with respect to the adoption of public cloud. Sam will share with you not only whether or not the concerns of lock-in have merit in the real world, but will also present some tools you can use to help your own thinking in this regard. ]]> Wed, 25 Sep 2019 14:49:44 GMT /slideshow/its-a-trap-176000461/176000461 spnewman@slideshare.net(spnewman) It's a trap! spnewman The growth of the public cloud market is obvious to everyone. But what’s less well known is that enterprises are still growing the infrastructure and services they run for themselves. A common reason cited for the continual growth in private cloud rather than adopting public cloud offerings are concerns about being locked in to a specific vendor. This talk analyses the concerns about vendor lock-in with respect to the adoption of public cloud. Sam will share with you not only whether or not the concerns of lock-in have merit in the real world, but will also present some tools you can use to help your own thinking in this regard. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/itsatrap-190925144944-thumbnail.jpg?width=120&height=120&fit=bounds" /> The growth of the public cloud market is obvious to everyone. But what’s less well known is that enterprises are still growing the infrastructure and services they run for themselves. A common reason cited for the continual growth in private cloud rather than adopting public cloud offerings are concerns about being locked in to a specific vendor. This talk analyses the concerns about vendor lock-in with respect to the adoption of public cloud. Sam will share with you not only whether or not the concerns of lock-in have merit in the real world, but will also present some tools you can use to help your own thinking in this regard.

It's a trap! from Sam Newman

]]> 3021 2 https://cdn.slidesharecdn.com/ss_thumbnails/itsatrap-190925144944-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Rip It Up - The Microservice Organisation /slideshow/rip-it-up-the-microservice-organisation/168372940 ripitup-themicroserviceorganisation-v2-190902134621
Much of the attention for microservice architectures tends to focus on the technical aspects. But when you look into the details of organisations that have benefited from this approach you realise that there is more to getting the most out of microservices than lots of shinny new technology. In this talk, I show how organisational structures and team responsibilities may need to change if you want to get the most out of adopting a microservice architecture. Looking at traditional IT structures and comparing them with the modern autonomous delivery teams, he’ll explore how to get the organisation and architecture working well together. From Conway's law, to Dunbar's number and two pizza teams, you'll see how you can start to apply these ideas inside your own company.]]>
Much of the attention for microservice architectures tends to focus on the technical aspects. But when you look into the details of organisations that have benefited from this approach you realise that there is more to getting the most out of microservices than lots of shinny new technology. In this talk, I show how organisational structures and team responsibilities may need to change if you want to get the most out of adopting a microservice architecture. Looking at traditional IT structures and comparing them with the modern autonomous delivery teams, he’ll explore how to get the organisation and architecture working well together. From Conway's law, to Dunbar's number and two pizza teams, you'll see how you can start to apply these ideas inside your own company.]]> Mon, 02 Sep 2019 13:46:21 GMT /slideshow/rip-it-up-the-microservice-organisation/168372940 spnewman@slideshare.net(spnewman) Rip It Up - The Microservice Organisation spnewman Much of the attention for microservice architectures tends to focus on the technical aspects. But when you look into the details of organisations that have benefited from this approach you realise that there is more to getting the most out of microservices than lots of shinny new technology. In this talk, I show how organisational structures and team responsibilities may need to change if you want to get the most out of adopting a microservice architecture. Looking at traditional IT structures and comparing them with the modern autonomous delivery teams, he’ll explore how to get the organisation and architecture working well together. From Conway's law, to Dunbar's number and two pizza teams, you'll see how you can start to apply these ideas inside your own company. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/ripitup-themicroserviceorganisation-v2-190902134621-thumbnail.jpg?width=120&height=120&fit=bounds" /> Much of the attention for microservice architectures tends to focus on the technical aspects. But when you look into the details of organisations that have benefited from this approach you realise that there is more to getting the most out of microservices than lots of shinny new technology. In this talk, I show how organisational structures and team responsibilities may need to change if you want to get the most out of adopting a microservice architecture. Looking at traditional IT structures and comparing them with the modern autonomous delivery teams, he’ll explore how to get the organisation and architecture working well together. From Conway's law, to Dunbar's number and two pizza teams, you'll see how you can start to apply these ideas inside your own company.

Rip It Up - The Microservice Organisation from Sam Newman

]]> 783 1 https://cdn.slidesharecdn.com/ss_thumbnails/ripitup-themicroserviceorganisation-v2-190902134621-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 What Is This Cloud Native Thing Anyway? /slideshow/what-is-this-cloud-native-thing-anyway/97275310 whatiscloudnative-180516103531
Sam has found himself spending much of the past few years dealing with buzzword-heavy areas of technology, trying to come to terms with what it all means. From DevOps, to Microservices, serverless and now Cloud Native. So many of these terms mean different things to different people. In an effort to try and set us up with a common understanding of what Cloud Native is, Sam will be taking us on a whistle-stop tour through the history leading up to Cloud Native, and try and synthesise what it is, and why it’s important. From the emergence of public cloud to the all consuming hype around Kubernetes, from 12 factors to servlerless, Sam will pull all these strands together to help us understand how everything is related, everything is new, and everything is old all at the same time.]]>
Sam has found himself spending much of the past few years dealing with buzzword-heavy areas of technology, trying to come to terms with what it all means. From DevOps, to Microservices, serverless and now Cloud Native. So many of these terms mean different things to different people. In an effort to try and set us up with a common understanding of what Cloud Native is, Sam will be taking us on a whistle-stop tour through the history leading up to Cloud Native, and try and synthesise what it is, and why it’s important. From the emergence of public cloud to the all consuming hype around Kubernetes, from 12 factors to servlerless, Sam will pull all these strands together to help us understand how everything is related, everything is new, and everything is old all at the same time.]]> Wed, 16 May 2018 10:35:31 GMT /slideshow/what-is-this-cloud-native-thing-anyway/97275310 spnewman@slideshare.net(spnewman) What Is This Cloud Native Thing Anyway? spnewman Sam has found himself spending much of the past few years dealing with buzzword-heavy areas of technology, trying to come to terms with what it all means. From DevOps, to Microservices, serverless and now Cloud Native. So many of these terms mean different things to different people. In an effort to try and set us up with a common understanding of what Cloud Native is, Sam will be taking us on a whistle-stop tour through the history leading up to Cloud Native, and try and synthesise what it is, and why it’s important. From the emergence of public cloud to the all consuming hype around Kubernetes, from 12 factors to servlerless, Sam will pull all these strands together to help us understand how everything is related, everything is new, and everything is old all at the same time. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/whatiscloudnative-180516103531-thumbnail.jpg?width=120&height=120&fit=bounds" /> Sam has found himself spending much of the past few years dealing with buzzword-heavy areas of technology, trying to come to terms with what it all means. From DevOps, to Microservices, serverless and now Cloud Native. So many of these terms mean different things to different people. In an effort to try and set us up with a common understanding of what Cloud Native is, Sam will be taking us on a whistle-stop tour through the history leading up to Cloud Native, and try and synthesise what it is, and why it’s important. From the emergence of public cloud to the all consuming hype around Kubernetes, from 12 factors to servlerless, Sam will pull all these strands together to help us understand how everything is related, everything is new, and everything is old all at the same time.

What Is This Cloud Native Thing Anyway? from Sam Newman

]]> 3822 5 https://cdn.slidesharecdn.com/ss_thumbnails/whatiscloudnative-180516103531-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Confusion In The Land Of The Serverless - 90min Version /slideshow/confusion-in-the-land-of-the-serverless-90min-version/86856366 serverlessconfusion-90mins-180129150923
Note: This is an expanded (roughly 90min) form of my "Confusion in the land of the serverless". Serverless computing is the hot new thing. Like any hyped technology, it promises a lot. However questions remain around concept and implementation, especially when you start to compare how we’ve built systems in the past, and what serverless offers us now. Is Serverless the future, or just the emperor’s new clothes? This talk will very brie y introduce serverless computing, but will then dive into some of the questions that aren’t always asked in conjunction with this technology. By the end of the talk you should have a firm grasp of what serverless computing really can offer, cut through some of the hype, and get an understanding about where and how you can use it in your own organisations. ]]>
Note: This is an expanded (roughly 90min) form of my "Confusion in the land of the serverless". Serverless computing is the hot new thing. Like any hyped technology, it promises a lot. However questions remain around concept and implementation, especially when you start to compare how we’ve built systems in the past, and what serverless offers us now. Is Serverless the future, or just the emperor’s new clothes? This talk will very brie y introduce serverless computing, but will then dive into some of the questions that aren’t always asked in conjunction with this technology. By the end of the talk you should have a firm grasp of what serverless computing really can offer, cut through some of the hype, and get an understanding about where and how you can use it in your own organisations. ]]> Mon, 29 Jan 2018 15:09:23 GMT /slideshow/confusion-in-the-land-of-the-serverless-90min-version/86856366 spnewman@slideshare.net(spnewman) Confusion In The Land Of The Serverless - 90min Version spnewman Note: This is an expanded (roughly 90min) form of my "Confusion in the land of the serverless". Serverless computing is the hot new thing. Like any hyped technology, it promises a lot. However questions remain around concept and implementation, especially when you start to compare how we’ve built systems in the past, and what serverless offers us now. Is Serverless the future, or just the emperor’s new clothes? This talk will very brie y introduce serverless computing, but will then dive into some of the questions that aren’t always asked in conjunction with this technology. By the end of the talk you should have a firm grasp of what serverless computing really can offer, cut through some of the hype, and get an understanding about where and how you can use it in your own organisations. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/serverlessconfusion-90mins-180129150923-thumbnail.jpg?width=120&height=120&fit=bounds" /> Note: This is an expanded (roughly 90min) form of my "Confusion in the land of the serverless". Serverless computing is the hot new thing. Like any hyped technology, it promises a lot. However questions remain around concept and implementation, especially when you start to compare how we’ve built systems in the past, and what serverless offers us now. Is Serverless the future, or just the emperor’s new clothes? This talk will very brie y introduce serverless computing, but will then dive into some of the questions that aren’t always asked in conjunction with this technology. By the end of the talk you should have a firm grasp of what serverless computing really can offer, cut through some of the hype, and get an understanding about where and how you can use it in your own organisations.

Confusion In The Land Of The Serverless - 90min Version from Sam Newman

]]> 709 2 https://cdn.slidesharecdn.com/ss_thumbnails/serverlessconfusion-90mins-180129150923-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 AppSec and Microservices /slideshow/appsec-and-microservices-80894986/80894986 appsec-and-microservices-latest-oct2017-171017113003
Microservices give us many options. We can pick different technologies, mix synchronous and asynchronous integration techniques or embrace different deployment patterns. But they also give us different options for how we think about securing our systems. Done right, and microservices can increase the security of your vital data and processes. Done wrong, and you can increase the surface area of attack. This talk will discuss the importance of defence in depth, discussing the many different ways in which you can secure your fine-grained, distributed architectures. The audience should come away with a working framework for thinking about application security, and also understand how microservices can help (or hinder) building a secure system.]]>
Microservices give us many options. We can pick different technologies, mix synchronous and asynchronous integration techniques or embrace different deployment patterns. But they also give us different options for how we think about securing our systems. Done right, and microservices can increase the security of your vital data and processes. Done wrong, and you can increase the surface area of attack. This talk will discuss the importance of defence in depth, discussing the many different ways in which you can secure your fine-grained, distributed architectures. The audience should come away with a working framework for thinking about application security, and also understand how microservices can help (or hinder) building a secure system.]]> Tue, 17 Oct 2017 11:30:03 GMT /slideshow/appsec-and-microservices-80894986/80894986 spnewman@slideshare.net(spnewman) AppSec and Microservices spnewman Microservices give us many options. We can pick different technologies, mix synchronous and asynchronous integration techniques or embrace different deployment patterns. But they also give us different options for how we think about securing our systems. Done right, and microservices can increase the security of your vital data and processes. Done wrong, and you can increase the surface area of attack. This talk will discuss the importance of defence in depth, discussing the many different ways in which you can secure your fine-grained, distributed architectures. The audience should come away with a working framework for thinking about application security, and also understand how microservices can help (or hinder) building a secure system. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/appsec-and-microservices-latest-oct2017-171017113003-thumbnail.jpg?width=120&height=120&fit=bounds" /> Microservices give us many options. We can pick different technologies, mix synchronous and asynchronous integration techniques or embrace different deployment patterns. But they also give us different options for how we think about securing our systems. Done right, and microservices can increase the security of your vital data and processes. Done wrong, and you can increase the surface area of attack. This talk will discuss the importance of defence in depth, discussing the many different ways in which you can secure your fine-grained, distributed architectures. The audience should come away with a working framework for thinking about application security, and also understand how microservices can help (or hinder) building a secure system.

AppSec and Microservices from Sam Newman

]]> 550 2 https://cdn.slidesharecdn.com/ss_thumbnails/appsec-and-microservices-latest-oct2017-171017113003-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Feature Branches And Toggles In A Post-GitHub World /slideshow/feature-branches-and-toggles-in-a-postgithub-world/77438917 newbranching-50min-170702143951
During the evolution of the ideas behind Continuous Delivery, many of us came to the conclusion that having branches for features was not a good idea, and resulted in some fairly problematic issues. This was contentious at the time, with lots of discussion around whether or not feature toggles or feature branching was the right way forward. Roll on several years, and through Git and GitHub, branches are everywhere. Is this a problem? This talk re-examines the role of feature branches and feature toggles, and looks at them in the context of new research and technology to try and distill down some sensible lessons in a post-GitHub, but hopefully not post-factual, world.]]>
During the evolution of the ideas behind Continuous Delivery, many of us came to the conclusion that having branches for features was not a good idea, and resulted in some fairly problematic issues. This was contentious at the time, with lots of discussion around whether or not feature toggles or feature branching was the right way forward. Roll on several years, and through Git and GitHub, branches are everywhere. Is this a problem? This talk re-examines the role of feature branches and feature toggles, and looks at them in the context of new research and technology to try and distill down some sensible lessons in a post-GitHub, but hopefully not post-factual, world.]]> Sun, 02 Jul 2017 14:39:51 GMT /slideshow/feature-branches-and-toggles-in-a-postgithub-world/77438917 spnewman@slideshare.net(spnewman) Feature Branches And Toggles In A Post-GitHub World spnewman During the evolution of the ideas behind Continuous Delivery, many of us came to the conclusion that having branches for features was not a good idea, and resulted in some fairly problematic issues. This was contentious at the time, with lots of discussion around whether or not feature toggles or feature branching was the right way forward. Roll on several years, and through Git and GitHub, branches are everywhere. Is this a problem? This talk re-examines the role of feature branches and feature toggles, and looks at them in the context of new research and technology to try and distill down some sensible lessons in a post-GitHub, but hopefully not post-factual, world. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/newbranching-50min-170702143951-thumbnail.jpg?width=120&height=120&fit=bounds" /> During the evolution of the ideas behind Continuous Delivery, many of us came to the conclusion that having branches for features was not a good idea, and resulted in some fairly problematic issues. This was contentious at the time, with lots of discussion around whether or not feature toggles or feature branching was the right way forward. Roll on several years, and through Git and GitHub, branches are everywhere. Is this a problem? This talk re-examines the role of feature branches and feature toggles, and looks at them in the context of new research and technology to try and distill down some sensible lessons in a post-GitHub, but hopefully not post-factual, world.

Feature Branches And Toggles In A Post-GitHub World from Sam Newman

]]> 1211 3 https://cdn.slidesharecdn.com/ss_thumbnails/newbranching-50min-170702143951-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Confusion In The Land Of The Serverless /slideshow/confusion-in-the-land-of-the-serverless/77438170 serverlessconfusion-45min-170702135549
Serverless computing is the hot new thing. Like any hyped technology, it promises a lot. However questions remain around concept and implementation, especially when you start to compare how we've built systems in the past, and what serverless offers us now. Is Serverless the future, or just the emperor's new clothes? This talk will very briefly introduce serverless computing, but will then dive into some of the questions that aren't always asked in conjunction with this technology. Topics will include: How does your attitude to security change? Is it easier, or harder, to create reliable, resilient systems? Do patterns like Circuit breakers and connection pools make sense any more? Is vendor lock-in a problem? Is serverless computing only for microservice architectures? Which problems fit serverless computing? By the end of the talk you should have a firm grasp of what serverless computing really can offer, cut through some of the hype, and get an understanding about where and how you can use it in your own organisations.]]>
Serverless computing is the hot new thing. Like any hyped technology, it promises a lot. However questions remain around concept and implementation, especially when you start to compare how we've built systems in the past, and what serverless offers us now. Is Serverless the future, or just the emperor's new clothes? This talk will very briefly introduce serverless computing, but will then dive into some of the questions that aren't always asked in conjunction with this technology. Topics will include: How does your attitude to security change? Is it easier, or harder, to create reliable, resilient systems? Do patterns like Circuit breakers and connection pools make sense any more? Is vendor lock-in a problem? Is serverless computing only for microservice architectures? Which problems fit serverless computing? By the end of the talk you should have a firm grasp of what serverless computing really can offer, cut through some of the hype, and get an understanding about where and how you can use it in your own organisations.]]> Sun, 02 Jul 2017 13:55:49 GMT /slideshow/confusion-in-the-land-of-the-serverless/77438170 spnewman@slideshare.net(spnewman) Confusion In The Land Of The Serverless spnewman Serverless computing is the hot new thing. Like any hyped technology, it promises a lot. However questions remain around concept and implementation, especially when you start to compare how we've built systems in the past, and what serverless offers us now. Is Serverless the future, or just the emperor's new clothes? This talk will very briefly introduce serverless computing, but will then dive into some of the questions that aren't always asked in conjunction with this technology. Topics will include: How does your attitude to security change? Is it easier, or harder, to create reliable, resilient systems? Do patterns like Circuit breakers and connection pools make sense any more? Is vendor lock-in a problem? Is serverless computing only for microservice architectures? Which problems fit serverless computing? By the end of the talk you should have a firm grasp of what serverless computing really can offer, cut through some of the hype, and get an understanding about where and how you can use it in your own organisations. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/serverlessconfusion-45min-170702135549-thumbnail.jpg?width=120&height=120&fit=bounds" /> Serverless computing is the hot new thing. Like any hyped technology, it promises a lot. However questions remain around concept and implementation, especially when you start to compare how we've built systems in the past, and what serverless offers us now. Is Serverless the future, or just the emperor's new clothes? This talk will very briefly introduce serverless computing, but will then dive into some of the questions that aren't always asked in conjunction with this technology. Topics will include: How does your attitude to security change? Is it easier, or harder, to create reliable, resilient systems? Do patterns like Circuit breakers and connection pools make sense any more? Is vendor lock-in a problem? Is serverless computing only for microservice architectures? Which problems fit serverless computing? By the end of the talk you should have a firm grasp of what serverless computing really can offer, cut through some of the hype, and get an understanding about where and how you can use it in your own organisations.

Confusion In The Land Of The Serverless from Sam Newman

]]> 1343 4 https://cdn.slidesharecdn.com/ss_thumbnails/serverlessconfusion-45min-170702135549-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 AppSec & Microservices - Velocity 2016 /slideshow/appsec-microservices-velocity-2016/63395645 securing-microservicesvelocity-90mins-160623231002
This is the longer, 90 min version of my Microservices talk, as presented at Velocity 2016 in Santa Clara. Security is everyone’s job, even if you’re not a specialist. Microservices offer many options for securing your systems. Done right, microservices can increase the security of your vital data and processes. Done wrong, and they can increase the surface area of attack. Sam Newman explores the importance of defense in depth, discussing the many different ways in which you can secure your fine-grained, distributed architectures and outlining a model to show how developers can think about application security and how they can play their part. From there, Sam dives into the specific challenges in microservice architectures and explains how application security principles can be applied to these often much more complex application architectures. You’ll leave with a high-level framework for thinking about application security and tools that help with prevention, detection, response, and recovery, as well as the knowledge of what not to do when breaches happen.]]>
This is the longer, 90 min version of my Microservices talk, as presented at Velocity 2016 in Santa Clara. Security is everyone’s job, even if you’re not a specialist. Microservices offer many options for securing your systems. Done right, microservices can increase the security of your vital data and processes. Done wrong, and they can increase the surface area of attack. Sam Newman explores the importance of defense in depth, discussing the many different ways in which you can secure your fine-grained, distributed architectures and outlining a model to show how developers can think about application security and how they can play their part. From there, Sam dives into the specific challenges in microservice architectures and explains how application security principles can be applied to these often much more complex application architectures. You’ll leave with a high-level framework for thinking about application security and tools that help with prevention, detection, response, and recovery, as well as the knowledge of what not to do when breaches happen.]]> Thu, 23 Jun 2016 23:10:01 GMT /slideshow/appsec-microservices-velocity-2016/63395645 spnewman@slideshare.net(spnewman) AppSec & Microservices - Velocity 2016 spnewman This is the longer, 90 min version of my Microservices talk, as presented at Velocity 2016 in Santa Clara. Security is everyone’s job, even if you’re not a specialist. Microservices offer many options for securing your systems. Done right, microservices can increase the security of your vital data and processes. Done wrong, and they can increase the surface area of attack. Sam Newman explores the importance of defense in depth, discussing the many different ways in which you can secure your fine-grained, distributed architectures and outlining a model to show how developers can think about application security and how they can play their part. From there, Sam dives into the specific challenges in microservice architectures and explains how application security principles can be applied to these often much more complex application architectures. You’ll leave with a high-level framework for thinking about application security and tools that help with prevention, detection, response, and recovery, as well as the knowledge of what not to do when breaches happen. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/securing-microservicesvelocity-90mins-160623231002-thumbnail.jpg?width=120&height=120&fit=bounds" /> This is the longer, 90 min version of my Microservices talk, as presented at Velocity 2016 in Santa Clara. Security is everyone’s job, even if you’re not a specialist. Microservices offer many options for securing your systems. Done right, microservices can increase the security of your vital data and processes. Done wrong, and they can increase the surface area of attack. Sam Newman explores the importance of defense in depth, discussing the many different ways in which you can secure your fine-grained, distributed architectures and outlining a model to show how developers can think about application security and how they can play their part. From there, Sam dives into the specific challenges in microservice architectures and explains how application security principles can be applied to these often much more complex application architectures. You’ll leave with a high-level framework for thinking about application security and tools that help with prevention, detection, response, and recovery, as well as the knowledge of what not to do when breaches happen.

AppSec & Microservices - Velocity 2016 from Sam Newman

]]> 4655 7 https://cdn.slidesharecdn.com/ss_thumbnails/securing-microservicesvelocity-90mins-160623231002-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 AppSec And Microservices /slideshow/appsec-and-microservices/61218780 securing-microservices-160422042018
Microservices give us many options. We can pick different technologies, mix synchronous and asynchronous integration techniques or embrace different deployment patterns. But they also give us different options in how we think about securing our systems. Done right, and microservices can increase the security of your vital data and processes. Done wrong, and you can increase the surface area of attack. This talk will discuss the importance of defence in depth, discussing the many different ways in which you can secure your fine-grained, distributed architectures.]]>
Microservices give us many options. We can pick different technologies, mix synchronous and asynchronous integration techniques or embrace different deployment patterns. But they also give us different options in how we think about securing our systems. Done right, and microservices can increase the security of your vital data and processes. Done wrong, and you can increase the surface area of attack. This talk will discuss the importance of defence in depth, discussing the many different ways in which you can secure your fine-grained, distributed architectures.]]> Fri, 22 Apr 2016 04:20:18 GMT /slideshow/appsec-and-microservices/61218780 spnewman@slideshare.net(spnewman) AppSec And Microservices spnewman Microservices give us many options. We can pick different technologies, mix synchronous and asynchronous integration techniques or embrace different deployment patterns. But they also give us different options in how we think about securing our systems. Done right, and microservices can increase the security of your vital data and processes. Done wrong, and you can increase the surface area of attack. This talk will discuss the importance of defence in depth, discussing the many different ways in which you can secure your fine-grained, distributed architectures. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/securing-microservices-160422042018-thumbnail.jpg?width=120&height=120&fit=bounds" /> Microservices give us many options. We can pick different technologies, mix synchronous and asynchronous integration techniques or embrace different deployment patterns. But they also give us different options in how we think about securing our systems. Done right, and microservices can increase the security of your vital data and processes. Done wrong, and you can increase the surface area of attack. This talk will discuss the importance of defence in depth, discussing the many different ways in which you can secure your fine-grained, distributed architectures.

AppSec And Microservices from Sam Newman

]]> 4420 5 https://cdn.slidesharecdn.com/ss_thumbnails/securing-microservices-160422042018-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Deploying and Scaling Microservices /slideshow/deploying-and-scaling-microservices/56358942 deployingandscalingmicroservices-brisbane-151222052924
The challenges of managing many, smaller deployable services mean that what we need in terms of deployment platforms are very different to what was needed before. But few areas of software technology have been experiencing as much innovation and churn as the deployment options available for microservice architectures. From appication containers, to docker, to mesos and beyond, this talk will break apart the myriad challenges that can come from managing microservices at scale, and how to pick the right technologies for you.]]>
The challenges of managing many, smaller deployable services mean that what we need in terms of deployment platforms are very different to what was needed before. But few areas of software technology have been experiencing as much innovation and churn as the deployment options available for microservice architectures. From appication containers, to docker, to mesos and beyond, this talk will break apart the myriad challenges that can come from managing microservices at scale, and how to pick the right technologies for you.]]> Tue, 22 Dec 2015 05:29:24 GMT /slideshow/deploying-and-scaling-microservices/56358942 spnewman@slideshare.net(spnewman) Deploying and Scaling Microservices spnewman The challenges of managing many, smaller deployable services mean that what we need in terms of deployment platforms are very different to what was needed before. But few areas of software technology have been experiencing as much innovation and churn as the deployment options available for microservice architectures. From appication containers, to docker, to mesos and beyond, this talk will break apart the myriad challenges that can come from managing microservices at scale, and how to pick the right technologies for you. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/deployingandscalingmicroservices-brisbane-151222052924-thumbnail.jpg?width=120&height=120&fit=bounds" /> The challenges of managing many, smaller deployable services mean that what we need in terms of deployment platforms are very different to what was needed before. But few areas of software technology have been experiencing as much innovation and churn as the deployment options available for microservice architectures. From appication containers, to docker, to mesos and beyond, this talk will break apart the myriad challenges that can come from managing microservices at scale, and how to pick the right technologies for you.

Deploying and Scaling Microservices from Sam Newman

]]> 4759 7 https://cdn.slidesharecdn.com/ss_thumbnails/deployingandscalingmicroservices-brisbane-151222052924-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 BETA - Securing microservices /slideshow/beta-securing-microservices/54299831 securing-microservices-151023111758-lva1-app6892
This is an early version of my talk on microservices and application security. ]]>
This is an early version of my talk on microservices and application security. ]]> Fri, 23 Oct 2015 11:17:58 GMT /slideshow/beta-securing-microservices/54299831 spnewman@slideshare.net(spnewman) BETA - Securing microservices spnewman This is an early version of my talk on microservices and application security. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/securing-microservices-151023111758-lva1-app6892-thumbnail.jpg?width=120&height=120&fit=bounds" /> This is an early version of my talk on microservices and application security.

BETA - Securing microservices from Sam Newman

]]> 1610 4 https://cdn.slidesharecdn.com/ss_thumbnails/securing-microservices-151023111758-lva1-app6892-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 The Principles of Microservices /slideshow/principles-of-microservices-ndc-oslo/49554056 pkgbc8nyrdyui8qbrzir-signature-2c52b42fb5ec0dc8508f351772ffc719670e885bdcfacb5a030ef67d19637ee3-poli-150618130733-lva1-app6892
This talk is distillation of what makes microservices different from normal services. While this talk can serve as an introduction to microservices the real goal is to help tease out the key areas of what is a very broard topic. There has been lots of buzz around Microservices over the last year, but there has often been a lack of clarity as to what Microservices are, or how to implement them well. I've been working to distill down the principles of Microservices to help ensure that we don't just end up repeating the mistakes we made during the last 20 years of service oriented architecture. I'll talk about the history of where Microservices came from, what they are, the benefits and downsides, and the core principles to stick to do to them well. This is a shorter 60min version of the presentation]]>
This talk is distillation of what makes microservices different from normal services. While this talk can serve as an introduction to microservices the real goal is to help tease out the key areas of what is a very broard topic. There has been lots of buzz around Microservices over the last year, but there has often been a lack of clarity as to what Microservices are, or how to implement them well. I've been working to distill down the principles of Microservices to help ensure that we don't just end up repeating the mistakes we made during the last 20 years of service oriented architecture. I'll talk about the history of where Microservices came from, what they are, the benefits and downsides, and the core principles to stick to do to them well. This is a shorter 60min version of the presentation]]> Thu, 18 Jun 2015 13:07:33 GMT /slideshow/principles-of-microservices-ndc-oslo/49554056 spnewman@slideshare.net(spnewman) Principles of microservices ndc oslo spnewman This talk is distillation of what makes microservices different from normal services. While this talk can serve as an introduction to microservices the real goal is to help tease out the key areas of what is a very broard topic. There has been lots of buzz around Microservices over the last year, but there has often been a lack of clarity as to what Microservices are, or how to implement them well. I've been working to distill down the principles of Microservices to help ensure that we don't just end up repeating the mistakes we made during the last 20 years of service oriented architecture. I'll talk about the history of where Microservices came from, what they are, the benefits and downsides, and the core principles to stick to do to them well. This is a shorter 60min version of the presentation <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/pkgbc8nyrdyui8qbrzir-signature-2c52b42fb5ec0dc8508f351772ffc719670e885bdcfacb5a030ef67d19637ee3-poli-150618130733-lva1-app6892-thumbnail.jpg?width=120&height=120&fit=bounds" /> This talk is distillation of what makes microservices different from normal services. While this talk can serve as an introduction to microservices the real goal is to help tease out the key areas of what is a very broard topic. There has been lots of buzz around Microservices over the last year, but there has often been a lack of clarity as to what Microservices are, or how to implement them well. I've been working to distill down the principles of Microservices to help ensure that we don't just end up repeating the mistakes we made during the last 20 years of service oriented architecture. I'll talk about the history of where Microservices came from, what they are, the benefits and downsides, and the core principles to stick to do to them well. This is a shorter 60min version of the presentation

Principles of microservices ndc oslo from Sam Newman

]]> 8047 12 https://cdn.slidesharecdn.com/ss_thumbnails/pkgbc8nyrdyui8qbrzir-signature-2c52b42fb5ec0dc8508f351772ffc719670e885bdcfacb5a030ef67d19637ee3-poli-150618130733-lva1-app6892-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 The Principles of Microservices Velocity /slideshow/principles-of-microservices-velocity/48717500 bingxg7qtyotclgpllwn-signature-f8006b2679b47e3073159aa4a973f70d35593a08a1aa24c71cc711678269f2d6-poli-150528171401-lva1-app6892
Microservices are small services with independent lifecycles that work together. There is an underlying tension in that definition – how independent can you be when you have to be part of a whole? I’ve spent much of the last couple of years trying to understand how to find the right balance, and in this talk/tutorial I’ll be presenting the core seven principles that I think represent what makes microservices tick. After a brief introduction of what microservices are and why they are important, we’ll spend the bulk of the time looking at the principles themselves, wherever possible covering real-world examples and technology: - Modelled around business domain – using techniques from domain-driven design to find service boundaries leads to better team alignment and more stable service boundaries, avoiding expensive cross-service changes. - Culture of automation – all organisations that use microservices at scale have strong cultures of automation. We’ll look at some of their stories and think about which sort of automation is key. - Hide implementation details – how do you hide the detail inside each service to avoid coupling, and ensure each service retains its autonomous nature? - Decentralize all the things! – we have to push power down as far as we can, and this goes for both the system and organisational architecture. We’ll look at everything from autonomous self-contained teams and internal open source, to using choreographed systems to handle long-lived business transactions. - Deploy independently – this is all about being able to deploy safely. So we’ll cover everything from deployment models to consumer-driven contracts and the importance of separating deployment from release. - Isolate failure – just making a system distributed doesn’t make it more stable than a monolithic application. So what do you need to look for? - Highly observable – we need to understand the health of a single service, but also the whole ecosystem. How? In terms of learning outcomes, beginners will get a sense of what microservices are and what makes them different, whereas more experienced practitioners will get insight and practical advice into how to implement them.]]>
Microservices are small services with independent lifecycles that work together. There is an underlying tension in that definition – how independent can you be when you have to be part of a whole? I’ve spent much of the last couple of years trying to understand how to find the right balance, and in this talk/tutorial I’ll be presenting the core seven principles that I think represent what makes microservices tick. After a brief introduction of what microservices are and why they are important, we’ll spend the bulk of the time looking at the principles themselves, wherever possible covering real-world examples and technology: - Modelled around business domain – using techniques from domain-driven design to find service boundaries leads to better team alignment and more stable service boundaries, avoiding expensive cross-service changes. - Culture of automation – all organisations that use microservices at scale have strong cultures of automation. We’ll look at some of their stories and think about which sort of automation is key. - Hide implementation details – how do you hide the detail inside each service to avoid coupling, and ensure each service retains its autonomous nature? - Decentralize all the things! – we have to push power down as far as we can, and this goes for both the system and organisational architecture. We’ll look at everything from autonomous self-contained teams and internal open source, to using choreographed systems to handle long-lived business transactions. - Deploy independently – this is all about being able to deploy safely. So we’ll cover everything from deployment models to consumer-driven contracts and the importance of separating deployment from release. - Isolate failure – just making a system distributed doesn’t make it more stable than a monolithic application. So what do you need to look for? - Highly observable – we need to understand the health of a single service, but also the whole ecosystem. How? In terms of learning outcomes, beginners will get a sense of what microservices are and what makes them different, whereas more experienced practitioners will get insight and practical advice into how to implement them.]]> Thu, 28 May 2015 17:14:01 GMT /slideshow/principles-of-microservices-velocity/48717500 spnewman@slideshare.net(spnewman) Principles of microservices velocity spnewman Microservices are small services with independent lifecycles that work together. There is an underlying tension in that definition – how independent can you be when you have to be part of a whole? I’ve spent much of the last couple of years trying to understand how to find the right balance, and in this talk/tutorial I’ll be presenting the core seven principles that I think represent what makes microservices tick. After a brief introduction of what microservices are and why they are important, we’ll spend the bulk of the time looking at the principles themselves, wherever possible covering real-world examples and technology: - Modelled around business domain – using techniques from domain-driven design to find service boundaries leads to better team alignment and more stable service boundaries, avoiding expensive cross-service changes. - Culture of automation – all organisations that use microservices at scale have strong cultures of automation. We’ll look at some of their stories and think about which sort of automation is key. - Hide implementation details – how do you hide the detail inside each service to avoid coupling, and ensure each service retains its autonomous nature? - Decentralize all the things! – we have to push power down as far as we can, and this goes for both the system and organisational architecture. We’ll look at everything from autonomous self-contained teams and internal open source, to using choreographed systems to handle long-lived business transactions. - Deploy independently – this is all about being able to deploy safely. So we’ll cover everything from deployment models to consumer-driven contracts and the importance of separating deployment from release. - Isolate failure – just making a system distributed doesn’t make it more stable than a monolithic application. So what do you need to look for? - Highly observable – we need to understand the health of a single service, but also the whole ecosystem. How? In terms of learning outcomes, beginners will get a sense of what microservices are and what makes them different, whereas more experienced practitioners will get insight and practical advice into how to implement them. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/bingxg7qtyotclgpllwn-signature-f8006b2679b47e3073159aa4a973f70d35593a08a1aa24c71cc711678269f2d6-poli-150528171401-lva1-app6892-thumbnail.jpg?width=120&height=120&fit=bounds" /> Microservices are small services with independent lifecycles that work together. There is an underlying tension in that definition – how independent can you be when you have to be part of a whole? I’ve spent much of the last couple of years trying to understand how to find the right balance, and in this talk/tutorial I’ll be presenting the core seven principles that I think represent what makes microservices tick. After a brief introduction of what microservices are and why they are important, we’ll spend the bulk of the time looking at the principles themselves, wherever possible covering real-world examples and technology: - Modelled around business domain – using techniques from domain-driven design to find service boundaries leads to better team alignment and more stable service boundaries, avoiding expensive cross-service changes. - Culture of automation – all organisations that use microservices at scale have strong cultures of automation. We’ll look at some of their stories and think about which sort of automation is key. - Hide implementation details – how do you hide the detail inside each service to avoid coupling, and ensure each service retains its autonomous nature? - Decentralize all the things! – we have to push power down as far as we can, and this goes for both the system and organisational architecture. We’ll look at everything from autonomous self-contained teams and internal open source, to using choreographed systems to handle long-lived business transactions. - Deploy independently – this is all about being able to deploy safely. So we’ll cover everything from deployment models to consumer-driven contracts and the importance of separating deployment from release. - Isolate failure – just making a system distributed doesn’t make it more stable than a monolithic application. So what do you need to look for? - Highly observable – we need to understand the health of a single service, but also the whole ecosystem. How? In terms of learning outcomes, beginners will get a sense of what microservices are and what makes them different, whereas more experienced practitioners will get insight and practical advice into how to implement them.

Principles of microservices velocity from Sam Newman

]]> 106756 93 https://cdn.slidesharecdn.com/ss_thumbnails/bingxg7qtyotclgpllwn-signature-f8006b2679b47e3073159aa4a973f70d35593a08a1aa24c71cc711678269f2d6-poli-150528171401-lva1-app6892-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 QCon Sao Paulo Keynote - Microservices, an Unexpected Journey /slideshow/qcon-sao-paulo-keynote-microservices-an-unexpected-journey/46701453 qconkeynote-historyofmicroservices-150406192123-conversion-gate01
Microservices are the hot new thing, but where did they come from, and where are they going? This keynote will take you through the many origins of microservices. In it I’ll share with you some of the surprising influences and prior art that have shaped what they have become. By understanding where microservices architectures have their roots, we can learn from the past and avoid making the same mistakes – and we can also start to see where microservices will be going next. This talk was delivered as the keynote at QCon Sao Paulo in 2015.]]>
Microservices are the hot new thing, but where did they come from, and where are they going? This keynote will take you through the many origins of microservices. In it I’ll share with you some of the surprising influences and prior art that have shaped what they have become. By understanding where microservices architectures have their roots, we can learn from the past and avoid making the same mistakes – and we can also start to see where microservices will be going next. This talk was delivered as the keynote at QCon Sao Paulo in 2015.]]> Mon, 06 Apr 2015 19:21:22 GMT /slideshow/qcon-sao-paulo-keynote-microservices-an-unexpected-journey/46701453 spnewman@slideshare.net(spnewman) QCon Sao Paulo Keynote - Microservices, an Unexpected Journey spnewman Microservices are the hot new thing, but where did they come from, and where are they going? This keynote will take you through the many origins of microservices. In it I’ll share with you some of the surprising influences and prior art that have shaped what they have become. By understanding where microservices architectures have their roots, we can learn from the past and avoid making the same mistakes – and we can also start to see where microservices will be going next. This talk was delivered as the keynote at QCon Sao Paulo in 2015. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/qconkeynote-historyofmicroservices-150406192123-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds" /> Microservices are the hot new thing, but where did they come from, and where are they going? This keynote will take you through the many origins of microservices. In it I’ll share with you some of the surprising influences and prior art that have shaped what they have become. By understanding where microservices architectures have their roots, we can learn from the past and avoid making the same mistakes – and we can also start to see where microservices will be going next. This talk was delivered as the keynote at QCon Sao Paulo in 2015.

QCon Sao Paulo Keynote - Microservices, an Unexpected Journey from Sam Newman

]]> 2968 3 https://cdn.slidesharecdn.com/ss_thumbnails/qconkeynote-historyofmicroservices-150406192123-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Principles of microservices XP Days Ukraine /slideshow/principles-of-microservices-xp-days-ukraine/42853461 principlesofmicroservices-xpdaysukraine-141218205837-conversion-gate01
There has been lots of buzz around Microservices over the last year, but there has often been a lack of clarity as to what Microservices are, or how to implement them well. I've been working to distill down the principles of Microservices to help ensure that we don't just end up repeating the mistakes we made during the last 20 years of service oriented architecture.]]>
There has been lots of buzz around Microservices over the last year, but there has often been a lack of clarity as to what Microservices are, or how to implement them well. I've been working to distill down the principles of Microservices to help ensure that we don't just end up repeating the mistakes we made during the last 20 years of service oriented architecture.]]> Thu, 18 Dec 2014 20:58:36 GMT /slideshow/principles-of-microservices-xp-days-ukraine/42853461 spnewman@slideshare.net(spnewman) Principles of microservices XP Days Ukraine spnewman There has been lots of buzz around Microservices over the last year, but there has often been a lack of clarity as to what Microservices are, or how to implement them well. I've been working to distill down the principles of Microservices to help ensure that we don't just end up repeating the mistakes we made during the last 20 years of service oriented architecture. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/principlesofmicroservices-xpdaysukraine-141218205837-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds" /> There has been lots of buzz around Microservices over the last year, but there has often been a lack of clarity as to what Microservices are, or how to implement them well. I've been working to distill down the principles of Microservices to help ensure that we don't just end up repeating the mistakes we made during the last 20 years of service oriented architecture.

Principles of microservices XP Days Ukraine from Sam Newman

]]> 9540 4 https://cdn.slidesharecdn.com/ss_thumbnails/principlesofmicroservices-xpdaysukraine-141218205837-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Testing & deploying microservices - XP Days Ukraine 2014 /slideshow/testing-deploying-microservices-xp-days-ukraine-2014/42853435 testingdeployingmicroservices-xpdaysukraine-141218205702-conversion-gate02
]]>
]]> Thu, 18 Dec 2014 20:57:02 GMT /slideshow/testing-deploying-microservices-xp-days-ukraine-2014/42853435 spnewman@slideshare.net(spnewman) Testing & deploying microservices - XP Days Ukraine 2014 spnewman <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/testingdeployingmicroservices-xpdaysukraine-141218205702-conversion-gate02-thumbnail.jpg?width=120&height=120&fit=bounds" />

Testing & deploying microservices - XP Days Ukraine 2014 from Sam Newman

]]> 1579 3 https://cdn.slidesharecdn.com/ss_thumbnails/testingdeployingmicroservices-xpdaysukraine-141218205702-conversion-gate02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Principles of Microservices - NDC 2014 /slideshow/principles-of-microservices-ndc-2014/42310427 principlesofmicroservices-ndc-141203094050-conversion-gate01
There has been lots of buzz around Microservices over the last year, but there has often been a lack of clarity as to what Microservices are, or how to implement them well. I've been working to distill down the principles of Microservices to help ensure that we don't just end up repeating the mistakes we made during the last 20 years of service oriented architecture.]]>
There has been lots of buzz around Microservices over the last year, but there has often been a lack of clarity as to what Microservices are, or how to implement them well. I've been working to distill down the principles of Microservices to help ensure that we don't just end up repeating the mistakes we made during the last 20 years of service oriented architecture.]]> Wed, 03 Dec 2014 09:40:50 GMT /slideshow/principles-of-microservices-ndc-2014/42310427 spnewman@slideshare.net(spnewman) Principles of Microservices - NDC 2014 spnewman There has been lots of buzz around Microservices over the last year, but there has often been a lack of clarity as to what Microservices are, or how to implement them well. I've been working to distill down the principles of Microservices to help ensure that we don't just end up repeating the mistakes we made during the last 20 years of service oriented architecture. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/principlesofmicroservices-ndc-141203094050-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds" /> There has been lots of buzz around Microservices over the last year, but there has often been a lack of clarity as to what Microservices are, or how to implement them well. I've been working to distill down the principles of Microservices to help ensure that we don't just end up repeating the mistakes we made during the last 20 years of service oriented architecture.

Principles of Microservices - NDC 2014 from Sam Newman

]]> 58183 6 https://cdn.slidesharecdn.com/ss_thumbnails/principlesofmicroservices-ndc-141203094050-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Practical microservices - NDC 2014 /slideshow/practical-microservices-ndc-2014/42310122 practicalmicroservices-ndc-141203093412-conversion-gate02
Presented at NDC London, December 2014 Microservice architectures can lead to easier to change, more maintainable systems which can be more secure, performant and stable than previous designs. But what are the practical concerns associated with running more fine-grained systems, and what are the new things you’ll need to know if you want to embrace the power of smaller services without the new sources of complexity making your life a nightmare? This talk will delve deeper into the characteristics of well-behaved services, and will define some clear principles your services should follow. It will also discuss in more depth some of the challenges associated with managing and monitoring more complex distributed systems. We’ll discuss how you can design services to be more fault-tolerant, what technologies may exist in your own platform to get you started. We’ll end by giving some pointers as to when you should consider microservice architectures, and how you should go about introducing them in your own organisation.]]>
Presented at NDC London, December 2014 Microservice architectures can lead to easier to change, more maintainable systems which can be more secure, performant and stable than previous designs. But what are the practical concerns associated with running more fine-grained systems, and what are the new things you’ll need to know if you want to embrace the power of smaller services without the new sources of complexity making your life a nightmare? This talk will delve deeper into the characteristics of well-behaved services, and will define some clear principles your services should follow. It will also discuss in more depth some of the challenges associated with managing and monitoring more complex distributed systems. We’ll discuss how you can design services to be more fault-tolerant, what technologies may exist in your own platform to get you started. We’ll end by giving some pointers as to when you should consider microservice architectures, and how you should go about introducing them in your own organisation.]]> Wed, 03 Dec 2014 09:34:12 GMT /slideshow/practical-microservices-ndc-2014/42310122 spnewman@slideshare.net(spnewman) Practical microservices - NDC 2014 spnewman Presented at NDC London, December 2014 Microservice architectures can lead to easier to change, more maintainable systems which can be more secure, performant and stable than previous designs. But what are the practical concerns associated with running more fine-grained systems, and what are the new things you’ll need to know if you want to embrace the power of smaller services without the new sources of complexity making your life a nightmare? This talk will delve deeper into the characteristics of well-behaved services, and will define some clear principles your services should follow. It will also discuss in more depth some of the challenges associated with managing and monitoring more complex distributed systems. We’ll discuss how you can design services to be more fault-tolerant, what technologies may exist in your own platform to get you started. We’ll end by giving some pointers as to when you should consider microservice architectures, and how you should go about introducing them in your own organisation. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/practicalmicroservices-ndc-141203093412-conversion-gate02-thumbnail.jpg?width=120&height=120&fit=bounds" /> Presented at NDC London, December 2014 Microservice architectures can lead to easier to change, more maintainable systems which can be more secure, performant and stable than previous designs. But what are the practical concerns associated with running more fine-grained systems, and what are the new things you’ll need to know if you want to embrace the power of smaller services without the new sources of complexity making your life a nightmare? This talk will delve deeper into the characteristics of well-behaved services, and will define some clear principles your services should follow. It will also discuss in more depth some of the challenges associated with managing and monitoring more complex distributed systems. We’ll discuss how you can design services to be more fault-tolerant, what technologies may exist in your own platform to get you started. We’ll end by giving some pointers as to when you should consider microservice architectures, and how you should go about introducing them in your own organisation.

Practical microservices - NDC 2014 from Sam Newman

]]> 5672 4 https://cdn.slidesharecdn.com/ss_thumbnails/practicalmicroservices-ndc-141203093412-conversion-gate02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Practical microservices - javazone 2014 /slideshow/practical-microservices-javazone-2014/39186537 practicalmicroservices-javazone-140917052106-phpapp01
These are the slides I gave from my recent talk at Javazone. It's an update of my 'Practical Considerations For Microservices' talk. You can see the accompanying video here: http://vimeo.com/105751281]]>
These are the slides I gave from my recent talk at Javazone. It's an update of my 'Practical Considerations For Microservices' talk. You can see the accompanying video here: http://vimeo.com/105751281]]> Wed, 17 Sep 2014 05:21:06 GMT /slideshow/practical-microservices-javazone-2014/39186537 spnewman@slideshare.net(spnewman) Practical microservices - javazone 2014 spnewman These are the slides I gave from my recent talk at Javazone. It's an update of my 'Practical Considerations For Microservices' talk. You can see the accompanying video here: http://vimeo.com/105751281 <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/practicalmicroservices-javazone-140917052106-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" /> These are the slides I gave from my recent talk at Javazone. It's an update of my 'Practical Considerations For Microservices' talk. You can see the accompanying video here: http://vimeo.com/105751281

Practical microservices - javazone 2014 from Sam Newman

]]> 2725 2 https://cdn.slidesharecdn.com/ss_thumbnails/practicalmicroservices-javazone-140917052106-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 https://cdn.slidesharecdn.com/profile-photo-spnewman-48x48.jpg?cb=1605631289 Independent consultant, trainer, and speaker, specialising in microservices, continuous delivery and the cloud. Author of Building Microservices for O'Reilly. samnewman.io https://cdn.slidesharecdn.com/ss_thumbnails/couplingcohesionandmicroservices-200610141308-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/hiding-the-lead-coupling-cohesion-and-microservices/235344836 Hiding The Lead: Coupl... https://cdn.slidesharecdn.com/ss_thumbnails/itsatrap-190925144944-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/its-a-trap-176000461/176000461 It's a trap! https://cdn.slidesharecdn.com/ss_thumbnails/ripitup-themicroserviceorganisation-v2-190902134621-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/rip-it-up-the-microservice-organisation/168372940 Rip It Up - The Micro...