The document summarizes Adrian Cockcroft's experience giving talks about Netflix's approach to technology over time. It notes that initially people reacted skeptically, saying Netflix's approach was crazy and wouldn't work (2009-2010). Later, people said it could only work for large companies like Netflix (2011). By 2012, people said they wanted to adopt a similar approach but couldn't. The document outlines key lessons learned from Cockcroft's time at Netflix, including that speed wins in the marketplace and removing friction from product development helps enable faster innovation.
Opening talk at Monitorama, talks about the problems of monitoring, challenges of creating monitoring tools and why monitoring vendors keep getting disrupted. Ended with a discussion of simulation testing and serverless architectures - Monitorless.
QCon New York - Migrating to Cloud Native with MicroservicesAdrian Cockcroft
The document discusses Adrian Cockcroft's experience at Netflix and lessons learned about building cloud native systems with microservices. Some key points include:
- Typical reactions to Cockcroft's early talks about Netflix's architecture evolved from skepticism to admiration as the approach was proven at Netflix.
- Speed wins in the marketplace and removing friction from product development are important.
- Having high trust between teams with low processes and no handoffs enables faster innovation.
Software Architecture Conference - Monitoring Microservices - A ChallengeAdrian Cockcroft
The document discusses the challenges of monitoring microservices architectures. It notes that microservices are deployed much more frequently than traditional applications, sometimes in seconds or milliseconds. This rapid deployment rate requires monitoring tools that can measure and report metrics at an equally fast pace. It also explains that microservices architectures involve large numbers of loosely coupled services distributed across multiple regions, zones, and instances. Monitoring tools must be able to handle the scale and complexity of these distributed systems. Other challenges discussed include visualizing request flows, understanding common failure scenarios, and testing monitoring systems at a large scale. The document advocates for using simulations to model microservices architectures and stress test monitoring tools to help address these challenges.
This document summarizes a presentation on microservices architectures. It begins with an introduction to microservices and some of the benefits they provide like scalability and faster development. It then discusses challenges like configuration, tooling, discovery, routing, and observability. Examples are provided of microservices architectures at companies like Netflix, Twitter, and Gilt. Key aspects covered include programming languages, containerization, orchestration, and data stores.
A rough and researchy presentation where I tried out some new material in front of a local audience. Skipped the usual introduction and talked about some of the problems people run into when they do microservices and miss a few things. More refined version of this talk to be shown at O'Reilly Software Architecture Conference in New York in April.
Microservices: What's Missing - O'Reilly Software Architecture New YorkAdrian Cockcroft
The document discusses microservices architecture and related challenges. It provides advice on failure injection testing, versioning and routing, protocols and interfaces, timeouts and retries, managing inconsistency, denormalized data models, and cloud native monitoring of microservices. The author emphasizes designing services to fail independently, incremental versioning, avoiding unproductive work from retries, and dealing with the inherent inconsistency of distributed systems.
The document summarizes Adrian Cockcroft's experience giving talks about Netflix's approach to technology over time. It notes that initially people reacted skeptically, saying Netflix's approach was crazy and wouldn't work (2009-2010). Later, people said it could only work for large companies like Netflix (2011). By 2012, people said they wanted to adopt a similar approach but couldn't. The document outlines key lessons learned from Cockcroft's time at Netflix, including that speed wins in the marketplace and removing friction from product development helps enable faster innovation.
Opening talk at Monitorama, talks about the problems of monitoring, challenges of creating monitoring tools and why monitoring vendors keep getting disrupted. Ended with a discussion of simulation testing and serverless architectures - Monitorless.
QCon New York - Migrating to Cloud Native with MicroservicesAdrian Cockcroft
The document discusses Adrian Cockcroft's experience at Netflix and lessons learned about building cloud native systems with microservices. Some key points include:
- Typical reactions to Cockcroft's early talks about Netflix's architecture evolved from skepticism to admiration as the approach was proven at Netflix.
- Speed wins in the marketplace and removing friction from product development are important.
- Having high trust between teams with low processes and no handoffs enables faster innovation.
Software Architecture Conference - Monitoring Microservices - A ChallengeAdrian Cockcroft
The document discusses the challenges of monitoring microservices architectures. It notes that microservices are deployed much more frequently than traditional applications, sometimes in seconds or milliseconds. This rapid deployment rate requires monitoring tools that can measure and report metrics at an equally fast pace. It also explains that microservices architectures involve large numbers of loosely coupled services distributed across multiple regions, zones, and instances. Monitoring tools must be able to handle the scale and complexity of these distributed systems. Other challenges discussed include visualizing request flows, understanding common failure scenarios, and testing monitoring systems at a large scale. The document advocates for using simulations to model microservices architectures and stress test monitoring tools to help address these challenges.
This document summarizes a presentation on microservices architectures. It begins with an introduction to microservices and some of the benefits they provide like scalability and faster development. It then discusses challenges like configuration, tooling, discovery, routing, and observability. Examples are provided of microservices architectures at companies like Netflix, Twitter, and Gilt. Key aspects covered include programming languages, containerization, orchestration, and data stores.
A rough and researchy presentation where I tried out some new material in front of a local audience. Skipped the usual introduction and talked about some of the problems people run into when they do microservices and miss a few things. More refined version of this talk to be shown at O'Reilly Software Architecture Conference in New York in April.
Microservices: What's Missing - O'Reilly Software Architecture New YorkAdrian Cockcroft
The document discusses microservices architecture and related challenges. It provides advice on failure injection testing, versioning and routing, protocols and interfaces, timeouts and retries, managing inconsistency, denormalized data models, and cloud native monitoring of microservices. The author emphasizes designing services to fail independently, incremental versioning, avoiding unproductive work from retries, and dealing with the inherent inconsistency of distributed systems.
Businesses are speeding up development and automating operations to remain competitive and to get large organizations to scale. Project based monolithic application updates are replaced by product teams owning containerized microservices. This puts developers on call, responsible for pushing code to production, fixing it when it breaks, and managing the cost and security aspects of running their microservices. In this world operations skill-sets are either embedded in the microservices development teams, or building and operating API driven platforms. The platform automates stress testing, canary based deployment, penetration testing and enforces availability and security requirements. There are no meetings or tickets to file in the delivery process for updating a containerized microservice, which can happen many times a day, and takes seconds to complete. The role of site reliability engineering moves from firefighting and fixing outages to buiding tools for finding problems and routing those problems to the right developers. SREs manage the incident lifecycle for customer visible problems, and measure and publish availability metrics. This may sound futuristic but Werner Vogels described this as “You build it, you run it” in 2006.
Slides originally written in April 2013 for a private conference and internal use at Netflix. Publishing now since Heartbleed is another example of an epidemic failure mode.
Microservices Application Tracing Standards and Simulators - Adrians at OSCONAdrian Cockcroft
This document discusses distributed tracing standards and microservices simulations. It introduces OpenZipkin and OpenTracing as open source distributed tracing projects. It also discusses Pivot Tracing and the OpenTracing initiative to standardize instrumentation. The document proposes using a microservices simulator called Spigo to generate test data and visualize traces. It provides an example of defining a LAMP stack architecture in JSON to simulate with Spigo.
Sildes of an internal talk given at Twitter similar to a previous webinar for Redhat with the same title.
Speeding up development is a key concern, cloud and technology improvements like Docker speed up key steps that make continuous delivery possible. Breaking up the work into many separate microservices and datastores with stable APIs allows teams to make progress independently so that the organization scales. Monolithic apps are preferred for small projects, built by small teams and when very low latency and high efficiency is the primary requirement. Monitoring microservices is currently a challenge with solutions starting to emerge.
It's clear that Docker speeds up development and makes testing and deployment more efficient. As Docker moves into production new use cases and patterns are emerging that address availability and security concerns. With microservices, safety is part of the architecture that developers need to understand and build for. It's no longer good enough to wrap a firewall around an entire app when it goes to production, and have a cold standby in case it breaks.
GameDay - Achieving resilience through Chaos EngineeringDiUS
http://dius.com.au/resources/game-day/
Agility has brought us iterative software development, independent feature teams, nimble architectures and distributed, scalable infrastructure. But how do you maintain confidence in these systems in the face of this emergent complexity and fast paced change? The answer is to anticipate and practice failure!
In this session we explore GameDays, a collaborative exercise where teams safely introduce chaos into their systems, in order to make them better.
Summary of fast development and cloud native architecture along with cost optimization techniques. Presented as opening keynote at the Utility and Cloud Computing 2014 as part of the Cloud Control Workshop.
Software application development and delivery often involves multiple development, infrastructure and operations teams, each with their own preferred “tools of the trade” for building, testing and deploying code changes
For years, virtualization and cloud technologies have provided agile, on-demand infrastructure. The advent of Microservices promises even more agility– but what is required to take advantage of Microservices?
Join Electric Cloud CTO Anders Wallgren and Trace3 Principal Consultant - DevOps Marc Hornbeek as they discuss what is required to:
- Overcome culture and architecture challenges created when decomposing monolithic applications into Microservices-based applications.
- Coordinate integration, testing, monitoring, packaging, release approval and deployment of Microservices-based applications over elastic infrastructures
- Create a controlled and auditable delivery pipeline to support
Microservices-based application.
- Prepare for “future” applications, pipelines and patterns.
Discussion of how microservices are being applied across both web scale and enterprise/government use cases to help speed up development.
Video available at http://www.ustream.tv/recorded/86151804
This document discusses how PagerDuty can be used to alert teams when incidents occur and mobilize people to respond. However, long incidents and escalations still occur when it is time to take action. This is where integrating PagerDuty with Rundeck for runbook automation can help by automatically triggering Rundeck jobs at the start of PagerDuty incidents, during incidents using custom actions, and having Rundeck jobs update incident notes in PagerDuty. This allows teams to leverage existing automation tools and scripts through Rundeck to shorten incidents and reduce escalations.
Real-world Microservices: Lessons from the Front Line - Zhamak Delghani, Thou...Thoughtworks
Is Microservices gaining momentum? Looking at the interest in microservices in Australia at the moment, it is evident that this is a Service Oriented Architecture making waves.
I shared our insights and experiences to over 500 interested attendees at completely sold out YOW! nights events across Sydney, Brisbane and Melbourne. These talks revealed the core lessons ThoughWorkers have learnt building a variety of systems with Microservices architecture globally. They aimed to help viewers identify Microservices and their counterparts; guide them on where to use Microservices; and deliver a series of practices for technologists to build, test, deploy and operate a Microservices architecture.
The world of software architecture is excited and energised with the promises of a new Service Oriented Architecture, Microservices; rapid deployment, scalability, autonomy, and faster cycles of experimentation and innovation, and we are too!
Full slide deck for day long discussion of microservices topics. Why use microservices, what options exist and how to migrate to them and address common problems.
Cloud Native: Designing Change-tolerant Softwarecornelia davis
To see this presentation given live, go to http://bit.ly/DesignPatternsReplay
There is a special (discount) offer in there! :-)
Cloud-native applications are characterized by highly distributed topologies consisting of many relatively small components (yup, usually called microservices). But the thing that sets them apart even more from the previous generation of apps is that they are expected to function flawlessly even while the environment they are running in is constantly changing, or even failing.
All of this requires applying a new set of design patterns and practices and this webinar will introduce the most important ones. The Twelve Factor App (12factor.net) is a high-level articulation of some of these techniques that you may well have heard of, but its descriptions are relatively dense and the industry knowledge has evolved a fair bit since its publication.
Cornelia Davis, Senior Director of Technology at Pivotal, will share best practices for cloud-native applications and clear some of the mystery that shrouds 12-factor today. At the conclusion, attendees will understand what is needed for cloud-native applications, as well as why and how to deliver on those requirements.
In June 2017 at the Devops Enterprise Summit in London, while announcing the 2017 State of Devops Report with his esteemed colleagues, Jez Humble reveled that their studies showed that there was a strong correlation between high-functioning teams and the architecture of the software they are building, deploying and managing. In short - architecture matters to Devops.
In this talk Cornelia goes over a host of software architectural patterns and their relationship to some of the key goals of Devops - "higher throughput and higher quality and stability." Cloud native applications and cloud native data are both covered.
Rugged DevOps Will help you build ur cloudzJames Wickett
Gauntlt is a security testing tool that can be integrated into a continuous integration system. It runs automated attacks and penetration tests against code as part of the build process. Gauntlt attacks are written in an easy to read language to make security testing accessible to developers, operations staff, and security teams. This allows different teams to collaborate better and find vulnerabilities earlier in the development process.
Evolving to Cloud-Native - Nate Schutta (2/2)VMware Tanzu
The document discusses moving from monolithic applications to microservices and serverless architectures. It outlines the benefits of these approaches, such as improved developer productivity, scalability, and operational efficiencies. It also notes some challenges, such as increased complexity. The document provides guidance on planning the transition, including assessing applications, creating a roadmap, and piloting changes on select applications before full migration.
It’s Not Just Request/Response: Understanding Event-driven Microservicescornelia davis
The document discusses event-driven microservice architectures as an alternative to traditional request/response microservice patterns. It describes how each microservice can operate independently by broadcasting state changes as events, rather than making direct requests to other services. This allows services to have autonomous control loops and respond immediately to requests if they are already aware of the necessary data states. The approach derives the CQRS pattern of separating query and command handling. It also advocates for an event store to decouple services and act as a message bus to distribute events.
The document discusses concepts related to game day and chaos engineering on AWS. It provides examples of chaos experiments that can be conducted such as resource exhaustion, network unreliability, and datastore saturation. It also discusses tools for chaos engineering like Chaos Toolkit and Simian Army. The goal of game days and chaos engineering is to test systems resilience by simulating failures and disasters to gain insights on how to improve systems reliability.
This document provides an overview and summary of wireless fundamentals and history. It includes sections on wireless modems and their basic elements, how wireless communication works, different modulation techniques used, performance over distance, wireless networks and spectrum, industry standards, and proprietary technologies. The summary aims to explain at a high level the basics of wireless technology and its evolution over time.
Businesses are speeding up development and automating operations to remain competitive and to get large organizations to scale. Project based monolithic application updates are replaced by product teams owning containerized microservices. This puts developers on call, responsible for pushing code to production, fixing it when it breaks, and managing the cost and security aspects of running their microservices. In this world operations skill-sets are either embedded in the microservices development teams, or building and operating API driven platforms. The platform automates stress testing, canary based deployment, penetration testing and enforces availability and security requirements. There are no meetings or tickets to file in the delivery process for updating a containerized microservice, which can happen many times a day, and takes seconds to complete. The role of site reliability engineering moves from firefighting and fixing outages to buiding tools for finding problems and routing those problems to the right developers. SREs manage the incident lifecycle for customer visible problems, and measure and publish availability metrics. This may sound futuristic but Werner Vogels described this as “You build it, you run it” in 2006.
Slides originally written in April 2013 for a private conference and internal use at Netflix. Publishing now since Heartbleed is another example of an epidemic failure mode.
Microservices Application Tracing Standards and Simulators - Adrians at OSCONAdrian Cockcroft
This document discusses distributed tracing standards and microservices simulations. It introduces OpenZipkin and OpenTracing as open source distributed tracing projects. It also discusses Pivot Tracing and the OpenTracing initiative to standardize instrumentation. The document proposes using a microservices simulator called Spigo to generate test data and visualize traces. It provides an example of defining a LAMP stack architecture in JSON to simulate with Spigo.
Sildes of an internal talk given at Twitter similar to a previous webinar for Redhat with the same title.
Speeding up development is a key concern, cloud and technology improvements like Docker speed up key steps that make continuous delivery possible. Breaking up the work into many separate microservices and datastores with stable APIs allows teams to make progress independently so that the organization scales. Monolithic apps are preferred for small projects, built by small teams and when very low latency and high efficiency is the primary requirement. Monitoring microservices is currently a challenge with solutions starting to emerge.
It's clear that Docker speeds up development and makes testing and deployment more efficient. As Docker moves into production new use cases and patterns are emerging that address availability and security concerns. With microservices, safety is part of the architecture that developers need to understand and build for. It's no longer good enough to wrap a firewall around an entire app when it goes to production, and have a cold standby in case it breaks.
GameDay - Achieving resilience through Chaos EngineeringDiUS
http://dius.com.au/resources/game-day/
Agility has brought us iterative software development, independent feature teams, nimble architectures and distributed, scalable infrastructure. But how do you maintain confidence in these systems in the face of this emergent complexity and fast paced change? The answer is to anticipate and practice failure!
In this session we explore GameDays, a collaborative exercise where teams safely introduce chaos into their systems, in order to make them better.
Summary of fast development and cloud native architecture along with cost optimization techniques. Presented as opening keynote at the Utility and Cloud Computing 2014 as part of the Cloud Control Workshop.
Software application development and delivery often involves multiple development, infrastructure and operations teams, each with their own preferred “tools of the trade” for building, testing and deploying code changes
For years, virtualization and cloud technologies have provided agile, on-demand infrastructure. The advent of Microservices promises even more agility– but what is required to take advantage of Microservices?
Join Electric Cloud CTO Anders Wallgren and Trace3 Principal Consultant - DevOps Marc Hornbeek as they discuss what is required to:
- Overcome culture and architecture challenges created when decomposing monolithic applications into Microservices-based applications.
- Coordinate integration, testing, monitoring, packaging, release approval and deployment of Microservices-based applications over elastic infrastructures
- Create a controlled and auditable delivery pipeline to support
Microservices-based application.
- Prepare for “future” applications, pipelines and patterns.
Discussion of how microservices are being applied across both web scale and enterprise/government use cases to help speed up development.
Video available at http://www.ustream.tv/recorded/86151804
This document discusses how PagerDuty can be used to alert teams when incidents occur and mobilize people to respond. However, long incidents and escalations still occur when it is time to take action. This is where integrating PagerDuty with Rundeck for runbook automation can help by automatically triggering Rundeck jobs at the start of PagerDuty incidents, during incidents using custom actions, and having Rundeck jobs update incident notes in PagerDuty. This allows teams to leverage existing automation tools and scripts through Rundeck to shorten incidents and reduce escalations.
Real-world Microservices: Lessons from the Front Line - Zhamak Delghani, Thou...Thoughtworks
Is Microservices gaining momentum? Looking at the interest in microservices in Australia at the moment, it is evident that this is a Service Oriented Architecture making waves.
I shared our insights and experiences to over 500 interested attendees at completely sold out YOW! nights events across Sydney, Brisbane and Melbourne. These talks revealed the core lessons ThoughWorkers have learnt building a variety of systems with Microservices architecture globally. They aimed to help viewers identify Microservices and their counterparts; guide them on where to use Microservices; and deliver a series of practices for technologists to build, test, deploy and operate a Microservices architecture.
The world of software architecture is excited and energised with the promises of a new Service Oriented Architecture, Microservices; rapid deployment, scalability, autonomy, and faster cycles of experimentation and innovation, and we are too!
Full slide deck for day long discussion of microservices topics. Why use microservices, what options exist and how to migrate to them and address common problems.
Cloud Native: Designing Change-tolerant Softwarecornelia davis
To see this presentation given live, go to http://bit.ly/DesignPatternsReplay
There is a special (discount) offer in there! :-)
Cloud-native applications are characterized by highly distributed topologies consisting of many relatively small components (yup, usually called microservices). But the thing that sets them apart even more from the previous generation of apps is that they are expected to function flawlessly even while the environment they are running in is constantly changing, or even failing.
All of this requires applying a new set of design patterns and practices and this webinar will introduce the most important ones. The Twelve Factor App (12factor.net) is a high-level articulation of some of these techniques that you may well have heard of, but its descriptions are relatively dense and the industry knowledge has evolved a fair bit since its publication.
Cornelia Davis, Senior Director of Technology at Pivotal, will share best practices for cloud-native applications and clear some of the mystery that shrouds 12-factor today. At the conclusion, attendees will understand what is needed for cloud-native applications, as well as why and how to deliver on those requirements.
In June 2017 at the Devops Enterprise Summit in London, while announcing the 2017 State of Devops Report with his esteemed colleagues, Jez Humble reveled that their studies showed that there was a strong correlation between high-functioning teams and the architecture of the software they are building, deploying and managing. In short - architecture matters to Devops.
In this talk Cornelia goes over a host of software architectural patterns and their relationship to some of the key goals of Devops - "higher throughput and higher quality and stability." Cloud native applications and cloud native data are both covered.
Rugged DevOps Will help you build ur cloudzJames Wickett
Gauntlt is a security testing tool that can be integrated into a continuous integration system. It runs automated attacks and penetration tests against code as part of the build process. Gauntlt attacks are written in an easy to read language to make security testing accessible to developers, operations staff, and security teams. This allows different teams to collaborate better and find vulnerabilities earlier in the development process.
Evolving to Cloud-Native - Nate Schutta (2/2)VMware Tanzu
The document discusses moving from monolithic applications to microservices and serverless architectures. It outlines the benefits of these approaches, such as improved developer productivity, scalability, and operational efficiencies. It also notes some challenges, such as increased complexity. The document provides guidance on planning the transition, including assessing applications, creating a roadmap, and piloting changes on select applications before full migration.
It’s Not Just Request/Response: Understanding Event-driven Microservicescornelia davis
The document discusses event-driven microservice architectures as an alternative to traditional request/response microservice patterns. It describes how each microservice can operate independently by broadcasting state changes as events, rather than making direct requests to other services. This allows services to have autonomous control loops and respond immediately to requests if they are already aware of the necessary data states. The approach derives the CQRS pattern of separating query and command handling. It also advocates for an event store to decouple services and act as a message bus to distribute events.
The document discusses concepts related to game day and chaos engineering on AWS. It provides examples of chaos experiments that can be conducted such as resource exhaustion, network unreliability, and datastore saturation. It also discusses tools for chaos engineering like Chaos Toolkit and Simian Army. The goal of game days and chaos engineering is to test systems resilience by simulating failures and disasters to gain insights on how to improve systems reliability.
This document provides an overview and summary of wireless fundamentals and history. It includes sections on wireless modems and their basic elements, how wireless communication works, different modulation techniques used, performance over distance, wireless networks and spectrum, industry standards, and proprietary technologies. The summary aims to explain at a high level the basics of wireless technology and its evolution over time.
This document discusses the differences between product managers and product owners in agile development. It notes that product managers have a broader scope and are responsible for the overall product strategy, roadmap, and market success, while product owners focus intensely on individual agile teams. The document outlines common failure modes when these roles are not properly defined or staffed. It provides examples of small and large organizational structures and emphasizes that product owner roles must be fully staffed and selected thoughtfully based on each team's focus area.
Wi-Fi Doctor: Keeping your WLAN healthy - White Paper - The Future TrustTechnicolor
This document provides an overview of Wi-Fi networking technologies and some common issues experienced by Wi-Fi providers and users. It discusses how Wi-Fi has evolved from early wireless LAN connections to today's standards that support higher bandwidths and true mobility. It also summarizes some typical problems reported by help desks, such as device configuration issues and network connectivity problems, and different tools and methods that have been developed to detect and resolve Wi-Fi performance issues.
Pervasive Computing : You're Already Knee Deep In ItRob Manson
Presentation for Web Directions South 2009 on Pervasive Computing that outlines 5 key metrics that can be used to measure how pervasive computing is collapsing your sense of space.
These measurements can be used to define and refine specific elements of a business model to make your operating and distribution platforms more pervasive.
Conversational Architecture, CAVE Language, Data StewardshipLoren Davie
These are the slides from the presentation I gave at the Semiotics Web meetup group on Nov 1st 2014. In this talk I discussed the emergency of the ubiquitous Internet, how to discuss the design of contextual apps, and presented an approach to privacy concerns that are inherently connected.
The document provides lessons from iconic product managers throughout history, including Thomas J. Watson Jr., Henry Ford, Steve Jobs, Bill Gates, Ferdinand Porsche, and others. It discusses their philosophies and contributions, such as Watson's belief that good design is good business, Ford's views on quality and market saturation, Jobs' focus on deciding what not to do, and Gates' creation of new markets. Contemporary visionaries like Elon Musk, Larry Ellison, Jeff Bezos, and Larry Page are also examined for their product leadership, vision, and business strategies. Lesser known figures like Marissa Mayer, Jack Dorsey, and Thomas Kurian are highlighted for enforcing vision, identifying opportunities, and using their own products
Broadband world forum service delivery framework KPN presentationAlan Quayle
KPN's presentation at the Broadband World Forum 2010 at the session "Service Delivery Platform Evolution Revolution, Convolution, Amalgamation, Elimination or Virtualization."
KPN vision is to provide services to any device on any network at anytime. Eventually, it moves to "Everything-is-a-Service" model. From a user perspective consistent, on-par (Apple setting the bar) UX is one of the most important buying (and usage) motivation. Customer satisfaction efforts demand co-operation/partnership with others in the value chain, among which are (independent) developers, VARs, users, verticals, etc. Hence, services will encompass assets and capabilities from many different sources. Critical for this paradigm is fulfillment(including activation, registration, log-on), assurance and billing.
Evolution Of Hybrid TV Over The Top (Internet) TV and TV Everywhere Issue 2Alan Quayle
A reference text in the evolution of TV delivery. OTT (Internet) TV cannot be viewed as a silo, it must be considered in the wider evolution of the industry, across payTV, Free to Air, hybrid TV, TV everywhere, broadband, regulation, consumer trends and the interplay of actors across the TV ecosystem. If you would like a copy just email me at 'info (at) alanquayle.com'
The document provides an overview of key features of the IEEE 802.11ac wireless networking standard. It discusses improvements over 802.11n including support for wider channel bandwidth up to 160MHz, denser 256QAM modulation, up to 8 spatial streams, and multi-user MIMO. These enhancements enable dramatically higher speeds up to 3.47Gbps and support for more clients. The standard aims to provide gigabit speeds and reliable delivery of high quality video and other bandwidth intensive content to multiple devices simultaneously.
Pervasive/ubiquitous computing refers to embedding microprocessors in everyday objects to communicate information and connect devices. The goal is for connectivity to be unobtrusive and always available. Key aspects include wireless technologies, advanced electronics, and the internet connecting smart products. Challenges include creating seamless integration between technology and users.
Ambient Intelligence is a concept of future environment near us, with ubiquitous means hidden computing around us without electronics being visible...the future the way you everybody wants: ).
Wi-Fi ac (802.11ac) is the next generation Wi-Fi standard that promises gigabit speeds through improvements like wider channels and multi-user MIMO. There are four key drivers for its adoption: 1) increased internet usage like online video will strain current networks, 2) the rise of Wi-Fi only portable devices, 3) more smart TVs and devices connecting via Wi-Fi, and 4) current and future congestion problems as more devices use existing Wi-Fi bands. Wi-Fi ac aims to alleviate congestion by moving to the less crowded 5GHz spectrum exclusively, though this band may also become overloaded. It could allow for improved streaming of high quality video wirelessly throughout homes and
Docker, Containers, and the Future of Application Delivery document discusses:
- The challenges of running applications across different environments due to variations in stacks and hardware ("N x N" compatibility problem).
- How Docker addresses this by allowing applications and their dependencies to be packaged into standardized software containers that can run consistently across any infrastructure similar to how shipping containers standardized cargo transportation.
- The benefits of Docker for developers in building applications once and running them anywhere without dependency or compatibility issues, and for operations in simplifying configuration management and automation.
Ubiquitous computing is one of the most prodiously growing topic which will be covering all facets of life.In the course of ordinary activities, someone "using" ubiquitous computing engages many computational devices and systems simultaneously, and may not necessarily even be aware that they are doing so. This model is considered an advancement from the older desktop paradigm. More formally, ubiquitous computing is defined as "machines that fit the human environment instead of forcing humans to enter theirs".
I hear voices: Explorations of multidevice experiences with conversational as...Karen Kaushansky
This document discusses conversational assistants and their personas. It provides examples of the personas for Siri, Cortana, Google Now, Alexa and others. It also discusses developing a consistent persona to improve user experience and engagement. The document explores multi-device experiences and how assistants can shift between devices depending on context. It suggests assistants should have an awareness of capabilities across devices and apps to provide seamless experiences for users.
The key themes from the Broadband World Forum 2012 included discussions around software defined networks (SDN) and using it to virtualize telecom networks, allowing changes to be made more quickly. Big data analytics and using customer data to improve customer relationships was also a topic. Presentations also focused on maximizing bandwidth over existing copper networks and the state of fiber deployments worldwide. The home gateway concept was criticized for being out of touch with how people actually use devices and services in their homes today.
Three Consumer Market Trends that are Impacting Telecom Industry (2014)Marc Jadoul
The document discusses three consumer market trends impacting the telecom industry: 1) The linear TV model is being replaced as viewers demand more flexible viewing options on multiple devices. 2) Mobile usage and data consumption is growing rapidly, especially for video. 3) The "Internet of Things" is emerging, connecting billions of devices and generating huge revenues. The telecom industry must adapt networks and services to these changing trends of media consumption and connectivity of people and devices.
Keynote at Dockercon Europe Amsterdam Dec 4th, 2014.
Speeding up development with Docker.
Summary of some interesting web scale microservice architectures.
Please send me updates and corrections to the architecture summaries @adrianco
Thanks Adrian
Continuous delivery requires more that DevOps. It also requires one to think differently about product design, development & testing, and the overall structure of the organization. This presentation will help you understand what it takes and why one would want to deliver value to your customers multiple times each day. #CIC
Jeff "Cheezy" Morgan Ardita Karaj
DevOps and the cloud: all hail the (developer) king - Daniel Bryant, Steve PooleJAXLondon_Conference
1) The document discusses the rise of microservices and DevOps approaches in application development and deployment. It notes both the promises and challenges of these approaches, including increased complexity and the need for new tooling.
2) It describes lessons learned from early adoption of microservices, such as the problems that can arise from shared data stores and monolithic upgrades.
3) The document advocates for a "safety first" mindset with DevOps, emphasizing the importance of security, compliance, and understanding where data is located in cloud environments.
JAXLondon 2015 "DevOps and the Cloud: All Hail the (Developer) King"Daniel Bryant
Last year we talked about DevOps, what it was, why it was important and how to get started. Boy, was it scary. Now we’re wiser. More battle-scarred. The scale of the challenge for application writers exploiting cloud and DevOps is clearer, but so is the path forward. Understanding the DevOps approach is important but equally you must understand specific deployment technologies. How to exploit them and how they effect the design of applications. Whether creating simple applications or sophisticated microservice architectures many of the challenges are the same.
Presented at JAXLondon 2015 with Steve Poole
Delivering responsive redesign projects at large scale enterprises is hard, but not impossible with modern processes and methods.
Slides by Mike Kivikoski, UX Designer at Cantina
Microservices, Microfrontends and Feature TeamsGiulio Roggero
Quali sono le buone pratiche per progettare un'architettura in stile Microservices?
Come rendere evolutiva un'applicazione Frontend senza che invecchi dopo poco tempo?
Come organizzare più team che lavorano su una Piattaforma che ha centinaia di Microservices e decine di Frontend?
A queste tre domande risponderò durante il talk con esempi pratici e casi di vita vissuta.
Keeping Your DevOps Transformation From Crushing Your Ops Capacity Rundeck
Presentation by Damon Edwards, co-founder of Rundeck, at DevOps Enterprise Summit in San Francisco, November 13, 2017
See a Demo of Rundeck Enterprise :
https://www.rundeck.com/see-demo
--or--
Download Rundeck Open Source here:
https://rundeck.com/open-source
Connect:
Stack Overflow community: https://stackoverflow.com/questions/tagged/rundeck
Github: https://github.com/rundeck/rundeck/issues
Twitter: https://twitter.com/Rundeck
Facebook: https://www.facebook.com/RundeckInc/
LinkedIn: www.linkedin.com › company › rundeck-inc
Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/1mz2piq.
Damon Edwards explores the successful patterns - and damaging anti-patterns - observed at dozens of companies going through DevOps transformations. The main focus is on how Development teams can influence and take a leading role in the closing of the DevOps divide. Filmed at qconlondon.com.
Damon Edwards is the co-founder and managing partner of the DTO Solutions consulting group. Damon is also a frequent contributor to the Web Operations focused dev2ops.org blog, the co-host of the DevOps Cafe podcast series, and a co-author of the DevOps Cookbook from IT Revolution Press.
This document discusses the concepts of devops and how to transition an organization to a devops model. Some key points:
- Devops aims to break down silos between development and operations through culture, automation, measurement, and sharing.
- Traditional organizations have opposing goals between dev and ops that cause issues. Devops promotes a cross-functional team approach.
- Automating builds, testing, deployments, infrastructure management reduces risk and improves collaboration.
- Monitoring and metrics should be built in from the start so teams can learn from data and continuously improve.
- Culture change can be difficult but focusing on mindset, collaboration and incremental goals can help transition teams.
Innovate Better Through Machine data AnalyticsHal Rottenberg
This talk was presented at IP Expo Manchester in May, 2016. the themes discussed are:
- how does machine data relate to devops?
- how can tracking this data lead to better outcomes?
- what types of data are important to track?
AtlasCamp 2015: Game of Codes: The CI battleAtlassian
This document provides an overview of continuous integration (CI) practices at Atlassian, a software company. It discusses Atlassian's large build infrastructure that includes 11 Bamboo instances, 900 elastic agents, and over 20,000 build plans. It also describes some of the challenges of implementing CI at a large company, such as long test suites, plugin development, and integrating cloud services. The document emphasizes that CI requires changes to both processes and culture in order to be successful.
6 ways DevOps helped PrepSportswear move from monolith to microservicesDynatrace
Like a lot of online businesses today, PrepSportswear’s success is 100% dependent on the availability, scalability and performance of their digital online services. If the website is down, the business stops. They knew they had to transform their business from that of a retailer with a website to a high caliber IT company that sells products online.
In these webinar slides, Richard Dominguez, PrepSportswear’s Developer in Operations, shares their journey. They transformed from a team operating a monolithic app using waterfall development methodology on an old, hard to maintain code base, to a modern IT organization applying new practices from Agile development, DevOps and a Service-Oriented Architectural approach.
The Impact? PrepSportswear’s Most Successful Online Holiday Shopping Season in Company History! Join us to:
Learn how to identify if you are running a monolithic application that is dragging you down.
Get tips on hiring the right people to inject a DevOps cultural mindset into your organization.
Understand how to break the monolith into smaller pieces that support key lines of business.
Discover where to automate monitoring into your pipeline and platform.
Identify metrics for individual stakeholders (dev vs. test vs. business).
Go forward, celebrate, learn from, and repeat success!
Richard will be joined by Andreas Grabner, Performance Advocate at Dynatrace who will support why monitoring, application and end user metrics have to be a key part of your own transformation!
Richard Dominguez has 9+ years’ experience as both a System Analyst and Software Developer in Test. He has worked on many high profile projects in Microsoft such as Hyper-V, Windows 7 Client Performance, and Windows Phone Services. Richard now works at PrepSportswear as the company’s DevOps engineer. His responsibilities include site reliability, external synthetic testing, release management and overall site performance.
Andreas Grabner has 15+ years’ experience as an architect and developer in the Java and .NET space. In his current role, Andi works as an advocate for high performing applications in both the development and operations areas. He is a regular expert and contributor to large performance communities, a frequent speaker at technology conferences and regularly publishes articles blogs on blog.dynatrace.com
Building and Scaling High Performing Technology Organizations by Jez Humble a...Agile India
This document discusses building and scaling high-performing technology organizations through agile practices and DevOps. It touches on topics like creating value streams across projects, challenges with going agile at an enterprise level, the importance of principles like test-driven development, and building a culture of learning from failures. It also provides links to research on metrics like lead time for changes and deploy frequency that correlate with high performance.
This document discusses the principles of Lean UX. It begins with an introduction to where Lean UX comes from and its relationship to agile development. The core Lean UX process is then described as a cycle of stating desired outcomes, declaring assumptions, hypothesizing tests, designing experiments, making MVPs, getting feedback, and repeating. Key characteristics of Lean UX like small cross-functional teams and a bias towards making things to learn are also outlined. The document then dives deeper into how to approach continuous learning, writing assumptions and hypotheses, enabling making through MVPs, managing outcomes rather than outputs, and creating an organizational structure to support Lean UX.
Right on the heels of the Manifesto for Agile Software Development, a new movement with the moniker DevOps has further advanced software delivery. Although the Agile software development movement brought iterative and incremental concepts to our industry, in many organizations its reach was relegated to only the application development teams. In many cases, this moved the bottlenecks in organizations from application development to release management, IT operations and business program and portfolio management decision making. This local optimization leads to real world application of Agile software development being perceived as unsuccessful and increased probability of being thrown away for the comfort in the illusions of control of plan-driven approaches.
The promise of DevOps is to further improve our ability to make holistic optimizations from business to software delivery to operations and ultimately increase feedback into our business decision making processes. This promise involves the application of The Three Ways as described by Gene Kim: Flow, Feedback and Continuous Experimentation and Learning. Even for those that were able to take advantage of Agile software development we can not sit on our laurels. We must embrace continuous improvement in order to fend off the effects of “Software is Eating the World” as Marc Andreessen pronounced. DevOps provides a view on the culture, practices, tools and processes for how valuable software is delivered, operated and evolved to enable competitive advantage.
The document discusses how PayPal transitioned to a "lean engineering" model between 2011-2014 to better support rapid experimentation and continuous learning. It outlines four key principles of lean engineering: 1) Enable continuous learning through frequent delivery and prototyping. 2) Design for experimentation and frequent changes. 3) Democratize innovation by keeping teams small and using open source tools. 4) Use lean UX processes to give structure and feedback to agile development, treating users as the "brain" of engineering efforts. The document provides examples of how PayPal implemented these principles through techniques like continuous delivery, same-stack prototyping, open source development, and integrating lean UX processes with agile.
Speed up the development and increase the app quality are the keywords for success. Good points, not so simple to achieve….
eXtreme Programming (XP) is an agile discipline of software development based on values of simplicity, communication, feedback, courage, and respect. The software is built around the needs of the customer through a continuous release of working software and creating a learning loop that dramatically improves the quality of the final product.
Some XP practices, like TDD and Continuous Integration, can benefit of the support of software tools and frameworks. In this session we will see how XCTest and Xcode Continuous Integration can streamline the process of the iOS XP team.
Impact of CD, Clean Code, ... on Team PerformanceFredrik Wendt
The document discusses trends in software development for 2014, including clean code and software craftsmanship, DevOps, continuous delivery, Docker and Vagrant, scaling agile, and microservices. For each trend, it provides a brief description and discusses possible impacts and how teams can implement the trend to improve team performance and deliver value through shorter cycles, faster learning, and lower risk development.
The document discusses Capital One's transition from traditional software development practices to DevOps over the past 5 years. It describes how Capital One originally used mostly outsourced development, waterfall methodology, quarterly releases, and manual processes. A proof of concept project using agile tools like Hudson, Maven, and Nexus showed improvements from days to minutes for releases. This success was shared with other teams, and the executive leaders approved a DevOps strategy to move operations and security closer to development.
Teaching Elephants to Dance (and Fly!) A Developer's Journey to Digital Trans...Burr Sutter
We can be brilliant developers, but we won’t succeed—and won’t lead our organizations to succeed—without a new perspective (if you will) and new assumptions about the components of the “technology ecosystem” that are fundamentally critical to our success. This includes the operators, QA team, DBAs, security folks, and even the pure business contingent—in most cases, each of these individuals and groups plays a critical role in the success of what we create and give birth to as developers. What we do in isolation might be genius, but if we insulate ourselves—especially with arrogance—from these colleagues, neither our code nor our organizations will realize their full potential, and most will fail. The bottom line is that our old ways are no longer viable, and as the elite within our industry, we will be the leaders and heroes who discard old assumptions and adopt a new perspective in this exciting journey to digital transformation—where the impossible can become reality.
Just about all of my current technical content in one 364 slide mega-deck. Source files at https://github.com/adrianco/slides
Sections on:
Scene Setting
State of the Cloud
What Changes?
Product Processes
Microservices
State of the Art
Segmentation
What’s Missing?
Monitoring
Challenges
Migration
Response Times
Serverless
Lock-In
Teraservices
Wrap-Up
Historical view of process and channel oriented programming idioms: CSP 1978, Occam 1983, Pi-Calculus 1993 etc. How they map to Go and some examples of dynamic channel routing using Go to simulate peer-to-peer networks and microservices networks.
The document discusses the challenges of implementing effective network segmentation across modern distributed systems. It outlines several common mechanisms used for segmentation, such as VPC networks, security groups, Docker networking, and eBPF/Calico policies. However, it notes that individually these approaches face issues with scalability, coordination, and potential for misconfiguration. The document advocates for a hierarchical approach to segmentation that enforces consistent policies across layers from IAM roles to security groups to individual networks or segments. It raises open questions around coordinating policy specification and management across the different available mechanisms.
Microxchg Analyzing Response Time Distributions for MicroservicesAdrian Cockcroft
The document summarizes Adrian Cockcroft's work analyzing response time distributions for microservices. It discusses challenges in managing scale for microservice platforms and visualizing request flows across many services. It also introduces Spigo, a tool developed by Cockcroft that can simulate microservice architectures and interactions, generate traces, and collect response time histograms for analysis.
Updated slides for 2016 presentation on innovation in large organizations, why microservices and Docker can be useful, thoughts on monitoring for large complex architectures, some discussion of new topics - serverless architectures AWS Lambda and teraservices.
This document summarizes trends in cloud and container ecosystems observed by Adrian Cockcroft in November 2015. It notes rapid adoption and evolution of container technologies like Docker. Standards bodies are emerging around container orchestration. Cloud ecosystems like AWS, Azure, and GCE continue expanding globally while new players like DigitalOcean see strong growth. SaaS investment is growing fastest in areas like application performance management, ERP/accounting, and sales/marketing tools. Serverless architectures and "teraservices" using huge amounts of memory are trends to watch in 2016.
Gluecon Monitoring Microservices and Containers: A ChallengeAdrian Cockcroft
This document discusses the challenges of monitoring microservices and containers. It provides six rules for effective monitoring: 1) spend more time on analysis than data collection, 2) reduce latency of key metrics to under 10 seconds, 3) validate measurement accuracy, 4) make monitoring more available than services monitored, 5) optimize for distributed cloud-native applications, 6) fit metrics to models to understand relationships. It also examines models for infrastructure, flow, and ownership and discusses speed, scale, failures, and testing challenges with microservices.
This document discusses strategies for optimizing cloud costs using cloud native architectures. It provides examples of how Netflix optimized costs by rapidly experimenting in the cloud without capacity planning. It then outlines several approaches to reduce cloud costs including turning off idle resources, rightsizing instances, using auto-scaling, mixing reserved and on-demand instances, consolidating accounts, and expecting price reductions over time. Combining these approaches could potentially reduce costs by over 90% compared to traditional architectures over three years.
Monitorama - Please, no more Minutes, Milliseconds, Monoliths or Monitoring T...Adrian Cockcroft
Monitorama opening keynote talk on the challenges of Monitoring in a world where we need to deal with continuous delivery, cloud, and automated control feedback loops.
Hack Kid Con - Learn to be a Data Scientist for $1Adrian Cockcroft
Attempt to inspire some kids to pay attention in Math and Science classes so they can get a good job and help fill the skills gap in the years to come.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
Best 20 SEO Techniques To Improve Website Visibility In SERPPixlogix Infotech
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
Dr. Sean Tan, Head of Data Science, Changi Airport Group
Discover how Changi Airport Group (CAG) leverages graph technologies and generative AI to revolutionize their search capabilities. This session delves into the unique search needs of CAG’s diverse passengers and customers, showcasing how graph data structures enhance the accuracy and relevance of AI-generated search results, mitigating the risk of “hallucinations” and improving the overall customer journey.
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024Neo4j
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
Communications Mining Series - Zero to Hero - Session 1DianaGray10
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!SOFTTECHHUB
As the digital landscape continually evolves, operating systems play a critical role in shaping user experiences and productivity. The launch of Nitrux Linux 3.5.0 marks a significant milestone, offering a robust alternative to traditional systems such as Windows 11. This article delves into the essence of Nitrux Linux 3.5.0, exploring its unique features, advantages, and how it stands as a compelling choice for both casual users and tech enthusiasts.
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
Pushing the limits of ePRTC: 100ns holdover for 100 daysAdtran
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
4. Typical reactions to my Netflix talks…
“You guys are
crazy! Can’t
believe it”
– 2009
5. Typical reactions to my Netflix talks…
“You guys are
crazy! Can’t
believe it”
– 2009
“What Netflix is doing
won’t work”
– 2010
6. Typical reactions to my Netflix talks…
“You guys are
crazy! Can’t
believe it”
– 2009
“What Netflix is doing
won’t work”
– 2010 It only works for
‘Unicorns’ like
Netflix”
– 2011
7. Typical reactions to my Netflix talks…
“You guys are
crazy! Can’t
believe it”
– 2009
“What Netflix is doing
won’t work”
– 2010 It only works for
‘Unicorns’ like
Netflix”
– 2011
“We’d like to do
that but can’t”
– 2012
8. Typical reactions to my Netflix talks…
“You guys are
crazy! Can’t
believe it”
– 2009
“What Netflix is doing
won’t work”
– 2010 It only works for
‘Unicorns’ like
Netflix”
– 2011
“We’d like to do
that but can’t”
– 2012
“We’re on our way using
Netflix OSS code”
– 2013
10. What I learned from my time at Netflix
•Speed wins in the marketplace
11. What I learned from my time at Netflix
•Speed wins in the marketplace
•Remove friction from product development
12. What I learned from my time at Netflix
•Speed wins in the marketplace
•Remove friction from product development
•High trust, low process, no hand-offs between teams
13. What I learned from my time at Netflix
•Speed wins in the marketplace
•Remove friction from product development
•High trust, low process, no hand-offs between teams
•Freedom and responsibility culture
14. What I learned from my time at Netflix
•Speed wins in the marketplace
•Remove friction from product development
•High trust, low process, no hand-offs between teams
•Freedom and responsibility culture
•Don’t do your own undifferentiated heavy lifting
15. What I learned from my time at Netflix
•Speed wins in the marketplace
•Remove friction from product development
•High trust, low process, no hand-offs between teams
•Freedom and responsibility culture
•Don’t do your own undifferentiated heavy lifting
•Use simple patterns automated by tooling
16. What I learned from my time at Netflix
•Speed wins in the marketplace
•Remove friction from product development
•High trust, low process, no hand-offs between teams
•Freedom and responsibility culture
•Don’t do your own undifferentiated heavy lifting
•Use simple patterns automated by tooling
•Self service cloud makes impossible things instant
20. Cloud Adoption
@adrianco’s
new job at the
intersection
of cloud and
Enterprise IT
2009 2014
%*&!”
By Simon Wardley http://enterpriseitadoption.com/
21. This is the year that
Enterprises finally
embraced cloud.
31. Land grab
opportunity Competitive
Observe
Orient
Decide
Act
Move
Customer Pain
Point
Measure
Customers
Continuous
Delivery
32. Land grab
opportunity Competitive
Observe
Orient
Decide
Act
Move
Customer Pain
Point
INNOVATION
Measure
Customers
Continuous
Delivery
33. Land grab
opportunity Competitive
Observe
Orient
Decide
Act
Move
Customer Pain
Point
Analysis
Model
Hypotheses
INNOVATION
Measure
Customers
Continuous
Delivery
34. Land grab
opportunity Competitive
Observe
Orient
Decide
Act
Move
Customer Pain
Point
Analysis
BIG DATA
Model
Hypotheses
INNOVATION
Measure
Customers
Continuous
Delivery
35. Land grab
opportunity Competitive
Observe
Orient
Decide
Act
Move
Customer Pain
Point
Analysis
BIG DATA
Plan Response
JFDI
Share Plans
Model
Hypotheses
INNOVATION
Measure
Customers
Continuous
Delivery
36. Land grab
opportunity Competitive
Observe
Orient
Decide
Act
Move
Customer Pain
Point
Analysis
BIG DATA
Plan Response
JFDI
Share Plans
Model
Hypotheses
INNOVATION
CULTURE
Measure
Customers
Continuous
Delivery
37. Land grab
opportunity Competitive
Observe
Orient
Decide
Act
Move
Customer Pain
Point
Analysis
BIG DATA
Plan Response
JFDI
Share Plans
Launch AB
Test
Automatic
Deploy
Incremental
Features
Model
Hypotheses
INNOVATION
CULTURE
Measure
Customers
Continuous
Delivery
38. Land grab
opportunity Competitive
Observe
Orient
Decide
Measure
Customers
Act
Move
Customer Pain
Point
Analysis
BIG DATA
Plan Response
JFDI
Share Plans
Launch AB
Test
Automatic
Deploy
Incremental
Features
Model
Hypotheses
INNOVATION
CULTURE
CLOUD
Continuous
Delivery
39. Land grab
opportunity Competitive
Observe
Orient
Decide
Measure
Customers
Act
Move
Customer Pain
Point
Analysis
BIG DATA
Plan Response
JFDI
Share Plans
Launch AB
Test
Automatic
Deploy
Incremental
Features
Model
Hypotheses
INNOVATION
CULTURE
CLOUD
Continuous
Delivery
40. Land grab
opportunity Competitive
Observe
Orient
Decide
Measure
Customers
Act
Move
Customer Pain
Point
Analysis
BIG DATA
Plan Response
JFDI
Share Plans
Launch AB
Test
Automatic
Deploy
Incremental
Features
Model
Hypotheses
INNOVATION
CULTURE
CLOUD
Continuous
Delivery
42. Breaking Down the SILOs
Prod
Mgr
UX Dev QA DBA Sys
Adm Adm
Net
Adm
SAN
43. Breaking Down the SILOs
Prod
Mgr
UX Dev QA DBA Sys
Adm Adm
Net
Adm
SAN
Product Team Using Monolithic Delivery
Product Team Using Monolithic Delivery
44. Breaking Down the SILOs
Product Team Using Monolithic Delivery
Prod
UX Dev QA DBA Sys
Net
SAN
Mgr
Adm
Adm
Adm Product Team Using Microservices
Product Team Using Monolithic Delivery
Product Team Using Microservices
Product Team Using Microservices
45. Breaking Down the SILOs
Product Team Using Monolithic Delivery
Prod
UX Dev QA DBA Sys
Net
SAN
Mgr
Adm
Adm
Adm Product Team Using Microservices
Product Team Using Monolithic Delivery
Product Team Using Microservices Platform Team
Product Team Using Microservices
46. Breaking Down the SILOs
Product Team Using Monolithic Delivery
Prod
UX Dev QA DBA Sys
Net
SAN
Mgr
Adm
Adm
Adm Product Team Using Microservices
Product Team Using Monolithic Delivery
Platform Team A
P
I Product Team Using Microservices
Product Team Using Microservices
47. Breaking Down the SILOs
Product Team Using Monolithic Delivery
Prod
UX Dev QA DBA Sys
Net
SAN
Mgr
Adm
Adm
Adm Product Team Using Microservices
Product Team Using Monolithic Delivery
Platform Team
A
P
I Product Team Using Microservices
Product Team Using Microservices
DevOps is a Re-Org
48. Release Plan
Developer
Developer
Developer
Developer
Developer
QA Release
Integration
Ops Replace Old
With New
Release
Monolithic service updates
Works well with a small number
of developers and a single
language like php, java or ruby
49. Release Plan
Developer
Developer
Developer
Developer
Developer
Monolithic service updates
QA Release
Integration
Ops Replace Old
With New
Release
Bugs
Works well with a small number
of developers and a single
language like php, java or ruby
50. Release Plan
Developer
Developer
Developer
Developer
Developer
Monolithic service updates
QA Release
Integration
Ops Replace Old
With New
Release
Bugs
Bugs
Works well with a small number
of developers and a single
language like php, java or ruby
51. Developer
Developer
Developer
Developer
Developer
Old Release Still
Running
Release Plan
Release Plan
Release Plan
Release Plan
Immutable microservice deployment
is faster, scales with large teams and
diverse platform components
52. Developer
Developer
Developer
Developer
Developer
Immutable microservice deployment
is faster, scales with large teams and
diverse platform components
Old Release Still
Running
Release Plan
Release Plan
Release Plan
Release Plan
Deploy
Feature to
Production
Deploy
Feature to
Production
Deploy
Feature to
Production
Deploy
Feature to
Production
53. Developer
Developer
Developer
Developer
Developer
Immutable microservice deployment
is faster, scales with large teams and
diverse platform components
Old Release Still
Running
Release Plan
Release Plan
Release Plan
Release Plan
Deploy
Feature to
Production
Deploy
Feature to
Production
Deploy
Feature to
Production
Deploy
Feature to
Production
Bugs
54. Developer
Developer
Developer
Developer
Developer
Immutable microservice deployment
is faster, scales with large teams and
diverse platform components
Old Release Still
Running
Release Plan
Release Plan
Release Plan
Release Plan
Deploy
Feature to
Production
Deploy
Feature to
Production
Deploy
Feature to
Production
Deploy
Feature to
Production
Bugs
Deploy
Feature to
Production
55. Non-Destructive Production Updates
● “Immutable Code” Service Pattern
● Existing services are unchanged, old code remains in service
● New code deploys as a new service group
● No impact to production until traffic routing changes
● A|B Tests, Feature Flags and Version Routing control traffic
● First users in the test cell are the developer and test engineers
● A cohort of users is added looking for measurable improvement
● Finally make default for everyone, keeping old code for a while
56. What Happened?
Rate of change
increased
Cost and size and
risk of change
reduced
59. If every service has to be
updated at the same time
it’s not loosely coupled
A Microservice Definition
!
Loosely coupled service oriented
architecture with bounded contexts
60. If every service has to be
updated at the same time
it’s not loosely coupled
A Microservice Definition
!
Loosely coupled service oriented
architecture with bounded contexts
If you have to know too much about surrounding
services you don’t have a bounded context. See the
Domain Driven Design book by Eric Evans.
61. Separate Concerns with Microservices
● Invert Conway’s Law – teams own service groups and backend stores
● One “verb” per single function micro-service, size doesn’t matter
● One developer independently produces a micro-service
● Each micro-service is it’s own build, avoids trunk conflicts
● Deploy in a container: Tomcat, AMI or Docker, whatever…
● Stateless business logic. Cattle, not pets.
● Stateful cached data access layer using replicated ephemeral instances
http://en.wikipedia.org/wiki/Conway's_law
62. NetflixOSS - High Availability Patterns
● Business logic isolation in stateless micro-services
● Immutable code with instant rollback
● Auto-scaled capacity and deployment updates
● Distributed across availability zones and regions
● De-normalized single function NoSQL data stores
● See over 40 NetflixOSS projects at netflix.github.com
● Get “Technical Indigestion” trying to keep up with techblog.netflix.com
64. Where to Start? Mobile
Enterprise Mobile Apps
Horizontal Team
App-Store Provisioning
APIs to Everyone
DevOps Already…
65. Reaction from Fortune 100 CTO:
“But Netflix has a superstar development team, we don’t!"
66. Reaction from Fortune 100 CTO:
“But Netflix has a superstar development team, we don’t!"
Adrian’s Response:
“Netflix hired them from you, and got out of their way…”
71. Any Questions?
● Battery Ventures http://www.battery.com
● Adrian’s Blog http://perfcap.blogspot.com
● Slideshare http://slideshare.com/adriancockcroft
!
● Monitorama Opening Keynote Portland OR - May 7th, 2014 - Video available
● GOTO Chicago Opening Keynote May 20th, 2014
● Qcon New York – Speed and Scale - June 11th, 2014 - Video available
● Structure - Cloud Trends June 19th, 2014 - Video available
● GOTO Copenhagen/Aarhus – Denmark – Sept 25th, 2014
● DevOps Enterprise Summit - San Francisco - Oct 21-23rd, 2014
● GOTO Berlin - Germany - Nov 6th, 2014
● AWS Re:Invent - Las Vegas - November 14th, 2014
Disclosure: some of the companies mentioned are Battery Ventures Portfolio Companies
See www.battery.com for a list of portfolio investments