Devops and Immutable infrastructure - Cloud Expo 2015 NYC

Jun 10, 201516 likes11,988 views

You often hear the two titles of "DevOps" and "Immutable Infrastructure" used independently. In his session at DevOps Summit, John Willis, Technical Evangelist for Docker, will cover the union between the two topics and why this is important. He will cover an overview of Immutable Infrastructure then show how an Immutable Continuous Delivery pipeline can be applied as a best practice for "DevOps." He will end the session with some interesting case study examples.

@bglpe
Devops and Immutable
Infrastructure
John Wills!
Technical Evangelist

@bglpe
@botchagalupe
• a.k.a. John Willis
• 35 Years in IT Operations
• Exxon, Canonical, Chef,
Enstratius, Socketplane
• Devopsdays Core Organizer
• Devopscafe on iTunes
• Tweet to @bglpe for Questions

@bglpe
Agenda
• What is Immutable Infrastructure?
• Why Immutable (Order Matters)
• Models and Methods
• Docker and Immutable Infrastructure
• Case Studies

@bglpe
“The least-cost way to ensure that the behavior of any
two hosts will remain completely identical is always to
implement the same changes in the same order on both
hosts.”
Order Matters

@bglpe
Management Methods
• Divergence
• Convergence
• Congruence

@bglpe
Why (When) Does Order
Matter?
• Circular Dependancies
• Right Command Wrong Order
• Right Package Wrong Order

@bglpe
Immutable Infrastructure
“Model”
• No CRUD allowed for…
• Packages
• Conﬁguration Files
• Application Software
• Data (RUD)

@bglpe
How To Do Immutable?
• Provision a new server.
• Test the new server.
• Change the reference to the new server.
• Keep the old server around for rollback.

@bglpe
The Immutable “Trombone”
• Golden Images
• Virtual Desktop Infrastructure (VDI)
• Virtual Images
• Phoenix Servers vs Snowﬂake Servers
• Infrastructure as Code
• Bake vs Fry
• Containers

@bglpe
Why Docker?
• Isolation
• Lightweight
• Simplicity
• Workﬂow
• Community

@bglpe
Docker Community
• 1200 Docker Contributors
• 100,000 Dockerized Applications
• 3 to 4 Million Developers using Docker
• 300 Million Downloads
• 32,000 Docker Related Projects
• 70% of enterprises are using Docker

@bglpe
References
Docker and the Three Ways of Devops!
https://blog.docker.com/2015/05/docker-three-ways-ops/!
!
Trash Your Servers and Burn Your Code: Immutable Infrastructure and Disposable Components!
Chad Fowler June 2013!
http://chadfowler.com/blog/2013/06/23/immutable-deployments/!
!
PhoenixServer!
Martin Fowler July 2012!
http://martinfowler.com/bliki/PhoenixServer.html!
!
Building with Legos!
http://techblog.netﬂix.com/2011/08/building-with-legos.html!
!
Immutable Infrastructure with Docker and EC2": Gilt at Dockercon (Video)!
http://tech.gilt.com/post/90578399884/immutable-infrastructure-with-docker-and-ec2!
!
Why you should build an Immutable Infrastructure!
by Florian Motlik - 2014-07-22!
https://blog.codeship.com/immutable-infrastructure/!
!
Baked Servers vs Fried Servers!
http://if.andonlyif.net/blog/2012/10/baked-servers-vs-fried-servers.html!
!
Why Order Matters: Turing Equivalence in Automated Systems Administration!
https://www.usenix.org/legacy/publications/library/proceedings/lisa02/tech/full_papers/traugott/traugott_html/index.html!
!
An Analysis of RPM Validation Drift!
https://www.usenix.org/legacy/events/lisa2002/tech/full_papers/hart/hart.pdf!

@bglpe
john.willis@docker.com
@botchagalupe

We often employ the "build-once-run-everywhere" principle to our application binaries. Our build server builds an artifact and puts it in a repository, this same artifact is then promoted from environment to environment, from test to production, to make sure that what ends up in production is the very same thing as what we have thoroughly tested before. Now, in a world of virtualization, what if we were to do the same thing with our complete infrastructure? In stead of just building our application and promote it from environment to environment, what if we would build a complete virtual machine image and do the same with that? Could we? This is what immutable infrastructure is about. Boxfuse can help you get there.

Splunk user group - automating Splunk with AnsibleMark Phillips

Inrastructure as CodeCharles Anderson

The Architect WayJan Jongboom

The document discusses modularizing a codebase using Architect, a dependency injection framework for Node.js. It describes problems that can occur when a codebase grows such as tight coupling between modules and lack of configuration options. Architect addresses these by treating each piece of functionality as a plugin that can import other plugins, declares dependencies, and is configured through options. This allows building independent and testable modules that can be combined to create applications.

DevOps Cardiff - Puppet vs Chef vs AnsibleMark Phillips

Hadoop Demystified + Automation Smackdown! Austin JUG June 24 2014datafundamentals

This document discusses two approaches to ETL jobs in Hadoop: a manual "special snowflake" approach and an automated approach. The manual approach involves a team spending a year copying and pasting code for 15 jobs. This leads to spaghetti code and is not sustainable. The automated approach involves designing reusable templates and rules to automate the ETL process. This frees up the developer Brent to focus on design rather than manual work. It results in code that is clean, consistent, easy to maintain and passes the "10 minute test" of being idempotent. The document demonstrates generating ETL code from metadata and deploying the automated jobs to Hadoop.

Serverless On Stage - Serverless URL ShortenerLuca Bianchi

CI/CD at bol.comMaarten Dirkse

You don’t need DTAP + Backbase implementation - Amsterdam 17-12-2015Pavel Chunyayev

WordPress Development EnvironmentsJosh Cummings

This document discusses tools for creating a WordPress development environment. It covers common development setups like LAMP/LEMP stacks, tools for local development like text editors and version control, and options for setting up a local environment like MAMP, native Linux/Mac stacks, Virtual Machines with Vagrant/VVV, and containers with Docker. The goals are to choose tools that allow for effective collaboration, testing, and deploying code across different environments.

User-percieved performanceMike North

Deployment Automation - My journey at PeazieWee Keat Chin

Actors Set the Stage for Project Orleanscjmyers

Dim the lights and queue the music. The stage has been set, and the virtual actors are soon to arrive. Come join an engaging discussion on Project Orleans and how it will create for us a world that transcends traditional three-tier architecture and truly achieves solutions with a high degree of performance, reliability, and scalability. In this discussion, Chris will provide an overview of actor model theory and discuss how Orleans leverages virtual actors in order to provide a high throughput, low latency, and high availability solution architecture. You will also learn how this tried and tested framework has been successfully leveraged in Azure in order to provide the extremely scalable and performant platform that has brought you some of your favorite online Xbox games and Microsoft products.

Developing Cross-Platform Web Apps with ASP.NET Core1.0EastBanc Tachnologies

Author: Dmitry Podrezov, www.easbacntech.com This deck showcases what's new and what's been trimmed in the upcoming version of ASP.NET framework scheduled for release this summer. The framework was built from ground-up for multiple platforms and those trying to migrate existing solutions into it will need to be ready for a few breaking changes. This is not a 101 description the framework fundamentals, rather it is a demo of new features and changes. The talk is packed with demonstrations and live code experience.

Avoiding integration hellaaronbassett

The document discusses integration hell, which can occur when developing software if changes and deployments happen too frequently without proper processes. It provides details on a real-world project with 6 developers, over 900 files, and a deployment every 43 minutes on average. Recommendations are made around using tools like Git, Jenkins, virtualenv, and others to help manage the integration process and spot problems early.

Managing changes to eZPublish DatabaseGaetano Giunta

The New JavaScript: ES6Rob Eisenberg

