Your Goat Antifragiled My Snowflake!: Demystifying DevOps Jargon - ChefConf 2015Chef
From ChefConf 2015.
https://youtu.be/OU3F_UU-Jpc
Are you a cow, a pet, a canary, or a unicorn? Do you prefer blue/green, or red/green/refactor? Who the heck is Brent?
Welcome to DevOps, where we are all about breaking down walls. But, we've created a private dialect, full of familiar words with unfamiliar meanings, and in-jokes upon in-jokes. Many newcomers wish there was a glossary for the movement. Time to be inclusive!
In this fun session, we'll go over some of the more unintuitive terms (being a goat is a good thing!) and the backstories behind them. We'll have an extended audience participation segment in which you can ask about words you've heard.
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.
Using software modules today is the default way of working for most systems and frameworks. With the advent of many software languages and OSS frameworks, new module systems are constantly created and new module ecosystems start to prevail. This trend is horizontal and covers operating system packages, language libraries and application modules (plugins). But while some module systems are nicer to use, others are repeating past mistakes and are a daily source for developer agony and pain. In this short talk I will present the \"lessons learned\" at JFrog, where we make software for managing software libraries and deal with many types of module systems. This talk will show what works and what doesn\'t work in a module system; what features can make a module ecosystem thrive or fail; and why, despite all downsides, modules are here to stay and conquer more space as the Cloud continues to grow.
Scratching the itch, making Scratch for the Raspberry PieESUG
Title: Scratching the itch, making Scratch for the Raspberry Pie
Speaker: Tim Rowledge
Fri, August 22, 12:00pm – 12:30pm
Abstract: Scratch was originally written in a Squeak 2.8 era image. Much has changed since then and to make the Raspberry Pi run Scratch as well as possible we have ported the code forward to a 4.5 image so it can run on a StackVM; and soon a Cog VM. A substantial amount of Smalltalk code has had to be rewritten to do this and yet we have to maintain complete compatibility with the original system to avoid overloading the teachers that use it in their classes. A new branch of Cog for the ARM cpu is being written as well.
Bio: Tim Rowledge has almost 30 years of Smalltalk experience, and almost as much with ARM. Somehow the two have always gone together.
Test driven infrastructure development (2 - puppetconf 2013 edition)Tomas Doran
The document discusses test driven infrastructure development. It describes issues with the current state where infrastructure changes are not repeatable and difficult to test. The speaker proposes modeling infrastructure as code where environments are defined programmatically and configuration is generated externally rather than defined directly in puppet code. This allows for entire environments to be provisioned on demand and tested in an automated and repeatable way. Key benefits include high availability, ability to test all infrastructure changes, fully repeatable environments, high confidence in changes, and continuous integration/deployment of infrastructure.
Embracing Failure - Fault Injection and Service Resilience at NetflixJosh Evans
A presentation given at AWS re:Invent on how Netflix induces failure to validate and harden production systems. Technologies discussed include the Simian Army (Chaos Monkey, Gorilla, Kong) and our next gen Failure Injection Test framework (FIT).
This is my noob recap of KubeCon 2019, which I transformed into a kubernetes bootcamp. I walked away with a bunch of learnings, so here they are for you :)
Your Goat Antifragiled My Snowflake!: Demystifying DevOps Jargon - ChefConf 2015Chef
From ChefConf 2015.
https://youtu.be/OU3F_UU-Jpc
Are you a cow, a pet, a canary, or a unicorn? Do you prefer blue/green, or red/green/refactor? Who the heck is Brent?
Welcome to DevOps, where we are all about breaking down walls. But, we've created a private dialect, full of familiar words with unfamiliar meanings, and in-jokes upon in-jokes. Many newcomers wish there was a glossary for the movement. Time to be inclusive!
In this fun session, we'll go over some of the more unintuitive terms (being a goat is a good thing!) and the backstories behind them. We'll have an extended audience participation segment in which you can ask about words you've heard.
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.
Using software modules today is the default way of working for most systems and frameworks. With the advent of many software languages and OSS frameworks, new module systems are constantly created and new module ecosystems start to prevail. This trend is horizontal and covers operating system packages, language libraries and application modules (plugins). But while some module systems are nicer to use, others are repeating past mistakes and are a daily source for developer agony and pain. In this short talk I will present the \"lessons learned\" at JFrog, where we make software for managing software libraries and deal with many types of module systems. This talk will show what works and what doesn\'t work in a module system; what features can make a module ecosystem thrive or fail; and why, despite all downsides, modules are here to stay and conquer more space as the Cloud continues to grow.
Scratching the itch, making Scratch for the Raspberry PieESUG
Title: Scratching the itch, making Scratch for the Raspberry Pie
Speaker: Tim Rowledge
Fri, August 22, 12:00pm – 12:30pm
Abstract: Scratch was originally written in a Squeak 2.8 era image. Much has changed since then and to make the Raspberry Pi run Scratch as well as possible we have ported the code forward to a 4.5 image so it can run on a StackVM; and soon a Cog VM. A substantial amount of Smalltalk code has had to be rewritten to do this and yet we have to maintain complete compatibility with the original system to avoid overloading the teachers that use it in their classes. A new branch of Cog for the ARM cpu is being written as well.
Bio: Tim Rowledge has almost 30 years of Smalltalk experience, and almost as much with ARM. Somehow the two have always gone together.
Test driven infrastructure development (2 - puppetconf 2013 edition)Tomas Doran
The document discusses test driven infrastructure development. It describes issues with the current state where infrastructure changes are not repeatable and difficult to test. The speaker proposes modeling infrastructure as code where environments are defined programmatically and configuration is generated externally rather than defined directly in puppet code. This allows for entire environments to be provisioned on demand and tested in an automated and repeatable way. Key benefits include high availability, ability to test all infrastructure changes, fully repeatable environments, high confidence in changes, and continuous integration/deployment of infrastructure.
Embracing Failure - Fault Injection and Service Resilience at NetflixJosh Evans
A presentation given at AWS re:Invent on how Netflix induces failure to validate and harden production systems. Technologies discussed include the Simian Army (Chaos Monkey, Gorilla, Kong) and our next gen Failure Injection Test framework (FIT).
This is my noob recap of KubeCon 2019, which I transformed into a kubernetes bootcamp. I walked away with a bunch of learnings, so here they are for you :)
Heroku uses Heroku to build Heroku. It has over 5000 apps, 500+ releases and 200+ deploys per day across 21 teams. Teams use various tools like Github, Trello, Campfire. Quality is ensured by hiring for quality and culture, giving engineers time without deadlines. Small autonomous teams provide quality, ownership, productivity and agility. Heroku enables continuous deployment by having a defined API, parity across environments from dev to prod, and apps that do one thing well with straightforward setup and low barriers.
This document discusses the Go programming language. It provides an overview of what Go is, including that it is open source, concurrent, garbage collected, efficient, scalable, and simple. It discusses the origins and evolution of Go from 2007 to present. Key people who created Go are named. The document discusses design decisions in Go including using structs over classes, functions over constructors, multiple returns over out parameters, and composition over inheritance. Error handling, concurrency using goroutines and channels, and adoption success stories are also summarized.
How to set up continuous delivery in 15 minutes if you really need it but you don't know anything about it (my case). Talk on Sloboda studio edu session.
'Intro to Infrastructure as Code' - DevOps BelfastJohn Fitzpatrick
This document provides an introduction to infrastructure as code and Chef. It discusses how infrastructure as code treats infrastructure configuration like code that can be version controlled, tested, and managed declaratively. It then introduces Chef concepts like resources, recipes, cookbooks, and how they allow defining infrastructure in a declarative way using Ruby DSL. The document uses examples like package, file, template and service resources to illustrate how Chef models infrastructure as code.
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.
Big Data! Great! Now What? #SymfonyCon 2014Ricard Clau
Big Data is one of the new buzzwords in the industry. Everyone is using NoSQL databases. MySQL is not cool anymore. But... do we really have big data? Where should we store it? Are the traditional RDBMS databases dead? Is NoSQL the solution to our problems? And most importantly, how can PHP and Symfony2 help with it?
Deploying distributed software services to the cloud without breaking a sweatSusan Potter
The document contains the output of multiple "finger" commands run on the user "susan". It shows Susan Potter is logged in from tty1 and has been on since 1997. It also lists her home directory, shell, and social media accounts. The remaining content discusses the scope of a talk and covers various DevOps and cloud computing topics at a high-level, including delivery models, characteristics, definitions, deployment pipelines, bottlenecks, and automation approaches.
OHOH is an iOS social networking app like Meetup.com but for smaller groups. It allows private and group chats, likes, comments, and uses push notifications. The app was originally developed using Objective-C, CocoaPods, AFNetworking, and Parse for push notifications. It has since switched to using Layer for chat functionality due to issues with Firebase and additional chat features. The developer discusses experiences with various technologies used in the app's development.
Startup Architecture: How to Lean on Others to Get Stuff DoneUntitledC4Media
The document provides an overview of InfoQ.com, a news and community site for software developers. It discusses InfoQ's content, which includes news articles, presentations, interviews and books. It also discusses QCon, a practitioner-driven conference organized by InfoQ. QCon is designed for influencers in software development and has been held in 9 cities worldwide, attracting over 12,000 delegates since 2007. The purpose of QCon is to empower software development by facilitating the spread of knowledge and innovation.
This is a talk given by Jason Hoffman at a workshop given by Joyent called "Scale With Rails" in 2006. There's quite a bit of prescience in this presentation, including the first documented use of ZFS in production ("Fsck you if you think ZFS isn't production") and of OS-based virtualization (zones) in the cloud (which, it must be said, was not called "cloud" in 2006).
Continuous delivery is an agile methodology that aims to reduce the cost, time, and risk of delivering software by frequently releasing small, incremental changes. The key goals are to continuously build the right features, reduce lead time, reduce costs through optimization and automation, and reduce risk through resilience and small increments. Continuous delivery utilizes a deployment pipeline to fully automate building, deploying, testing and releasing software. This allows organizations to reliably deliver changes involving a single line of code. It also reduces risk by failing fast and treating every version as a release candidate. Continuous delivery challenges teams to avoid anti-patterns like code freezes, manual processes, and exceptions to the pipeline for releases.
Combining R With Java For Data Analysis (Devoxx UK 2015 Session)Ryan Cuprak
Java is a general-purpose language and is not particularly well suited for performing statistical analysis. Special languages and software environments have been created by and for statisticians to use. Statisticians think about programming and data analysis much different from Java programmers. These languages and tools make it easy to perform very sophisticated analyses on large data sets easily. Tools, such as R and SAS, contain a large toolbox of statistical tools that are well tested, documented and validated. For data analysis you want to use these tools.
In this session we will provide an overview of how to leverage the power of R from Java. R is the leading open source statistical package/language/environment. The first part of the presentation will provide an overview of R focusing on the differences between R and Java at the language level. We’ll also look at some of the basic and more advanced tests to illustrate the power of R. The second half of the presentation will cover how to integrate R and Java using rJava. We’ll look at leverage R from the new Java EE Batching (JSR 352) to provide robust statistical analysis for enterprise applications.
From vagrant to production - Mark EijsermansDevopsdays
This document discusses the evolution of HootSuite's development and operations processes over several years as the company grew. It begins with a small co-located team that could release to production anytime with low overhead. It progresses to larger distributed teams releasing every 2-4 weeks through a more complicated process. The current process involves 6-10 releases per day through automation and practices like infrastructure as code that allow anyone to deploy. Key steps along the way included adopting Vagrant for development environments, implementing continuous integration and delivery pipelines, and moving to a microservices architecture.
Maintaining reliability in an unreliable worldJeremy Edberg
The document discusses maintaining reliability in an unreliable world. It talks about how Netflix moved to the cloud to scale with growing demand and gain redundancy beyond their two datacenters. The document advocates building systems with redundancy from the start, preferably with 3 or more components, to survive failures. It also discusses caching, database sharding, and monitoring systems used by Reddit and Netflix to detect and mitigate issues.
Getting a Neural Network Up and Running with OpenLabMelvin Hillsman
Access to hardware for AI/ML for the everyday developer wanting to explore this field can be challenging to obtain and maintain for even the most rudimentary applications and testing. Needing to go beyond a single development machine running locally only increases this. OpenLab is curated infrastructure accessible to open source projects and individuals working within and on open source projects designed to help address this use case. Access to GPU, FPGA, IoT, and more, allows HPC, AI/ML, Deep Learning, or other testing and applications. In this presentation, we will walk through getting an account with OpenLab, obtaining resources, and getting a neural network up and running with an app that will bring back great childhood memories.
This document discusses debugging microservices in production environments. It begins by providing context on the history of debugging and introduces some common anti-patterns in debugging. It then argues that debugging should be approached methodically using the scientific method. The document outlines a method for debugging software called the software debugging method. Finally, it discusses challenges that arise in debugging microservices due to their distributed nature and argues that containers can help address these challenges.
The document discusses the DevOpsSec approach which aims to integrate security testing into the development process through automation. It outlines how DevOpsSec can help address issues that arise from the traditional separation of development and operations teams. The document provides examples of different types of tests that can be automated, such as unit testing, performance testing, and security testing of an application's attack surface. It promotes automating as many tests as possible and sharing test automation code to continuously monitor for vulnerabilities and issues.
Engineering Netflix Global Operations in the CloudJosh Evans
Delivered at re:Invent 2015.
Operating a massively scalable, constantly changing, distributed global service is a daunting task. We innovate at breakneck speed to attract new customers and stay ahead of the competition. This means more features, more experiments, more deployments, more engineers making changes in production environments, and ever-increasing complexity. Simultaneously improving service availability and accelerating rate of change seems impossible on the surface. At Netflix, operations engineering is both a technical and organizational construct designed to accomplish just that by integrating disciplines like continuous delivery, fault injection, regional traffic management, crisis response, best practice automation, and real-time analytics. In this talk, designed for technical leaders seeking a path to operational excellence, we'll explore these disciplines in depth and how they integrate and create competitive advantages.
Debugging under fire: Keeping your head when systems have lost their mindbcantrill
This document discusses debugging complex distributed systems during outages. It argues that debugging should be viewed not just as fixing bugs but understanding systems to improve them. Debugging requires balancing recovery and understanding during outages. Software should be designed for debuggability through instrumentation, diagnostics, and avoiding patterns that impede understanding failures. Outages provide opportunities to advance knowledge, and a culture that values debuggability leads to more robust software.
PHP performance 101: so you need to use a databaseLeon Fayer
Being involved in performance audits on systems of every size, from start-up sites hacked together overnight, to a ginormous applications built by world-recognized brand companies, I’ve seen a lot of interesting (and sometimes very unique) performance issues in every level of the stack: code, architecture, databases (sometimes all of the above). But there are a few particular, very “Performance 101″, issues that (unfortunately) appear in a lot of code bases. In this talk I present the most common database-related performance bottlenecks that can happen in most PHP applications.
Heroku uses Heroku to build Heroku. It has over 5000 apps, 500+ releases and 200+ deploys per day across 21 teams. Teams use various tools like Github, Trello, Campfire. Quality is ensured by hiring for quality and culture, giving engineers time without deadlines. Small autonomous teams provide quality, ownership, productivity and agility. Heroku enables continuous deployment by having a defined API, parity across environments from dev to prod, and apps that do one thing well with straightforward setup and low barriers.
This document discusses the Go programming language. It provides an overview of what Go is, including that it is open source, concurrent, garbage collected, efficient, scalable, and simple. It discusses the origins and evolution of Go from 2007 to present. Key people who created Go are named. The document discusses design decisions in Go including using structs over classes, functions over constructors, multiple returns over out parameters, and composition over inheritance. Error handling, concurrency using goroutines and channels, and adoption success stories are also summarized.
How to set up continuous delivery in 15 minutes if you really need it but you don't know anything about it (my case). Talk on Sloboda studio edu session.
'Intro to Infrastructure as Code' - DevOps BelfastJohn Fitzpatrick
This document provides an introduction to infrastructure as code and Chef. It discusses how infrastructure as code treats infrastructure configuration like code that can be version controlled, tested, and managed declaratively. It then introduces Chef concepts like resources, recipes, cookbooks, and how they allow defining infrastructure in a declarative way using Ruby DSL. The document uses examples like package, file, template and service resources to illustrate how Chef models infrastructure as code.
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.
Big Data! Great! Now What? #SymfonyCon 2014Ricard Clau
Big Data is one of the new buzzwords in the industry. Everyone is using NoSQL databases. MySQL is not cool anymore. But... do we really have big data? Where should we store it? Are the traditional RDBMS databases dead? Is NoSQL the solution to our problems? And most importantly, how can PHP and Symfony2 help with it?
Deploying distributed software services to the cloud without breaking a sweatSusan Potter
The document contains the output of multiple "finger" commands run on the user "susan". It shows Susan Potter is logged in from tty1 and has been on since 1997. It also lists her home directory, shell, and social media accounts. The remaining content discusses the scope of a talk and covers various DevOps and cloud computing topics at a high-level, including delivery models, characteristics, definitions, deployment pipelines, bottlenecks, and automation approaches.
OHOH is an iOS social networking app like Meetup.com but for smaller groups. It allows private and group chats, likes, comments, and uses push notifications. The app was originally developed using Objective-C, CocoaPods, AFNetworking, and Parse for push notifications. It has since switched to using Layer for chat functionality due to issues with Firebase and additional chat features. The developer discusses experiences with various technologies used in the app's development.
Startup Architecture: How to Lean on Others to Get Stuff DoneUntitledC4Media
The document provides an overview of InfoQ.com, a news and community site for software developers. It discusses InfoQ's content, which includes news articles, presentations, interviews and books. It also discusses QCon, a practitioner-driven conference organized by InfoQ. QCon is designed for influencers in software development and has been held in 9 cities worldwide, attracting over 12,000 delegates since 2007. The purpose of QCon is to empower software development by facilitating the spread of knowledge and innovation.
This is a talk given by Jason Hoffman at a workshop given by Joyent called "Scale With Rails" in 2006. There's quite a bit of prescience in this presentation, including the first documented use of ZFS in production ("Fsck you if you think ZFS isn't production") and of OS-based virtualization (zones) in the cloud (which, it must be said, was not called "cloud" in 2006).
Continuous delivery is an agile methodology that aims to reduce the cost, time, and risk of delivering software by frequently releasing small, incremental changes. The key goals are to continuously build the right features, reduce lead time, reduce costs through optimization and automation, and reduce risk through resilience and small increments. Continuous delivery utilizes a deployment pipeline to fully automate building, deploying, testing and releasing software. This allows organizations to reliably deliver changes involving a single line of code. It also reduces risk by failing fast and treating every version as a release candidate. Continuous delivery challenges teams to avoid anti-patterns like code freezes, manual processes, and exceptions to the pipeline for releases.
Combining R With Java For Data Analysis (Devoxx UK 2015 Session)Ryan Cuprak
Java is a general-purpose language and is not particularly well suited for performing statistical analysis. Special languages and software environments have been created by and for statisticians to use. Statisticians think about programming and data analysis much different from Java programmers. These languages and tools make it easy to perform very sophisticated analyses on large data sets easily. Tools, such as R and SAS, contain a large toolbox of statistical tools that are well tested, documented and validated. For data analysis you want to use these tools.
In this session we will provide an overview of how to leverage the power of R from Java. R is the leading open source statistical package/language/environment. The first part of the presentation will provide an overview of R focusing on the differences between R and Java at the language level. We’ll also look at some of the basic and more advanced tests to illustrate the power of R. The second half of the presentation will cover how to integrate R and Java using rJava. We’ll look at leverage R from the new Java EE Batching (JSR 352) to provide robust statistical analysis for enterprise applications.
From vagrant to production - Mark EijsermansDevopsdays
This document discusses the evolution of HootSuite's development and operations processes over several years as the company grew. It begins with a small co-located team that could release to production anytime with low overhead. It progresses to larger distributed teams releasing every 2-4 weeks through a more complicated process. The current process involves 6-10 releases per day through automation and practices like infrastructure as code that allow anyone to deploy. Key steps along the way included adopting Vagrant for development environments, implementing continuous integration and delivery pipelines, and moving to a microservices architecture.
Maintaining reliability in an unreliable worldJeremy Edberg
The document discusses maintaining reliability in an unreliable world. It talks about how Netflix moved to the cloud to scale with growing demand and gain redundancy beyond their two datacenters. The document advocates building systems with redundancy from the start, preferably with 3 or more components, to survive failures. It also discusses caching, database sharding, and monitoring systems used by Reddit and Netflix to detect and mitigate issues.
Getting a Neural Network Up and Running with OpenLabMelvin Hillsman
Access to hardware for AI/ML for the everyday developer wanting to explore this field can be challenging to obtain and maintain for even the most rudimentary applications and testing. Needing to go beyond a single development machine running locally only increases this. OpenLab is curated infrastructure accessible to open source projects and individuals working within and on open source projects designed to help address this use case. Access to GPU, FPGA, IoT, and more, allows HPC, AI/ML, Deep Learning, or other testing and applications. In this presentation, we will walk through getting an account with OpenLab, obtaining resources, and getting a neural network up and running with an app that will bring back great childhood memories.
This document discusses debugging microservices in production environments. It begins by providing context on the history of debugging and introduces some common anti-patterns in debugging. It then argues that debugging should be approached methodically using the scientific method. The document outlines a method for debugging software called the software debugging method. Finally, it discusses challenges that arise in debugging microservices due to their distributed nature and argues that containers can help address these challenges.
The document discusses the DevOpsSec approach which aims to integrate security testing into the development process through automation. It outlines how DevOpsSec can help address issues that arise from the traditional separation of development and operations teams. The document provides examples of different types of tests that can be automated, such as unit testing, performance testing, and security testing of an application's attack surface. It promotes automating as many tests as possible and sharing test automation code to continuously monitor for vulnerabilities and issues.
Engineering Netflix Global Operations in the CloudJosh Evans
Delivered at re:Invent 2015.
Operating a massively scalable, constantly changing, distributed global service is a daunting task. We innovate at breakneck speed to attract new customers and stay ahead of the competition. This means more features, more experiments, more deployments, more engineers making changes in production environments, and ever-increasing complexity. Simultaneously improving service availability and accelerating rate of change seems impossible on the surface. At Netflix, operations engineering is both a technical and organizational construct designed to accomplish just that by integrating disciplines like continuous delivery, fault injection, regional traffic management, crisis response, best practice automation, and real-time analytics. In this talk, designed for technical leaders seeking a path to operational excellence, we'll explore these disciplines in depth and how they integrate and create competitive advantages.
Debugging under fire: Keeping your head when systems have lost their mindbcantrill
This document discusses debugging complex distributed systems during outages. It argues that debugging should be viewed not just as fixing bugs but understanding systems to improve them. Debugging requires balancing recovery and understanding during outages. Software should be designed for debuggability through instrumentation, diagnostics, and avoiding patterns that impede understanding failures. Outages provide opportunities to advance knowledge, and a culture that values debuggability leads to more robust software.
PHP performance 101: so you need to use a databaseLeon Fayer
Being involved in performance audits on systems of every size, from start-up sites hacked together overnight, to a ginormous applications built by world-recognized brand companies, I’ve seen a lot of interesting (and sometimes very unique) performance issues in every level of the stack: code, architecture, databases (sometimes all of the above). But there are a few particular, very “Performance 101″, issues that (unfortunately) appear in a lot of code bases. In this talk I present the most common database-related performance bottlenecks that can happen in most PHP applications.
One of the major risks when implementing a third party service is the reliance on the availability of that third party service. The service that you have no control over. And no matter how large or successful the service that you’re using is – it will go down at one point or another. This talk is intended to give a real-world disaster example of heavy integration with external social network and practical tips to mitigate or avoid similar issues.
Improving DevOps through better monitoringLeon Fayer
Leon Fayer discusses how monitoring is a key part of DevOps and improving systems. He outlines what aspects systems, applications, databases, and business processes should be monitored. Fayer then provides a case study example of how one company traced a revenue issue to a problem with their email system by taking a top-down approach and correlating multiple metrics from traffic down through load time, databases, and email. Fayer emphasizes understanding the business and correlating different types of data to effectively monitor complex systems.
Being involved in performance audits on systems of every size, from start-up sites hacked together overnight, to a ginormous applications built by world-recognized brand companies, I’ve seen a lot of interesting (and sometimes very unique) performance issues in every level of the stack: code, architecture, databases (sometimes all of the above). But there are a few particular, very “Performance 101″, issues that (unfortunately) appear in a lot of code bases. In this talk I'll present the most common database-related performance bottlenecks that can happen in most applications.
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.
The challenge of application distribution - Introduction to Docker (2014 dec ...Sébastien Portebois
Live recording with the demos: https://www.youtube.com/watch?v=0XRcmJEiZOM
Contents
- The application distribution challenge
- The current solutions
- Introduction to Docker, Containers, and the Matrix from Hell
- Why people care: Separation of Concerns
- Technical Discussion
- Ecosystem, momentum
- How to build Docker images
- How to make containers talk to each other, how to handle data persistence
- Demo 1: isolation
- Demo 2: real case - installing Go Math! Academy, tail –f containers, unit tests
This document discusses developing a Go runtime for Apache OpenWhisk to improve upon the existing DockerSkeleton approach. The key points are:
1) The current DockerSkeleton approach has some limitations like being fragile and having potential race conditions.
2) The new design keeps the Python proxy but uses a Go executable that runs as a Unix command, reading input and writing output on stdin/stdout/stderr.
3) An initial implementation has been done in a GitHub repository replacing DockerSkeleton with a Go server and refactoring to a piped loop. Testing with a Swift executable showed promising performance improvements over DockerSkeleton.
Hey curious friend, let's play a game. How can we bring together two different companies, an established enterprise with traditional dev and ops having cultural differences when working together with a DevOps champion startup. In the middle exists a number of real use cases on how we are bringing DevOps culture with Docker to Atos Worldline. In my talk I will discuss the first use cases for Docker at Atos Worldline, where we are today, learnings and benefits until now, our future technology stack and how Docker is changing our human stack a.k.a. how we communicate and work together.
Matt Franklin - Apache Software (Geekfest)W2O Group
The document discusses the potential benefits of container technologies like Docker. It notes that containers offer significantly higher density than virtual machines by avoiding hypervisor overhead. This density improvement can lead to major cost reductions by reducing infrastructure needs. Containers also improve developer efficiency by making development environments portable and disposable. This allows more rapid experimentation and innovation, potentially translating to increased revenue. Technologies like Amazon Lambda take the on-demand aspects of containers even further by abstracting compute resources. The document promotes StackEngine as a solution for managing containers at scale in production environments.
The document discusses using Play Framework, Docker, CircleCI, and AWS together to create an automated microservices build pipeline. Key aspects include using GitHub for source control, CircleCI for continuous integration to build Docker images, pushing images to Docker Hub, and deploying to AWS using ECS for container orchestration. The author demonstrates setting up each part of the pipeline live.
This document provides an overview of DevOps, including:
1) It discusses Garry, a product owner whose team had slow and manual software delivery processes until discovering DevOps.
2) DevOps is defined as a culture change involving shared responsibility between development and operations teams to deliver software rapidly through practices like continuous integration, delivery, infrastructure as code, and monitoring.
3) The benefits of DevOps are outlined as faster and more frequent software delivery, improved quality, security, and compliance through automation and visibility across the software lifecycle.
4) Examples of DevOps in action include deploying a web application directly from a development machine versus through an automated build and test process on a separate build box.
The document discusses DevOps practices for real world companies. It defines DevOps as people, processes and tools working together to enable continuous delivery of value to end users faster. It provides advice on establishing baselines, starting simple with one codebase, automating tests and infrastructure, implementing feature flags, improving cycle times through automation and removing bottlenecks, and shifting to a no-silos culture with collaboration between teams. The overall message is that DevOps requires cultural and operational changes to break down barriers and deliver value to users faster.
Do you need Ops in your new startup? If not now, then when? And...what is Ops?
Learn how to scale ruby-based distributed software infrastructure in the cloud to serve 4,000 requests per second, handle 400 updates per second, and achieve 99.97% uptime – all while building the product at the speed of light.
Unimpressed? Now try doing the above altogether without the Ops team, while growing your traffic 100x in 6 months and deploying 5-6 times a day!
It could be a dream, but luckily it's a reality that could be yours.
Coder sans peur du changement avec la meme pas mal hexagonal architectureThomas Pierrain
Découvrez en pratique l'architecture hexagonale, indispensable pour vos applications complexes !
Ce style d'architecture permet d'adapter votre code à tout changement de technologie sans souffrir. Si vous aimez changer de frameworks ou de librairies, tester correctement ou appliquer le Domain-Driven Design, alors vous avez besoin d'architecture hexagonale !
Avec des exemples en code Java, et au travers d’un kata d’architecture auquel vous pourrez participer, nous vous montrerons les pièges à éviter et comment mettre en œuvre ce pattern sans trop galérer, et ce dès votre retour au bureau !
Hybrid applications combine web development skills with native containers to create cross-platform mobile apps. While frameworks like Ionic and Famo.us allow developing hybrids quickly, performance issues remain on Android. React Native offers better performance by using native UI components instead of a webview, allowing developers to write once with React and deploy natively to iOS and Android. It has potential to replace other "native wrapper" frameworks by bringing React's declarative paradigm directly to mobile.
Wordnik's architecture is built around a large English word graph database and uses microservices and ephemeral Amazon EC2 storage. Key aspects include:
1) The system is built as independent microservices that communicate via REST APIs documented using Swagger specifications.
2) Databases for each microservice are kept small by design to facilitate operations like backups, replication, and index rebuilding.
3) Services are deployed across multiple Availability Zones and regions on ephemeral Amazon EC2 storage for high availability despite individual host failures.
Patterns & Antipatterns in Docker Image Lifecycleyoavl
While Docker has enabled an unprecedented velocity of software production, it is all too easy to spin out of control. A promotion-based model is required to control and track the flow of Docker images as much as it is required for a traditional software development lifecycle. New tools often introduce new paradigms. We will examine the patterns and the anti-patterns for Docker image management, and what impact the new tools have on the battle-proven paradigms of the software development lifecycle.
This talk takes it from the point that everybody already understand the need in the CI/CD pipeline and some of the basic techniques are taken for granted. It’s much more about tools, processes and automation.
The Ember.js Framework - Everything You Need To KnowAll Things Open
All Things Open 2014 - Day 2
Thursday, October 23rd, 2014
Yehuda Katz
Founder of Tilde
Front Dev 1
The Ember.js Framework - Everything You Need To Know
Ransack, an Application Built on Ansible's API for Rackspace -- AnsibleFest N...Paul Durivage
Ransack is an application built on Ansible's API that was created by Rackspace to automate repetitive tasks on customer servers. It uses Ansible's inventory and dynamic inventory features to access servers via Rackspace's APIs. The Ransack CLI was developed to provide a custom interface for Rackspace users, with sane defaults and self-documenting arguments. Initial launch problems stemmed from complex installation processes, but images and Docker helped address this. Future plans include offering Ransack as a service and improving deployment frequency.
The Tale of a Docker-based Continuous Delivery Pipeline by Rafe Colton (ModCl...Docker, Inc.
The ModCloth Platform team has been building a Docker-based continuous delivery pipeline. This presentation discusses that project and how we build containers at ModCloth. The topics include what goes into our containers; how to optimize builds to use the Docker build cache effectively; useful development workflows (including using fig); and the key decision to treat containers as processes instead of mini-vms. This presentation will also discuss (and demo!) the workflow we’ve adopted for building containers and how we’ve integrated container builds with our CI.
My talk from Dockercon EU in Amsterdam, Dec 2014. Original abstract:
The ModCloth Platform team has been building a Docker-based continuous delivery pipeline. This presentation discusses that project and how we build containers at ModCloth. The topics include what goes into our containers; how to optimize builds to use the Docker build cache effectively; useful development workflows (including using fig); and the key decision to treat containers as processes instead of mini-vms. This presentation will also discuss (and demo!) the workflow we’ve adopted for building containers and how we’ve integrated container builds with our CI.
Drupal and its contributed modules provides an impressive amount of functionality without needing to write a single line of code by storing information in Drupal’s database tables. Unfortunately this poses a challenge for developers wanting to stage changes between servers. This talk starts to address these issues by describing the problem and presenting a variety of solutions as well as their pros and cons. I also discuss some possible paths to make this easier coming down the pipe.
This is a talk given at Clojure Conj 2014 in Washington DC. The title was Paradigms of core.async and it was given by Julian Gamble.
The code and demos are available here: https://github.com/juliangamble/clojure-conj-2014-paradigms-of-core-async
Similar to Your Goat Anti-Fragiled My Snowflake! Demystifying DevOps Jargon (30 minute version) (20)
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
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.
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
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.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-EfficiencyScyllaDB
Freshworks creates AI-boosted business software that helps employees work more efficiently and effectively. Managing data across multiple RDBMS and NoSQL databases was already a challenge at their current scale. To prepare for 10X growth, they knew it was time to rethink their database strategy. Learn how they architected a solution that would simplify scaling while keeping costs under control.
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.
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/temporal-event-neural-networks-a-more-efficient-alternative-to-the-transformer-a-presentation-from-brainchip/
Chris Jones, Director of Product Management at BrainChip , presents the “Temporal Event Neural Networks: A More Efficient Alternative to the Transformer” tutorial at the May 2024 Embedded Vision Summit.
The expansion of AI services necessitates enhanced computational capabilities on edge devices. Temporal Event Neural Networks (TENNs), developed by BrainChip, represent a novel and highly efficient state-space network. TENNs demonstrate exceptional proficiency in handling multi-dimensional streaming data, facilitating advancements in object detection, action recognition, speech enhancement and language model/sequence generation. Through the utilization of polynomial-based continuous convolutions, TENNs streamline models, expedite training processes and significantly diminish memory requirements, achieving notable reductions of up to 50x in parameters and 5,000x in energy consumption compared to prevailing methodologies like transformers.
Integration with BrainChip’s Akida neuromorphic hardware IP further enhances TENNs’ capabilities, enabling the realization of highly capable, portable and passively cooled edge devices. This presentation delves into the technical innovations underlying TENNs, presents real-world benchmarks, and elucidates how this cutting-edge approach is positioned to revolutionize edge AI across diverse applications.
“Temporal Event Neural Networks: A More Efficient Alternative to the Transfor...
Your Goat Anti-Fragiled My Snowflake! Demystifying DevOps Jargon (30 minute version)
1. /
Your Goat Anti-Fragiled My
Snowflake!
Clinton Wolfe
DevOps Practice Lead
Demystifying DevOps Jargon
2. id clintoncwolfe
• DevOps Practice Lead at omniti.com
• We do web & services ops & development
• Chef architect, Ansible engineer, “devops consultant”
• author of various bits of tooling & glue
• we're hiring!
17. Pets
Nodes / servers / instances that are lovingly
hand-maintained, with long lives
Cattle
Nodes / servers / instances that are easily
replaced; created and destroyed via automation
18. Pets vs Cattle
“We’ve automated everything but the database
servers; the DBAs treat them as Pets.”
Coinage:
Originally from Bill Baker of Microsoft,
popularized by Gavin McCance of CERN
44. DSL
Domain Specific Language
a syntax and command set designed so that
users can write in their conceptual model
directory '/opt/my-app'
template '/opt/my-app/cfg.yaml' do
source 'alternate-cfg.yaml'
end
51. CI
1. Continuous Integration –running tests
whenever a commit occurs
2. Continuous Improvement – a culture
of looking for ways to improve
processes over time
54. CD
1. Continuous Delivery – building
software packages whenever a commit
occurs
2. Continuous Deployment – installing
the software to production whenever a
commit occurs
63. Red / Green / Refactor
workflow rhythm when developing under TDD
1. Write failing tests (red terminal output)
2. Write the least code possible to make the
code pass (green terminal output)
3. Clean up the code internally, while ensuring
the tests still pass (refactor)
67. Bikeshedding
to argue at length over a decision that is, in the
end, arbitrary
Coinage:
From the BSD community (mid 90's?): arguing
over what color to paint the bikeshed while the
house is not yet finished
(Computer Jargon File)
82. HugOps
a meme reflecting empathy among engineers,
especially after an incident, disagreement, or
personal tragedy
Example Usage:
@clintoncwolfe sorry to hear about your talk
going so badly #hugops
84. ChatOps
using your text chat tool as an interface to your
tooling, as well as a log of work
Appears to have emerged from GitHub in 2013,
Jesse Newland - ChatOps at GitHub