This year ECMA International will be ratifying the biggest update to the JavaScript language in its history. In this talk we'll look at key features already appearing in browsers as well as those coming in the near future. We'll also explore how you can begin leveraging the power of ES6 across all browsers today. If you haven't looked at JavaScript recently, you soon realize that a bigger, better world awaits.

Stackato v3Jonas Brømsø

Ten years laterCristian Vat

This document discusses the history and evolution of JavaScript over the past 23 years, from its origins in 1995 to the present. It focuses on key events like the standardization of ECMAScript, the introduction of AJAX, jQuery, and how Google Chrome and technologies like V8, Node.js, and WebAssembly have driven JavaScript's widespread adoption and improved performance. JavaScript has gone from an experimental scripting language to being ubiquitous across the web and in applications through technologies like Electron.

Powerful Automation Made SimpleGaetano Giunta

The Silver Bullet Syndrome by Alexey VasilievPivorak MeetUp

This document discusses various technology trends and challenges related to software development. It cautions against blindly following trends or buzzwords and emphasizes the importance of understanding user needs and making choices based on project context rather than social pressures. While new technologies can enable improvements, there is no single "silver bullet" solution and all code comes with costs that must be weighed against the goals of building useful software.

What we talk about when we talk about DevOpsRicard Clau

This document discusses DevOps concepts and tools. It begins by outlining common problems companies face with development and operations, such as deployments being events and environments differing. It then defines DevOps as developers and operations working together to deliver value through automation, continuous integration/delivery, and infrastructure as code. The document recommends starting with CI/CD and configuration management to gradually introduce DevOps. It provides overviews and demonstrations of Packer, Ansible, and Terraform as example tools.

React talk, GrunnJs 24 September 2014_jjoos_

Erlang - Dive Right Invorn

Erlang is a functional programming language built for reliability and concurrency. It is used to build scalable and fault-tolerant systems through features like its supervision tree, behaviors, and OTP framework. The document recommends learning more about Erlang through various books and online resources, and suggests trying out the build tools rebar and ChicagoBoss or contributing to open source projects like Riak to get hands-on experience with the language.

Dev-Friendly OpsJosh Schramm

1. The document discusses how OpsWorks has made the presenter's life easier as a developer who also handles operations. OpsWorks provides hosted infrastructure on AWS for deploying applications using Chef recipes. 2. It describes the main structures in OpsWorks - stacks, layers, apps, and instances. Stacks represent entire applications, layers define different parts like web servers, apps contain specific settings, and instances define the servers. 3. The presenter discusses using OpsWorks with Ruby on Rails applications, including customizing Chef recipes, deploying code, and integrating other AWS services for monitoring, security, and scaling. While documentation can be confusing, OpsWorks provides an easy way for developers to manage operations.

The Architect Way - JSCamp.asia 2012Jan Jongboom

The document introduces Architect, a module system for JavaScript applications. It discusses problems that arise when codebases grow large, such as duplicated modules, dependency errors, and long startup times. Architect addresses these by defining each piece of functionality as a plugin that can import other plugins. An application is defined as a set of plugins, allowing modularization and loose coupling between components. Plugins are configured through options and communicate through an event bus. This allows features to be swapped out easily for different implementations, improving testability and flexibility.

Michael North "Ember.js 2 - Future-friendly ambitious apps, that scale!"Fwdays

Ember.js is being adopted more and more broadly as time passes, and is an excellent choice for highly complex data-driven UIs. With the recent release of the "2.0" version of the framework, things are faster, smarter, and easier than ever. With a focus on productivity and reducing the number of trivial decisions developers must make while building an app, it's astonishing how quickly one can get up and running, and how well the abstractions hold up as the codebase scales in size and complexity. I'd like to give a general overview of Ember, and pause to reflect on some important differences that may be important when considering what the best tool is for your project.

Three Lessons Global CEOs Can Learn From Grassroots ActivistsGaurav Mishra

Global CEOs can learn three lessons from grassroots activists: 1) Always start with why - understand your company's purpose and inspire employees. 2) Give more than you take - maximize societal and environmental impact beyond profits. 3) Know that you will need help - create ecosystems that bring together stakeholders to co-create solutions. Examples of companies doing this include Nike's apps to inspire exercise as a social activity, and Mahindra's programs to connect employees with people needing help.

Pets vs. Cattle: The Elastic Cloud StoryRandy Bias

More Related Content

What's hot (20)

CI/CD at bol.comMaarten Dirkse

You don’t need DTAP + Backbase implementation - Amsterdam 17-12-2015Pavel Chunyayev

WordPress Development EnvironmentsJosh Cummings

User-percieved performanceMike North

Deployment Automation - My journey at PeazieWee Keat Chin

Actors Set the Stage for Project Orleanscjmyers

Developing Cross-Platform Web Apps with ASP.NET Core1.0EastBanc Tachnologies

Avoiding integration hellaaronbassett

Managing changes to eZPublish DatabaseGaetano Giunta

The New JavaScript: ES6Rob Eisenberg

Stackato v3Jonas Brømsø

Ten years laterCristian Vat

Powerful Automation Made SimpleGaetano Giunta

The Silver Bullet Syndrome by Alexey VasilievPivorak MeetUp

What we talk about when we talk about DevOpsRicard Clau

React talk, GrunnJs 24 September 2014_jjoos_

Erlang - Dive Right Invorn

Dev-Friendly OpsJosh Schramm

The Architect Way - JSCamp.asia 2012Jan Jongboom

Michael North "Ember.js 2 - Future-friendly ambitious apps, that scale!"Fwdays

CI/CD at bol.comMaarten Dirkse

You don’t need DTAP + Backbase implementation - Amsterdam 17-12-2015Pavel Chunyayev

WordPress Development EnvironmentsJosh Cummings

User-percieved performanceMike North

Deployment Automation - My journey at PeazieWee Keat Chin

Actors Set the Stage for Project Orleanscjmyers

Developing Cross-Platform Web Apps with ASP.NET Core1.0EastBanc Tachnologies

Avoiding integration hellaaronbassett

Managing changes to eZPublish DatabaseGaetano Giunta

The New JavaScript: ES6Rob Eisenberg

Stackato v3Jonas Brømsø

Ten years laterCristian Vat

Powerful Automation Made SimpleGaetano Giunta

The Silver Bullet Syndrome by Alexey VasilievPivorak MeetUp

What we talk about when we talk about DevOpsRicard Clau

React talk, GrunnJs 24 September 2014_jjoos_

Erlang - Dive Right Invorn

Dev-Friendly OpsJosh Schramm

The Architect Way - JSCamp.asia 2012Jan Jongboom

Michael North "Ember.js 2 - Future-friendly ambitious apps, that scale!"Fwdays

Viewers also liked (20)

Three Lessons Global CEOs Can Learn From Grassroots ActivistsGaurav Mishra

Pets vs. Cattle: The Elastic Cloud StoryRandy Bias

The Art Of Writing A Business Plan (Zafar)Naeem Zafar

Writing a business plan is often a giant obstacle for an entrepreneur. It seems complex and many have never seen a business plan before. The Art of Writing a Business Plan will demystify the process for you. We will outline the logical sequence of thinking through all aspects of starting a business and putting that in a document that will become the source of enlightenment for you and your investors. We will cover the following topics - What is a business plan and when is it needed? How long should it be and what topics must it cover? Who should write it and who will read it? How long will it take to write a business plan? Why do I need one? How will you provide a detailed outline of all sections that are needed? What should not be in a business plan?

WebRTC beyond Audio and Video Silvia Pfeiffer

Internet of things, Big Data and Analytics 101Mukul Krishna

Cloud Expo - KEYNOTE Career HacksSandy Carter

This document discusses strategies for women in technology careers. It suggests acting like an open API by sharing knowledge through blogging, teaching and mentoring. It also recommends being intentional about social media influence by being active in the right online communities. Additionally, it advises showing your soft skills to win difficult sales by highlighting personal interests and driving collaborative skills. The document stresses that career advancement comes from challenging assignments, not just qualifications, and emphasizes the importance of developing lifelong relationships through networking and engagement.

WebRTC Reborn - Cloud Expo / WebRTC SummitDan Jenkins

Sane SQL Change Management with SqitchDavid Wheeler

This document discusses Sqitch, a tool for managing database schema changes. Sqitch uses plain SQL scripts checked into version control. It handles dependencies between changes, generates deployment plans, and tags deployed changes. The key advantages of Sqitch include reduced duplication, built-in configuration, deployment planning, and tight integration with version control systems through a Git-like workflow.

Understand Immutable infrastructure - at Build Stuff Kiev 2016Quentin Adam

Immutable infrastructure with Docker and EC2dotCloud

This document discusses Gilt's strategy of using immutable infrastructure with Docker and EC2 to enable continuous delivery and minimize risk when deploying new software versions. Some key points made include: - Gilt builds Docker containers for each new application version, creates a new "stack" of infrastructure to run the container, and uses incremental rollout and automated rollback to reduce risk. - Immutable infrastructure emerges naturally with Docker since each version requires new containers and infrastructure rather than updating existing instances. - Automating deployment, rollback, and incremental rollout across new infrastructure stacks reduces probability, cost and occurrences of failures when deploying new versions. - Instant rollback is possible by moving traffic back to the previous version's infrastructure if

Immutable Infrastructure: Rise of the Machine ImagesC4Media

Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/1WlpXHF. Axel Fontaine looks at what Immutable Infrastructure is and how it affects scaling, logging, sessions, configuration, service discovery and more. He also looks at how containers and machine images compare and why some things people took for granted may not be necessary anymore. Filmed at qconlondon.com. Axel Fontaine is the founder and CEO of Boxfuse. Axel is also the creator and project lead of Flyway, the open source tool that makes database migration easy. He is a Continuous Delivery and Immutable Infrastructure expert, a Java Champion, a JavaOne Rockstar and a regular speaker at various large international conferences.

Immutable Infrastructure: the new App DeploymentAxel Fontaine

Immutable Infrastructure: the new App Deployment App deployment and server setup are complex, error-prone and time-consuming. They require OS installers, package managers, configuration recipes, install and deployment scripts, server tuning, hardening and more. But... Is this really necessary? Are we trapped in a mindset of doing things this way just because that's how they've always done? What if we could start over and radically simplify all this? What if, within seconds, and with a single command, we could wrap our application into the bare minimal machine required to run it? What if this machine could then be transported and run unchanged on our laptop and in the cloud? How do the various platforms and tools like AWS, Docker, Heroku and Boxfuse fit into this picture? What are their strengths and weaknesses? When should you use them? This talk is for developers and architects wishing to radically improve and simplify how they deploy their applications. It takes Continuous Delivery to a level far beyond what you've seen today. Welcome to Immutable Infrastructure generation. This is the new black.

Joomla! 1.5 Para PrincipiantesLuis Barriocanal

El documento describe las necesidades de un servidor web para ejecutar Joomla, incluyendo un servidor Apache, MySQL como gestor de base de datos, PHP como lenguaje de programación e interpretación, y PhpMyAdmin para gestionar MySQL a través de la web. Se explica que Joomla es un sistema de gestión de contenidos que funciona como una aplicación en un servidor web, no como un programa para diseñar páginas web directamente.

SPOF - Single "Person" of FailureSasha Rosenbaum

Chaos patterns - architecting for failure in distributed systemsJos Boumans

As we architect our systems for greater demands, scale, uptime, and performance, the hardest thing to control becomes the environment in which we deploy and the subtle but crucial interactions between complicated systems. Chaos Patterns help us establish and implement a virtuous cycle that let’s us both prove & improve our system along each of these dimensions before the inevitable happens. While it may seem reckless or counter-intuitive, our experience has proven that it’s a matter of how and when (not if) we will learn about the limitations and failure modes of the system. This is the story of the pitfalls we encountered, and how, through architecture, convention and common sense, we managed to build an infrastructure that is "Always Up" from the end user perspective and incredibly economical to build, scale & operate; using chaos testing, we learn more about how our system fails from a 10 second controlled failure than a multi-hour uncontrolled outage. In this session we will cover various implementation techniques, available to any developer & operator, which will vastly increase the resilience of your systems and provide a superior end user experience; from optimizing your use of DNS for failure, to configuring your CDN to have your back, to synthetic responses and expected database outages. But why stop there? Netflix has pioneered a culture and suite of tools that actively injects ‘once in a blue moon’ failures into its production systems, which lets you battle test your resilience design and let developers & operators sleep comfortably at night knowing their systems are able to handle even the worst of worst case scenarios.

Un-broken Logging - Operability.io 2015 - Matthew SkeltonSkelton Thatcher Consulting Ltd

The document discusses how logging in software is often broken and provides recommendations for making logging more effective. It recommends using continuous event IDs, transaction tracing, log aggregation and search tools, designing software with logging in mind, and making log severity levels configurable. This will help with tasks like verification, traceability, accountability, and diagnosing issues across development and operations teams.

Monitoring Is Never DoneMelanie Cey

Time to say goodbye to your Nagios based setupCheck my Website

Production testing through monitoringLeon Fayer

Identifying and fixing issues in new code before deploying it to production is important for every software development cycle. However, relying on traditional testing methods in the age of Internet-scale data driven problems may prove to be incomplete. Identifying and fixing the issues in production quickly is crucial, but it requires insight into usage patterns and trends across the whole architecture and application logic. In this talk I touch on inefficiencies of some of the most common testing methods, provide real world examples of discovering odd edge cases with monitoring and offer recommendations on top-down metric instrumentation to help DevOps organizations with identifying and acting on business-effecting problems.

Continuous Delivery Tools Collaboration Conways Law - QCon London - Matthew S...Skelton Thatcher Consulting Ltd

Presentation given at QCon London on 4th March 2015 Tools, Collaboration, and Conway's Law: how to choose and use tools effectively for Continuous Delivery and DevOps With an ever-increasing array of tools and technologies claiming to 'enable DevOps' or 'implement Continuous Delivery', how do we know which tools to try or to choose? In-house, open source, or commercial? Ruby or shell? Dedicated or plugins? It transpires that highly collaborative practices such as DevOps and Continuous Delivery require new ways of assessing tools and technologies in order to avoid creating new silos. Matthew Skelton shares his recent experience of helping many different organisations to evaluate and select tools to facilitate DevOps and Continuous Delivery, including version control, log aggregation, deployment pipelines, monitoring and metrics, and infrastructure automation tools; the recommendations may surprise you.

Three Lessons Global CEOs Can Learn From Grassroots ActivistsGaurav Mishra

Pets vs. Cattle: The Elastic Cloud StoryRandy Bias

The Art Of Writing A Business Plan (Zafar)Naeem Zafar

WebRTC beyond Audio and Video Silvia Pfeiffer

Internet of things, Big Data and Analytics 101Mukul Krishna

Cloud Expo - KEYNOTE Career HacksSandy Carter

WebRTC Reborn - Cloud Expo / WebRTC SummitDan Jenkins

Sane SQL Change Management with SqitchDavid Wheeler

Understand Immutable infrastructure - at Build Stuff Kiev 2016Quentin Adam

Immutable infrastructure with Docker and EC2dotCloud

Immutable Infrastructure: Rise of the Machine ImagesC4Media

Immutable Infrastructure: the new App DeploymentAxel Fontaine

Joomla! 1.5 Para PrincipiantesLuis Barriocanal

SPOF - Single "Person" of FailureSasha Rosenbaum

Chaos patterns - architecting for failure in distributed systemsJos Boumans

Un-broken Logging - Operability.io 2015 - Matthew SkeltonSkelton Thatcher Consulting Ltd

Monitoring Is Never DoneMelanie Cey

Time to say goodbye to your Nagios based setupCheck my Website

Production testing through monitoringLeon Fayer

Continuous Delivery Tools Collaboration Conways Law - QCon London - Matthew S...Skelton Thatcher Consulting Ltd

Similar to Devops and Immutable infrastructure - Cloud Expo 2015 NYC (20)

Devopsdays Chicago State of the Union 2015John Willis

John Willis from Docker, Inc gave a presentation on the state of DevOps. He discussed loose DevOps taxonomies like CAMS (Culture, Automation, Measurement, Sharing) and ICE (Inclusion, Complexity, Empathy). Recent DevOps surveys showed improvements in code quality and testing. Adoption of DevOps in the enterprise is growing through forums and working groups. Technologies supporting DevOps include containers, microservices, and immutable infrastructure. Empathy, collaboration, and a learning culture were emphasized as keys to high performance.

DevopsCon Munich - Keynote - Devops State of the UnionJohn Willis

John Willis, Director of Ecosystem Development at Docker, Inc., gave a presentation on the state of DevOps. He discussed common DevOps frameworks like CAMS (Culture, Automation, Measurement, Sharing) and ICE (Inclusion, Complexity, Empathy). Survey results showed high performing organizations have high trust, cross-functional collaboration, and shared responsibilities. Willis also covered DevOps in the enterprise, with working groups on security compliance and test automation. He advocated for concepts from lean manufacturing like kaizen, jidoka, and genchi genbutsu to drive continuous improvement.

Data Modeling for NoSQLTony Tam

- Data modeling for NoSQL databases is different than relational databases and requires designing the data model around access patterns rather than object structure. Key differences include not having joins so data needs to be duplicated and modeling the data in a way that works for querying, indexing, and retrieval speed. - The data model should focus on making the most of features like atomic updates, inner indexes, and unique identifiers. It's also important to consider how data will be added, modified, and retrieved factoring in object complexity, marshalling/unmarshalling costs, and index maintenance. - The _id field can be tailored to the access patterns, such as using dates for time-series data to keep recent

Core Principles Of CiOpenSource Connections

Core Principles of CI was a presentation that covered: 1) The definition of continuous integration as automated builds that run many times a day. 2) The key aspects of CI including source code compilation, database integration, testing, inspection, deployment, feedback, and producing deployable software. 3) The benefits of CI like reduced human error, rapid feedback cycles, increased project visibility and confidence, and facilitating communication.

200808 AIM Walking SkeletonTroy Young

This document discusses the concept of a "walking skeleton", which is a minimal implementation of a software system that links together the main architectural components and allows the architecture and functionality to evolve together. It provides examples of challenges in implementing a walking skeleton for a claims revamp project at a company. The walking skeleton started as more of a spike but helped identify technical challenges and created a foundation to resume work later.

Android Developer Skills, Techniques, and Patternsgdgut

Ancestry is a large company that provides family history and DNA testing services. It has over 1 billion records in its databases and over 3 million subscribers. As an Android developer at Ancestry, a typical day involves collaborating with teammates to work on user stories, addressing bugs, learning new skills, and ensuring code quality. Developers focus on testing, code reviews, following best practices, and balancing individual and team work. The goal is to build high quality features while continuously improving skills.

Reactive Development: Commands, Actors and Events. Oh My!!David Hoerster

Distributed applications are becoming more popular with the increasing popularity of microservices (however you want to define that term). But the principles of distributed application development are key if you want to build a system that is resilient, responsive, elastic and maintainable. In this workshop, we’ll review the principles of CQRS and the Reactive Manifesto, and how they complement each other. We’ll build an application that can handle a large stream of data, and allow users to still have a responsive experience while interacting with real-time and near-real-time data. We’ll look at Akka.NET as the workhorse inside your services, and how the principles of CQRS can help with your service-to-service communications. We’ll also look at how Event Sourcing can aid in managing your domain state, and how an event stream can be used to project data for your system for a number of different uses. We’ll build our own simple event store, but also look at commercially available stores, too. This session will focus on using Akka.NET along with a few other tools and technologies, such as EventStore and MongoDB. The concepts learned in this session will be applicable to a number of different tools, technologies and languages.

What I Learned Building a Toy Example to Crawl & Render like GoogleCatalyst

JR Oakes presented on building a toy crawler and renderer to better understand how Google and other search engines operate. He discussed key components of crawlers like prioritizing pages, handling duplicates, and respecting robots.txt. He then created a simple "toy internet" of linked pages to crawl. JR built a basic crawler in Python that applies techniques like PageRank, renders pages with Chrome Headless, and includes a search interface using Streamlit. The open source project is intended for learning and experimentation.

Engage 2019: Modernising Your Domino and XPages Applications Paul Withers

This document discusses modernizing Domino and XPages applications. It covers modernizing web and mobile interfaces, using Dynamic Query Language for improved performance, and integrating applications via REST APIs. The document provides examples and considerations for updating applications' user interfaces, database design, and integration to meet modern needs and habits while leveraging new platform capabilities.

DOES15 - Joshua Corman & John Willis - Immutable Awesomeness?Gene Kim

Immutable Awesomeness?: Where Containers Collide with SW Supply Chains Joshua Corman, CTO, Sonatype John Willis, Director of Ecosystem Development, Docker With continuous development, we write less code and consume more re-usable open source code. We are getting faster and more efficient. But this innovation also accelerates complexity and complexity is the enemy of quality. Poor quality creates unplanned/unscheduled work. Re-work creates a drag on development speed. It’s a continuous loop. Couple this complexity with the fact that this past year was open season on open source. Heartbleed, Bash Bug, Shellshock… For many it took days, weeks, even months to determine if they were impacted, where they were impacted and then make the appropriate fixes. That’s a lot of unplanned work. And those are just the vulnerabilities that made the headlines. With the emergence of containers there is a benefit of even more speed and efficiency, but at the cost of visibility at a time when we need it most. The good news: other industries have figured this out with supply chain management. Applying supply chain approaches to software raises the bar on continuous goals. A few of the patterns we can take from the rigor of things like the Toyota Supply Chain: - Scrutinize the number and quality of your “suppliers” - Manage out avoidable risk and complexity - Improve traceability and visibility - Ensure prompt agile responses when things go wrong These two speakers will show that you can deliver applications on-time (even faster), on-budget (even more efficiently) and with a natural byproduct of higher quality and less risk by embracing supply chain principles as you embrace containerization with tools like Docker.

The Key Components of Adopting CI The OpenStack WayiWeb (group INAP)

Devopsdays Toronto 2016 - State of the UnionJohn Willis

This document summarizes John Willis's presentation on the state of DevOps. Some key points from loose DevOps taxonomies like CAMS (Culture, Automation, Measurement, Sharing) and ICE (Inclusion, Complexity, Empathy) are discussed. Survey results show benefits like better code quality and testing. Case studies from companies like Target, Verizon, and Nordstrom demonstrate DevOps successes in reducing lead times and defects in large enterprises. Empathy is emphasized as important for reducing burnout and facilitating collaboration between dev and ops teams.

A tale of 3 databasesChris Skardon

This document summarizes Chris Skardon's experience migrating the database for his competition running site Tournr from SQL to document and graph databases. It describes how the initial database choice of SQL Server became limiting and led to migrations first to RavenDB, a document database, and then to Neo4j, a graph database. Both migrations required reworking the data model and code but provided performance and flexibility benefits. While challenging, the migrations were worthwhile as the graph model better fit Tournr's needs.

BackbonemeetupBen McCormick

Ben McCormick will give a presentation on Backbone.js. He has over a year of experience using Backbone and experience with alternatives like React, Angular, and Knockout. He will explain what Backbone is, why it remains relevant despite newer frameworks, and provide demonstrations. Backbone is a lightweight client-side JavaScript framework that provides models, collections, views, and routing capabilities. It emphasizes separation of data and views, extensibility, minimalism, and transparency. These principles allow for flexibility, usability, fast learning, and stability over time as technologies evolve.

Ds @ bolAsparuh Hristov

The document discusses various data science applications at Bol.com including measuring user interactions on the website, forecasting product demand, and building recommendation systems. It provides examples and details for each application. For measuring, it notes Bol is able to process user event data with a 1-2 second lag compared to 25-30 seconds for another company. For recommendations, it highlights improvements from moving the service to the cloud including faster response times and being able to generate new predictions in 30 minutes instead of 24 hours. For forecasting demand, it outlines the process and techniques used including starting small, experimenting fast, and scaling up over time using various machine learning models and cloud technologies.

Getting intimate with GitKoalaMetrics

The presentation was given by Grzesiek Sikorski ([email protected]) at FreshTalk #17 - a morning tech talk organised by KoalaMetrics and Sigmapoint. We meet every two weeks in Krakow to talk about mobile technology, mobile apps, Android, iOS and data science. For more info check out our meetup website (http://www.meetup.com/FreshTalk/) or the event blog (http://koalametrics.github.io/).

DBmaestro's State of the Database Continuous Delivery Survey- Findings RevealedDBmaestro - Database DevOps

The document summarizes findings from a survey on continuous delivery practices. The survey found that while 81% of organizations practiced some form of continuous delivery for their code, only around 50% did so for their databases. Key challenges included a lack of database version control, manual scripting processes prone to errors, and a lack of trust and communication between developers and database administrators. Adopting database version control, automated deployments informed by version control data, and making DBAs responsible for continuous delivery processes could help address these challenges and barriers to fully implementing continuous delivery for databases.

What is devopsAaron Blythe

The document discusses the origins and key principles of DevOps. It originates from a 2009 Velocity Conference talk about Flickr's deployment practices of 10+ deploys per day through automation, shared version control, and one-step builds. The main principles discussed are CAMS - Culture, Automation, Measurement, and Sharing. Culture focuses on respect, trust, and avoiding blame. Automation, measurement, and sharing are also emphasized as important aspects of DevOps.

50 Shades of Fail KScope16Christian Berg

This document discusses common mistakes made in Oracle Business Intelligence development. It is organized by categories including the three layers of the RPD, system/DevOps/security issues, multidimensional modeling failures, front-end usage mistakes, and analysis/dashboard errors. Specific examples provided include using incorrect data types, not creating dimensional hierarchies, manual security management instead of roles, treating cubes like relational sources, and using OBI as an Excel exporting or data entry tool. The document is intended to review worst practices to improve core OBI development skills.

DevOps: IT's Automation RevolutionIBM UrbanCode Products

DevOps aims to reduce conflict between development and operations teams through improved collaboration and automation. It advocates destroying stereotypes, involving both teams in strategy, instilling process discipline, and accelerating workflows with automation. Automation can perform tasks and connect processes to reduce complexity and accelerate application deployment. Successful DevOps requires open communication across the development lifecycle and treating releases as packaged transitions rather than individual components.

Devopsdays Chicago State of the Union 2015John Willis

DevopsCon Munich - Keynote - Devops State of the UnionJohn Willis

Data Modeling for NoSQLTony Tam

Core Principles Of CiOpenSource Connections

200808 AIM Walking SkeletonTroy Young

Android Developer Skills, Techniques, and Patternsgdgut

Reactive Development: Commands, Actors and Events. Oh My!!David Hoerster

What I Learned Building a Toy Example to Crawl & Render like GoogleCatalyst

Engage 2019: Modernising Your Domino and XPages Applications Paul Withers

DOES15 - Joshua Corman & John Willis - Immutable Awesomeness?Gene Kim

The Key Components of Adopting CI The OpenStack WayiWeb (group INAP)

Devopsdays Toronto 2016 - State of the UnionJohn Willis

A tale of 3 databasesChris Skardon

BackbonemeetupBen McCormick

Ds @ bolAsparuh Hristov

Getting intimate with GitKoalaMetrics

DBmaestro's State of the Database Continuous Delivery Survey- Findings RevealedDBmaestro - Database DevOps

What is devopsAaron Blythe

50 Shades of Fail KScope16Christian Berg

DevOps: IT's Automation RevolutionIBM UrbanCode Products

More from John Willis (20)

Automated GovernanceJohn Willis

This document provides an overview of automated governance and DevSecOps. It discusses using automated governance to reduce audit time, increase efficacy, shorten feedback loops, and enable trust. Automated governance can enforce policies to block vulnerabilities and misconfigurations. The remainder of the document discusses industry trends and outlines a reference architecture for implementing DevSecOps automated governance across development, non-production, and production stages.

Devops Long Strange Trip John Willis

I Got 99 Problems and a Bash DSL Ain't One of ThemJohn Willis

This document summarizes the evolution of configuration management over four decades through three generations: - First generation used scripting and descriptive files for manual, ad hoc configuration. - Second generation introduced declarative languages and full automation with desired states but environments were convergent, not identical. - Third generation focuses on immutable infrastructure, consistency through automation from development to production, and disposable environments using techniques like infrastructure as code and immutable delivery.

Math is coolJohn Willis

Math is used in many jobs and fields. 94% of jobs use some type of math like fractions, decimals, and percentages. 34% of labor jobs use basic algebra and 29% use geometry and trigonometry. Jobs that commonly use math include animators, computer scientists, engineers, scientists, economists, and designers. Specific areas of math like algebra, calculus, trigonometry, and geometry have applications in music, gaming, roller coasters, cybersecurity, artificial intelligence, and engineering. The demand for math-related jobs like data scientists, software developers, and engineers is growing significantly.

The 7 deadly diseases of DevOps 2019John Willis

The document outlines an agenda for a webinar on the 7 deadly diseases of DevOps. The webinar will discuss identifying problems within an organization's culture and processes through forensics of why approaches like Lean and Agile have failed to create longstanding improvements. Speakers will also cover how human capital intersects with technology and keys to long-term improvement. The bulk of the webinar will focus on explaining and addressing 7 specific diseases that plague DevOps initiatives: invisible work, management system toil, tribal knowledge, misalignment of incentives, incongruent organizational design, managing complexity, and security and compliance theater. Attendees can submit questions during the live webinar.

Next Generation Infrastructure - Devops Enterprise Summit 2018John Willis

Kubernetes is a container management platform that allows for the orchestration of containers. It uses a service mesh like Istio to provide capabilities like observability, traffic control, service discovery and load balancing for microservices. Kubernetes supports API extensibility through custom resources and controllers that can monitor and make decisions about clusters. Kubebuilder is an SDK that makes it easier to build and publish custom Kubernetes APIs.

swampUP - 2018 - The Divine and Felonious Nature of Cyber SecurityJohn Willis

The document discusses the divine and felonious nature of cyber security and introduces the concept of DevSecOps. It notes that traditional perimeter-based security is no longer sufficient given changes in applications and infrastructure. DevSecOps integrates security practices like training, requirements, threat modeling directly into the development pipeline from the beginning. This helps automate security testing and monitoring throughout the software development lifecycle and supply chain. When done right, DevSecOps helps create a "new Goldilocks zone" where security is no longer a bottleneck to rapid software development and deployment.

Divine and felonios cyber security devopsdays austin 2018John Willis

Devops - A Long Strange Trip It's BeenJohn Willis

DevopsdaysNYC - Almost 10 Years - What A Strange Long Trip It's BeenJohn Willis

You build it - Cyber Chicago KeynoteJohn Willis

This document provides an introduction to DevSecOps practices. It discusses how DevOps aims to accelerate software delivery through practices like continuous delivery, automation, and removing silos. It notes that security has become the new bottleneck in software delivery. DevSecOps aims to integrate security practices and tools into the software development pipeline to shift security left. This allows security to be addressed continuously throughout development and deployment rather than as a separate phase. The document outlines some DevSecOps basics like security training, threat modeling, and integrating static code analysis and vulnerability scanning into the CI/CD pipeline.

Art of the Possible - Serverless Conference NYC 2017 John Willis

This document discusses DevOps practices in a serverless world. It argues that DevOps is about humans, not technology, and focuses on creating high-performance organizations through practices like continuous delivery, embracing failure, and creating a culture of collaboration, automation, and measurement. The document presents DevOps concepts like lean production, just-in-time processes, and stopping production to fix problems as ways to achieve the goals of high quality, low cost, and short lead times. Data is presented showing organizations with strong DevOps practices see benefits like 30x more deployments, 60x higher success rates, and increased market performance. Creating generative organizations that can have speed, resilience and quality is framed as "the possible" that DevOps

Why Executives Can't Change John Willis

The document discusses why executives have difficulty changing strategies and processes, even when presented with compelling data showing alternatives would be better. It explains that organizations often fall into "bad equilibriums" where individually rational strategies combine to produce poor collective outcomes. This happens because organizations converge on processes that are faster, cheaper and better for each individual player, but do not optimize the desired outcomes of reliability, collaboration, risk management etc. for the organization as a whole. The document advocates using tools from "game theory" and "Lean" like value stream mapping to help executives understand these dynamics and make changes through techniques like establishing a "Dojo" for hands-on learning and coaching.

Devops Kaizen - DevopsDays Dallas 2017 John Willis

The document outlines a Devops Kaizen roadmap to continuously improve Devops capabilities. It involves assessing current capabilities, identifying improvement areas, and tracking key outcomes. A Devops retrospective process uses value stream mapping to identify inefficiencies and develop countermeasures. A Devops coach helps teach practices like continuous delivery. Experimental learning in a Dojo helps teams transform projects using Devops principles and tools. The goal is ongoing development of Devops skills and organizational capabilities through kata-style practice and coaching.

Evolve 2017 - Vegas - Devops, Docker and Security John Willis

This document discusses DevOps, Docker, and security. It begins by introducing the speaker and their background in DevOps. It then discusses how DevOps practices like continuous delivery, automation, and culture can make organizations 2000x faster. It introduces Docker and how it can make deployments more effective. Finally, it discusses how applying supply chain principles from Toyota, such as limiting variability and ensuring visibility, can make systems 100x more reliable when combined with Docker and immutable infrastructure.

Alibaba Cloud Conference 2016 - Docker Open Source John Willis

This document provides an overview of John Willis and his background in DevOps. It then discusses several DevOps practices and principles like continuous delivery, version control, and automating everything. The rest of the document focuses on Docker specifically, covering topics like the Docker ecosystem, platform, and commercial solutions. It also discusses Docker usage growth over time and opportunities in China.

Alibaba Cloud Conference 2016 - Docker EnterpriseJohn Willis

This document provides an overview of Docker and John Willis, including: 1. John Willis is the director of ecosystem development at Docker and has extensive experience in the DevOps field, including founding DevOps conferences and companies. 2. It discusses DevOps practices that Docker enables, like continuous delivery, version control, and automating everything. 3. Docker aims to eliminate friction in the development cycle by providing tools for mass innovation through a programmable internet and container platform.

Breaking Bad Equilibrium - Devops Connect 2017 RSACJohn Willis

The document discusses concepts from game theory, economics, and behavioral psychology including equilibrium, Pareto efficiency, Nash equilibrium, and cognitive biases. It argues that organizations can fall into a "bad equilibrium" similar to situations analyzed in game theory where outcomes are undesirable for all players due to things like technical debt, lack of cooperation, and burnout. To achieve better outcomes, the document advocates applying principles of devops such as increasing transparency, managing work in progress and flow, building high trust, and embracing failure to create a "devops advanced" equilibrium and learning organization.

Breaking Bad Equilibrium - Devops Connect 2016 LAJohn Willis

The document discusses concepts from game theory and behavioral economics including: - Bad equilibrium, where no player has an incentive to change their strategy despite undesirable outcomes for all - Nash equilibrium, where the optimal strategy for each player depends on the other players' strategies - Pareto efficiency and inefficiency, relating to situations where someone can be made better off without making others worse off It also discusses cognitive biases and human irrationality that can lead to suboptimal decisions, as highlighted by the work of Kahneman and Tversky, and suggests strategies like increasing visibility, flow management, and embracing failure to change equilibrium to a better outcome.

All daydevops 2016 - Turning Human Capital into High Performance Organizati...John Willis

The document discusses DevOps and how it can help turn an organization's human capital into high-performing capital through the use of certain practices and patterns. It notes that DevOps focuses on using practices like continuous delivery, automation, and breaking down silos to improve organizational performance. Data is presented showing that companies with high-performing DevOps teams see improvements like 30x more frequent deployments, 60x higher success rates of changes, and being 2x as likely to exceed business goals. The document advocates for taking a lean approach and building a safety culture and learning organization to fully realize the benefits of DevOps.

Automated GovernanceJohn Willis

Devops Long Strange Trip John Willis

I Got 99 Problems and a Bash DSL Ain't One of ThemJohn Willis

Math is coolJohn Willis

The 7 deadly diseases of DevOps 2019John Willis

Next Generation Infrastructure - Devops Enterprise Summit 2018John Willis

swampUP - 2018 - The Divine and Felonious Nature of Cyber SecurityJohn Willis

Divine and felonios cyber security devopsdays austin 2018John Willis

Devops - A Long Strange Trip It's BeenJohn Willis

DevopsdaysNYC - Almost 10 Years - What A Strange Long Trip It's BeenJohn Willis

You build it - Cyber Chicago KeynoteJohn Willis

Art of the Possible - Serverless Conference NYC 2017 John Willis

Why Executives Can't Change John Willis

Devops Kaizen - DevopsDays Dallas 2017 John Willis

Evolve 2017 - Vegas - Devops, Docker and Security John Willis

Alibaba Cloud Conference 2016 - Docker Open Source John Willis

Alibaba Cloud Conference 2016 - Docker EnterpriseJohn Willis

Breaking Bad Equilibrium - Devops Connect 2017 RSACJohn Willis

Breaking Bad Equilibrium - Devops Connect 2016 LAJohn Willis

All daydevops 2016 - Turning Human Capital into High Performance Organizati...John Willis

Recently uploaded (20)

Multi-currency in odoo accounting and Update exchange rates automatically in ...Celine George

SCI BIZ TECH QUIZ (OPEN) PRELIMS XTASY 2025.pptxRonisha Das

World war-1(Causes & impacts at a glance) PPT by Simanchala Sarab(BABed,sem-4...larencebapu132

YSPH VMOC Special Report - Measles Outbreak Southwest US 4-30-2025.pptxYale School of Public Health - The Virtual Medical Operations Center (VMOC)

A measles outbreak originating in West Texas has been linked to confirmed cases in New Mexico, with additional cases reported in Oklahoma and Kansas. The current case count is 795 from Texas, New Mexico, Oklahoma, and Kansas. 95 individuals have required hospitalization, and 3 deaths, 2 children in Texas and one adult in New Mexico. These fatalities mark the first measles-related deaths in the United States since 2015 and the first pediatric measles death since 2003. The YSPH Virtual Medical Operations Center Briefs (VMOC) were created as a service-learning project by faculty and graduate students at the Yale School of Public Health in response to the 2010 Haiti Earthquake. Each year, the VMOC Briefs are produced by students enrolled in Environmental Health Science Course 581 - Public Health Emergencies: Disaster Planning and Response. These briefs compile diverse information sources – including status reports, maps, news articles, and web content– into a single, easily digestible document that can be widely shared and used interactively. Key features of this report include: - Comprehensive Overview: Provides situation updates, maps, relevant news, and web resources. - Accessibility: Designed for easy reading, wide distribution, and interactive use. - Collaboration: The “unlocked" format enables other responders to share, copy, and adapt seamlessly. The students learn by doing, quickly discovering how and where to find critical information and presenting it in an easily understood manner.

Niamh Lucey, Mary Dunne. Health Sciences Libraries Group (LAI). Lighting the ...Library Association of Ireland

Geography Sem II Unit 1C Correlation of Geography with other school subjectsProfDrShaikhImran

Sinhala_Male_Names.pdf Sinhala_Male_Namekeshanf79

UNIT 3 NATIONAL HEALTH PROGRAMMEE. SOCIAL AND PREVENTIVE PHARMACYDR.PRISCILLA MARY J

GDGLSPGCOER - Git and GitHub Workshop.pptxazeenhodekar

YSPH VMOC Special Report - Measles Outbreak Southwest US 5-3-2025.pptxYale School of Public Health - The Virtual Medical Operations Center (VMOC)

A measles outbreak originating in West Texas has been linked to confirmed cases in New Mexico, with additional cases reported in Oklahoma and Kansas. The current case count is 817 from Texas, New Mexico, Oklahoma, and Kansas. 97 individuals have required hospitalization, and 3 deaths, 2 children in Texas and one adult in New Mexico. These fatalities mark the first measles-related deaths in the United States since 2015 and the first pediatric measles death since 2003. The YSPH Virtual Medical Operations Center Briefs (VMOC) were created as a service-learning project by faculty and graduate students at the Yale School of Public Health in response to the 2010 Haiti Earthquake. Each year, the VMOC Briefs are produced by students enrolled in Environmental Health Science Course 581 - Public Health Emergencies: Disaster Planning and Response. These briefs compile diverse information sources – including status reports, maps, news articles, and web content– into a single, easily digestible document that can be widely shared and used interactively. Key features of this report include: - Comprehensive Overview: Provides situation updates, maps, relevant news, and web resources. - Accessibility: Designed for easy reading, wide distribution, and interactive use. - Collaboration: The “unlocked" format enables other responders to share, copy, and adapt seamlessly. The students learn by doing, quickly discovering how and where to find critical information and presenting it in an easily understood manner. CURRENT CASE COUNT: 817 (As of 05/3/2025) • Texas: 688 (+20)(62% of these cases are in Gaines County). • New Mexico: 67 (+1 )(92.4% of the cases are from Eddy County) • Oklahoma: 16 (+1) • Kansas: 46 (32% of the cases are from Gray County) HOSPITALIZATIONS: 97 (+2) • Texas: 89 (+2) - This is 13.02% of all TX cases. • New Mexico: 7 - This is 10.6% of all NM cases. • Kansas: 1 - This is 2.7% of all KS cases. DEATHS: 3 • Texas: 2 – This is 0.31% of all cases • New Mexico: 1 – This is 1.54% of all cases US NATIONAL CASE COUNT: 967 (Confirmed and suspected): INTERNATIONAL SPREAD (As of 4/2/2025) • Mexico – 865 (+58) ‒Chihuahua, Mexico: 844 (+58) cases, 3 hospitalizations, 1 fatality • Canada: 1531 (+270) (This reflects Ontario's Outbreak, which began 11/24) ‒Ontario, Canada – 1243 (+223) cases, 84 hospitalizations. • Europe: 6,814

Phoenix – A Collaborative Renewal of Children’s and Young People’s Services C...Library Association of Ireland

To study the nervous system of insect.pptxArshad Shaikh

The *nervous system of insects* is a complex network of nerve cells (neurons) and supporting cells that process and transmit information. Here's an overview: Structure 1. *Brain*: The insect brain is a complex structure that processes sensory information, controls behavior, and integrates information. 2. *Ventral nerve cord*: A chain of ganglia (nerve clusters) that runs along the insect's body, controlling movement and sensory processing. 3. *Peripheral nervous system*: Nerves that connect the central nervous system to sensory organs and muscles. Functions 1. *Sensory processing*: Insects can detect and respond to various stimuli, such as light, sound, touch, taste, and smell. 2. *Motor control*: The nervous system controls movement, including walking, flying, and feeding. 3. *Behavioral responThe *nervous system of insects* is a complex network of nerve cells (neurons) and supporting cells that process and transmit information. Here's an overview: Structure 1. *Brain*: The insect brain is a complex structure that processes sensory information, controls behavior, and integrates information. 2. *Ventral nerve cord*: A chain of ganglia (nerve clusters) that runs along the insect's body, controlling movement and sensory processing. 3. *Peripheral nervous system*: Nerves that connect the central nervous system to sensory organs and muscles. Functions 1. *Sensory processing*: Insects can detect and respond to various stimuli, such as light, sound, touch, taste, and smell. 2. *Motor control*: The nervous system controls movement, including walking, flying, and feeding. 3. *Behavioral responses*: Insects can exhibit complex behaviors, such as mating, foraging, and social interactions. Characteristics 1. *Decentralized*: Insect nervous systems have some autonomy in different body parts. 2. *Specialized*: Different parts of the nervous system are specialized for specific functions. 3. *Efficient*: Insect nervous systems are highly efficient, allowing for rapid processing and response to stimuli. The insect nervous system is a remarkable example of evolutionary adaptation, enabling insects to thrive in diverse environments. The insect nervous system is a remarkable example of evolutionary adaptation, enabling insects to thrive

To study Digestive system of insect.pptxArshad Shaikh

The ever evoilving world of science /7th class science curiosity /samyans aca...Sandeep Swamy

The Ever-Evolving World of Science Welcome to Grade 7 Science4not just a textbook with facts, but an invitation to question, experiment, and explore the beautiful world we live in. From tiny cells inside a leaf to the movement of celestial bodies, from household materials to underground water flows, this journey will challenge your thinking and expand your knowledge. Notice something special about this book? The page numbers follow the playful flight of a butterfly and a soaring paper plane! Just as these objects take flight, learning soars when curiosity leads the way. Simple observations, like paper planes, have inspired scientific explorations throughout history.

Social Problem-Unemployment .pptx notes for Physiotherapy StudentsDrNidhiAgarwal

Unemployment is a major social problem, by which not only rural population have suffered but also urban population are suffered while they are literate having good qualification.The evil consequences like poverty, frustration, revolution result in crimes and social disorganization. Therefore, it is necessary that all efforts be made to have maximum. employment facilities. The Government of India has already announced that the question of payment of unemployment allowance cannot be considered in India

Michelle Rumley & Mairéad Mooney, Boole Library, University College Cork. Tra...Library Association of Ireland

Anti-Depressants pharmacology 1slide.pptxMayuri Chavan

CBSE - Grade 8 - Science - Chemistry - Metals and Non Metals - WorksheetSritoma Majumder

Introduction All the materials around us are made up of elements. These elements can be broadly divided into two major groups: Metals Non-Metals Each group has its own unique physical and chemical properties. Let's understand them one by one. Physical Properties 1. Appearance Metals: Shiny (lustrous). Example: gold, silver, copper. Non-metals: Dull appearance (except iodine, which is shiny). 2. Hardness Metals: Generally hard. Example: iron. Non-metals: Usually soft (except diamond, a form of carbon, which is very hard). 3. State Metals: Mostly solids at room temperature (except mercury, which is a liquid). Non-metals: Can be solids, liquids, or gases. Example: oxygen (gas), bromine (liquid), sulphur (solid). 4. Malleability Metals: Can be hammered into thin sheets (malleable). Non-metals: Not malleable. They break when hammered (brittle). 5. Ductility Metals: Can be drawn into wires (ductile). Non-metals: Not ductile. 6. Conductivity Metals: Good conductors of heat and electricity. Non-metals: Poor conductors (except graphite, which is a good conductor). 7. Sonorous Nature Metals: Produce a ringing sound when struck. Non-metals: Do not produce sound. Chemical Properties 1. Reaction with Oxygen Metals react with oxygen to form metal oxides. These metal oxides are usually basic. Non-metals react with oxygen to form non-metallic oxides. These oxides are usually acidic. 2. Reaction with Water Metals: Some react vigorously (e.g., sodium). Some react slowly (e.g., iron). Some do not react at all (e.g., gold, silver). Non-metals: Generally do not react with water. 3. Reaction with Acids Metals react with acids to produce salt and hydrogen gas. Non-metals: Do not react with acids. 4. Reaction with Bases Some non-metals react with bases to form salts, but this is rare. Metals generally do not react with bases directly (except amphoteric metals like aluminum and zinc). Displacement Reaction More reactive metals can displace less reactive metals from their salt solutions. Uses of Metals Iron: Making machines, tools, and buildings. Aluminum: Used in aircraft, utensils. Copper: Electrical wires. Gold and Silver: Jewelry. Zinc: Coating iron to prevent rusting (galvanization). Uses of Non-Metals Oxygen: Breathing. Nitrogen: Fertilizers. Chlorine: Water purification. Carbon: Fuel (coal), steel-making (coke). Iodine: Medicines. Alloys An alloy is a mixture of metals or a metal with a non-metal. Alloys have improved properties like strength, resistance to rusting.

How to track Cost and Revenue using Analytic Accounts in odoo Accounting, App...Celine George

Analytic accounts are used to track and manage financial transactions related to specific projects, departments, or business units. They provide detailed insights into costs and revenues at a granular level, independent of the main accounting system. This helps to better understand profitability, performance, and resource allocation, making it easier to make informed financial decisions and strategic planning.

One Hot encoding a revolution in Machine learningmomer9505

Multi-currency in odoo accounting and Update exchange rates automatically in ...Celine George

SCI BIZ TECH QUIZ (OPEN) PRELIMS XTASY 2025.pptxRonisha Das

World war-1(Causes & impacts at a glance) PPT by Simanchala Sarab(BABed,sem-4...larencebapu132

YSPH VMOC Special Report - Measles Outbreak Southwest US 4-30-2025.pptxYale School of Public Health - The Virtual Medical Operations Center (VMOC)

Niamh Lucey, Mary Dunne. Health Sciences Libraries Group (LAI). Lighting the ...Library Association of Ireland

Geography Sem II Unit 1C Correlation of Geography with other school subjectsProfDrShaikhImran

Sinhala_Male_Names.pdf Sinhala_Male_Namekeshanf79

UNIT 3 NATIONAL HEALTH PROGRAMMEE. SOCIAL AND PREVENTIVE PHARMACYDR.PRISCILLA MARY J

GDGLSPGCOER - Git and GitHub Workshop.pptxazeenhodekar

YSPH VMOC Special Report - Measles Outbreak Southwest US 5-3-2025.pptxYale School of Public Health - The Virtual Medical Operations Center (VMOC)

Phoenix – A Collaborative Renewal of Children’s and Young People’s Services C...Library Association of Ireland

To study the nervous system of insect.pptxArshad Shaikh

To study Digestive system of insect.pptxArshad Shaikh

The ever evoilving world of science /7th class science curiosity /samyans aca...Sandeep Swamy

Social Problem-Unemployment .pptx notes for Physiotherapy StudentsDrNidhiAgarwal

Michelle Rumley & Mairéad Mooney, Boole Library, University College Cork. Tra...Library Association of Ireland

Anti-Depressants pharmacology 1slide.pptxMayuri Chavan

CBSE - Grade 8 - Science - Chemistry - Metals and Non Metals - WorksheetSritoma Majumder

How to track Cost and Revenue using Analytic Accounts in odoo Accounting, App...Celine George

One Hot encoding a revolution in Machine learningmomer9505

Devops and Immutable infrastructure - Cloud Expo 2015 NYC

1. @bglpe Devops and Immutable Infrastructure John Wills! Technical Evangelist

2. @bglpe @botchagalupe • a.k.a. John Willis • 35 Years in IT Operations • Exxon, Canonical, Chef, Enstratius, Socketplane • Devopsdays Core Organizer • Devopscafe on iTunes • Tweet to @bglpe for Questions

3. @bglpe Agenda • What is Immutable Infrastructure? • Why Immutable (Order Matters) • Models and Methods • Docker and Immutable Infrastructure • Case Studies

4. @bglpe

5. @bglpe Immutable Infrastructure Myth

6. @bglpe “The least-cost way to ensure that the behavior of any two hosts will remain completely identical is always to implement the same changes in the same order on both hosts.” Order Matters

7. @bglpe Management Methods • Divergence • Convergence • Congruence

8. @bglpe Why (When) Does Order Matter? • Circular Dependancies • Right Command Wrong Order • Right Package Wrong Order

9. @bglpe Package Example

10. @bglpe Immutable Infrastructure “Model” • No CRUD allowed for… • Packages • Conﬁguration Files • Application Software • Data (RUD)

11. @bglpe How To Do Immutable? • Provision a new server. • Test the new server. • Change the reference to the new server. • Keep the old server around for rollback.

12. @bglpe The Immutable “Trombone” • Golden Images • Virtual Desktop Infrastructure (VDI) • Virtual Images • Phoenix Servers vs Snowﬂake Servers • Infrastructure as Code • Bake vs Fry • Containers

13. @bglpe

14. @bglpe Why Docker? • Isolation • Lightweight • Simplicity • Workﬂow • Community

15. @bglpe Docker Community • 1200 Docker Contributors • 100,000 Dockerized Applications • 3 to 4 Million Developers using Docker • 300 Million Downloads • 32,000 Docker Related Projects • 70% of enterprises are using Docker

16. @bglpe Case Studies

17. @bglpe Case Studies

18. @bglpe References Docker and the Three Ways of Devops! https://blog.docker.com/2015/05/docker-three-ways-ops/! ! Trash Your Servers and Burn Your Code: Immutable Infrastructure and Disposable Components! Chad Fowler June 2013! http://chadfowler.com/blog/2013/06/23/immutable-deployments/! ! PhoenixServer! Martin Fowler July 2012! http://martinfowler.com/bliki/PhoenixServer.html! ! Building with Legos! http://techblog.netﬂix.com/2011/08/building-with-legos.html! ! Immutable Infrastructure with Docker and EC2": Gilt at Dockercon (Video)! http://tech.gilt.com/post/90578399884/immutable-infrastructure-with-docker-and-ec2! ! Why you should build an Immutable Infrastructure! by Florian Motlik - 2014-07-22! https://blog.codeship.com/immutable-infrastructure/! ! Baked Servers vs Fried Servers! http://if.andonlyif.net/blog/2012/10/baked-servers-vs-fried-servers.html! ! Why Order Matters: Turing Equivalence in Automated Systems Administration! https://www.usenix.org/legacy/publications/library/proceedings/lisa02/tech/full_papers/traugott/traugott_html/index.html! ! An Analysis of RPM Validation Drift! https://www.usenix.org/legacy/events/lisa2002/tech/full_papers/hart/hart.pdf!

19. @bglpe [email protected] @botchagalupe

Devops and Immutable infrastructure - Cloud Expo 2015 NYC

Recommended

More Related Content

What's hot (20)

Viewers also liked (20)

Similar to Devops and Immutable infrastructure - Cloud Expo 2015 NYC (20)

More from John Willis (20)

Recently uploaded (20)

Devops and Immutable infrastructure - Cloud Expo 2015 NYC