This document discusses trends in software delivery past, present and future. It notes how software delivery has shifted from manual and localized to automated and distributed. It argues continuous delivery is about dealing with increasing chaos and diversity. The document suggests several trends for the future including machine learning, augmented reality, IoT and self-driving vehicles. It envisions a future where computers write more of the code, delivery is further automated through self-healing systems, and improved visualization and interfaces change how software is developed and delivered.
The document discusses different mobile operating systems and their associated ecosystems. It describes the ecosystems of Android, iOS, Blackberry, and Windows, noting that the operating system determines compatibility. It also discusses security of mobile ecosystems and peripherals that can expand ecosystems. It poses questions about the future prevalence and form of mobile ecosystems.
ServerLess technology analysis, state of the technology as of December 2018, what needs to be done to build a complete, operational serverless platform for production
Architecture - December 2013 - Avinash Ramineni, Shekhar Veumuriclairvoyantllc
This document discusses various architecture concepts including web services, security, AWS services, architecture principles, n-tier architectures, distributed systems fallacies, best practices, transactions, and asynchronous architectures. It covers topics such as SOAP, REST, authentication, authorization, SSL, EC2, S3, RDS, EBS, ELB and more.
DevOps - Continuous Integration, Continuous Delivery - let's talkD Z
Brief but detailed insight about what to expect and what not from DevOps engineer if an organization is willing to hire one.
At the same time detailed insight about someone who is willing to dive into DevOps as a career option.
As OPNFV's mission is to create a carrier-grade, integrated reference platform built from open source components we are constantly facing with the difficulties these dependencies cause us. We see CI/CD & DevOps to be a solution to our challenges by providing a foundation for developing, integrating and testing OPNFV faster and more efficient through the release cycles. It is crucial for OPNFV and the ecosystem we are building the underlying upstream projects to find the best way to realize the principles and best practices of these methodologies to reduce the impacts caused by the integration work and be able to provide fast feedback to other communities and a stable platform to our users release by release. This presentation will discuss the importance of CI/CD and DevOps from end user, vendor, and upstream project perspectives and talk about the expectations on us, challenges we are facing, our experiences, and plans about CI/CD & DevOps for OPNFV.
Introduction to DevOps on AWS. Basic introduction to Devops principles and practices, and how they can be implemented on AWS. Introduces basic cloudformation.
AWS re:Invent 2016: DevOps on AWS: Advanced Continuous Delivery Techniques (D...Amazon Web Services
Continuous delivery makes teams more agile and quickens the pace of innovation. Too often, though, teams adopt continuous delivery without putting the right safety mechanisms in place. In this talk, we'll transform a simple but typical software release process into one that is safe. We'll use DevOps techniques like continuous integration, a variety of non-production testing stages, rollbacks, machine redundancy, Availability Zone redundancy, canary deployments, canary tests, and dashboards. We'll use AWS Lambda, AWS CloudFormation, AWS CodePipeline, AWS CodeDeploy, Amazon CloudWatch alarms and dashboards, and AWS Elastic Beanstalk.
Much has been said about DevOps culture, this webinar talks about exactly what it means to exercise a DevOps methodology inside your organization and takes a more detailed look at Continuous Integration and Continuous Deployment – two of the elements of a successful DevOps framework. With AWS’s API driven infrastructure, running a lean platform becomes possible and the ability to treat ‘Infrastructure as Code’.
Reasons to attend:
Learn how to set up and experience the benefits of 'Continuous Integration' and 'Continuous Deployment' for your Development Environment.
Learn about DevOps best practices and the agility that the AWS Cloud can bring your business.
Learn how business have successfully implemented DevOps methodologies.
The document discusses different mobile operating systems and their associated ecosystems. It describes the ecosystems of Android, iOS, Blackberry, and Windows, noting that the operating system determines compatibility. It also discusses security of mobile ecosystems and peripherals that can expand ecosystems. It poses questions about the future prevalence and form of mobile ecosystems.
ServerLess technology analysis, state of the technology as of December 2018, what needs to be done to build a complete, operational serverless platform for production
Architecture - December 2013 - Avinash Ramineni, Shekhar Veumuriclairvoyantllc
This document discusses various architecture concepts including web services, security, AWS services, architecture principles, n-tier architectures, distributed systems fallacies, best practices, transactions, and asynchronous architectures. It covers topics such as SOAP, REST, authentication, authorization, SSL, EC2, S3, RDS, EBS, ELB and more.
DevOps - Continuous Integration, Continuous Delivery - let's talkD Z
Brief but detailed insight about what to expect and what not from DevOps engineer if an organization is willing to hire one.
At the same time detailed insight about someone who is willing to dive into DevOps as a career option.
As OPNFV's mission is to create a carrier-grade, integrated reference platform built from open source components we are constantly facing with the difficulties these dependencies cause us. We see CI/CD & DevOps to be a solution to our challenges by providing a foundation for developing, integrating and testing OPNFV faster and more efficient through the release cycles. It is crucial for OPNFV and the ecosystem we are building the underlying upstream projects to find the best way to realize the principles and best practices of these methodologies to reduce the impacts caused by the integration work and be able to provide fast feedback to other communities and a stable platform to our users release by release. This presentation will discuss the importance of CI/CD and DevOps from end user, vendor, and upstream project perspectives and talk about the expectations on us, challenges we are facing, our experiences, and plans about CI/CD & DevOps for OPNFV.
Introduction to DevOps on AWS. Basic introduction to Devops principles and practices, and how they can be implemented on AWS. Introduces basic cloudformation.
AWS re:Invent 2016: DevOps on AWS: Advanced Continuous Delivery Techniques (D...Amazon Web Services
Continuous delivery makes teams more agile and quickens the pace of innovation. Too often, though, teams adopt continuous delivery without putting the right safety mechanisms in place. In this talk, we'll transform a simple but typical software release process into one that is safe. We'll use DevOps techniques like continuous integration, a variety of non-production testing stages, rollbacks, machine redundancy, Availability Zone redundancy, canary deployments, canary tests, and dashboards. We'll use AWS Lambda, AWS CloudFormation, AWS CodePipeline, AWS CodeDeploy, Amazon CloudWatch alarms and dashboards, and AWS Elastic Beanstalk.
Much has been said about DevOps culture, this webinar talks about exactly what it means to exercise a DevOps methodology inside your organization and takes a more detailed look at Continuous Integration and Continuous Deployment – two of the elements of a successful DevOps framework. With AWS’s API driven infrastructure, running a lean platform becomes possible and the ability to treat ‘Infrastructure as Code’.
Reasons to attend:
Learn how to set up and experience the benefits of 'Continuous Integration' and 'Continuous Deployment' for your Development Environment.
Learn about DevOps best practices and the agility that the AWS Cloud can bring your business.
Learn how business have successfully implemented DevOps methodologies.
DevOps, Continuous Integration and Deployment on AWS: Putting Money Back into...Amazon Web Services
Organizations around the globe are leveraging the cloud to accomplish world-changing missions. This session will address how AWS can help organizations put more money toward their mission and scale outreach and operations to achieve more with less. Hear some of AWS’s most advanced customers on how their organizations handle DevOps, continuous integration and deployment. Learn how these practices allow them to rapidly develop, iterate, test and deploy highly-scalable web applications and core operational systems on AWS. The discussion will focus on best practices, lessons learned, and the specific technologies and services they use.
The document discusses the roles and relationships between development (Dev) and operations (Ops) teams, and introduces the DevOps approach. It notes that traditionally there has been a disconnect between Devs and Ops that results in inefficiencies. DevOps aims to bridge this gap through a collaborative mindset and practices like automating infrastructure provisioning and deployments, implementing continuous integration/delivery, monitoring metrics, and breaking down silos between teams. Specific tools mentioned that support DevOps include Puppet for configuration management and Autobahn for continuous deployment.
DevOps: A Culture Transformation, More than TechnologyCA Technologies
DevOps is not a new technology or a product. It's an approach or culture of SW development that seeks stability and performance at the same time that it speeds software deliveries to the business. We will discuss this cultural shift where development teams have to accept the feedback of operations teams and the operations team should be ready to accept frequent updates to the SW that it's running.
To learn more about DevOps solutions from CA Technologies, please visit: http://bit.ly/1wbjjqX
This document provides an overview of DevOps concepts and practices. It defines DevOps as development and operations engineers collaborating throughout the entire service lifecycle, from design to production support. Key principles discussed include automating infrastructure, measuring everything, and fostering a culture of collaboration between teams. The document outlines DevOps practices like continuous integration/delivery and monitoring, and provides checklists for starting a DevOps initiative at both the grassroots and management levels.
AWS re:Invent 2016: DevOps on AWS: Accelerating Software Delivery with the AW...Amazon Web Services
Today’s cutting edge companies have software release cycles measured in days instead of months. This agility is enabled by the DevOps practice of continuous delivery, which automates building, testing, and deploying all code changes. This automation helps you catch bugs sooner and accelerates developer productivity. In this session, we’ll share the processes followed by Amazon engineers and discuss how you can bring them to your company by using AWS CodePipeline and AWS CodeDeploy, services inspired by Amazon's internal developer tools and DevOps culture.
Continuous integration has gone mainstream. It has helped development teams move quicker, and has disrupted build management and put additional pressures on deployment groups. In this presentation, we look at how CI achieved such a disruptive, positive impact, how it is turning into Continuous Delivery, and where DevOps fits into the picture (And how DevOps will be just as disruptive).
The document defines environmental pollution and describes its three main types: air, water, and soil pollution. It provides details on the causes and effects of each type of pollution. Air pollution is caused by emissions from vehicles, factories, and burning of fossil fuels, and can lead to acid rain, haze, health issues, and depletion of the ozone layer. Water pollution results from industrial waste, oil spills, and waste disposal in rivers and oceans, harming wildlife and spreading disease. Soil pollution is caused by industrial chemicals, mining, pesticides, and landfills, contaminating groundwater and reducing soil fertility.
With an ever-increasing array of tools and technologies claiming to 'enable DevOps', 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; the recommendations may surprise you.
Microservices involve developing applications as suites of small, independent services that communicate via APIs. This avoids problems of monolithic architectures where all code is deployed together. Well-defined components that are independently replaceable and upgradeable define microservices. While allowing greater scalability, flexibility and continuous delivery, microservices architectures require more sophisticated infrastructure automation, monitoring and approaches to handle failures and distributed transactions across services.
A high level overview of the new technologies & architectures in the software market today. A more detailed presentation will be coming next to go in depth into different languages / async models & cloud solution maintenance.
Software Architecture as Systems DissolveEoin Woods
The way we build systems is changing. From our history of monolithic systems, then distributed systems, to Internet connected systems, we are now entering the era of cloud-hosted, microservice based, pay-for-usage system development. What does the history of software architecture tell us about the challenges of this new environment? And how does our approach to software architecture need to evolve in order to meet them?
Software architecture has been a mainstream discipline since the 1990s and in that time has become a recognised, widely researched and often valued part of the software engineering process. However architecture approaches must reflect the technologies and priorities of the systems we are building and in this regard its future has never looked more uncertain or more exciting. From our history of monolithic compile time architecture, to many tiered distributed systems, to Internet connected services, we are now entering the era of cloud-hosted, microservice-based, pay-for-usage systems development. In this new world the boundaries of “my” system are no longer so clear and our systems are dissolving into complex webs of independently owned and evolved services, with nothing more in common than a shared credit card for billing and an agreement on the format of network requests. What can the history of software architecture tell us about the likely challenges in this environment? And how must it develop in order to meet them?
This version of the talk was presented at GOTO London in October 2016.
The document discusses microservice architecture and compares it to monolithic architecture. It describes microservices as small, discrete, isolated services that can be deployed separately. A monolith is a single application combining all business logic and data access. The document outlines characteristics of microservices such as single responsibility, statelessness, independent data management and communication through APIs or message queues. It also covers deployment, testing, monitoring, metrics and the need for automation and a culture open to change when using microservice architecture.
Midori is a new operating system being developed by Microsoft Research as the successor to Windows. It is a cloud-based OS that aims to be lightweight and portable across devices. Midori uses a microkernel architecture and isolates application components through software processes (SIPs) to improve security and reliability. It is coded primarily in M#, a customized version of C#, and will support web technologies like HTML5. The goal of Midori is to provide a post-Windows OS that is optimized for cloud computing and used via the web.
DevOps and the cloud: all hail the (developer) king - Daniel Bryant, Steve PooleJAXLondon_Conference
1) The document discusses the rise of microservices and DevOps approaches in application development and deployment. It notes both the promises and challenges of these approaches, including increased complexity and the need for new tooling.
2) It describes lessons learned from early adoption of microservices, such as the problems that can arise from shared data stores and monolithic upgrades.
3) The document advocates for a "safety first" mindset with DevOps, emphasizing the importance of security, compliance, and understanding where data is located in cloud environments.
This document provides an overview of embedded systems in 3 paragraphs or less:
Embedded systems are computer systems that are part of larger mechanical or electrical systems, often with real-time computing constraints. They are controlled by software programs to perform specific functions like controlling locks, thermostats, pacemakers, and industrial and military applications. Embedded systems have requirements for real-time operation, small size, reliability, operating in harsh environments, and cost sensitivity. The document discusses examples of embedded systems and their applications, system organization and design requirements, software design issues, and future possibilities for more embedded processors in new applications like pervasive computing.
Guaranteed Delivery - Delivering Infrastructure and Code Together - Matt MoorAtlassian
This document summarizes Matt Moor's presentation on guaranteeing delivery of code and infrastructure together through continuous delivery practices. It discusses building code and infrastructure separately but integrating them through shared artifacts. The key steps are to automate infrastructure builds with tools like Packer and Puppet, integrate code and infrastructure through builds that deploy code to virtual machines, and tie it all together with build notifications and deployment. The goal is to avoid surprises at deployment time and establish common ground between development and operations.
Microservices: How loose is loosely coupled?John Rofrano
Microservice architecture is a popular design pattern for DevOps deployments of cloud native applications. It's single purpose, loosely coupled, bounded context design lends itself to the independent life cycle required to quickly deploy and scale in the cloud. Docker containerization of these services further aids in the zero down-time deployments of these horizontally scalable services. But how do you keep them loosely coupled? How do they communicate without knowing about each other? and how do you keep all of those containers patched from new vulnerabilities that are being discovered every day?
This talk discusses the implementation of a Container Vulnerability Remediation Services that itself is designed as a collection of loosely coupled microservices that communicate via publish/subscribe messaging model using Kafka, Cloud Functions (OpenWhisk), and REST APIs implemented in Python Flask. This design keeps each microservice independent and replaceable, while enabling expandability for new services to participate in business functions without any pre-determined knowledge of the business workflow.
JAXLondon 2015 "DevOps and the Cloud: All Hail the (Developer) King"Daniel Bryant
Last year we talked about DevOps, what it was, why it was important and how to get started. Boy, was it scary. Now we’re wiser. More battle-scarred. The scale of the challenge for application writers exploiting cloud and DevOps is clearer, but so is the path forward. Understanding the DevOps approach is important but equally you must understand specific deployment technologies. How to exploit them and how they effect the design of applications. Whether creating simple applications or sophisticated microservice architectures many of the challenges are the same.
Presented at JAXLondon 2015 with Steve Poole
Imagine we had the power to understand the code before its complied or embedding a backdoor or even stealing legitimate certificates of a well known vendor and using them to sign malware?
Join me in the journey of exploring security issues that tend to happen during Build Time in typical enterprise environments.
The .NET Framework is a platform created by Microsoft for developing applications using languages like C# and VB.NET. It includes a library and Common Language Runtime (CLR) that manages execution. Code is compiled to an intermediate language (CIL) then JIT compiled to native code for the target system. Applications are compiled into assemblies (.exe or .dll files) that can be reused. The CLR handles memory management, security, and debugging. Visual Studio is an IDE that exposes .NET features and allows running/debugging applications. Controls represent UI elements with associated events and handlers that respond to user interactions.
There is a good chance that you have heard of artificial intelligence, machine learning, blockchain and bots. However, do you know what the implications of each of these technologies are? How it can and will impact your business in the near future? In this talk, we will discuss these technological trends, as well as a few others, that you will need to be familiar with as your association prepares to compete over the next few years. Let's take a peek into the future that is already here!
DevOps, Continuous Integration and Deployment on AWS: Putting Money Back into...Amazon Web Services
Organizations around the globe are leveraging the cloud to accomplish world-changing missions. This session will address how AWS can help organizations put more money toward their mission and scale outreach and operations to achieve more with less. Hear some of AWS’s most advanced customers on how their organizations handle DevOps, continuous integration and deployment. Learn how these practices allow them to rapidly develop, iterate, test and deploy highly-scalable web applications and core operational systems on AWS. The discussion will focus on best practices, lessons learned, and the specific technologies and services they use.
The document discusses the roles and relationships between development (Dev) and operations (Ops) teams, and introduces the DevOps approach. It notes that traditionally there has been a disconnect between Devs and Ops that results in inefficiencies. DevOps aims to bridge this gap through a collaborative mindset and practices like automating infrastructure provisioning and deployments, implementing continuous integration/delivery, monitoring metrics, and breaking down silos between teams. Specific tools mentioned that support DevOps include Puppet for configuration management and Autobahn for continuous deployment.
DevOps: A Culture Transformation, More than TechnologyCA Technologies
DevOps is not a new technology or a product. It's an approach or culture of SW development that seeks stability and performance at the same time that it speeds software deliveries to the business. We will discuss this cultural shift where development teams have to accept the feedback of operations teams and the operations team should be ready to accept frequent updates to the SW that it's running.
To learn more about DevOps solutions from CA Technologies, please visit: http://bit.ly/1wbjjqX
This document provides an overview of DevOps concepts and practices. It defines DevOps as development and operations engineers collaborating throughout the entire service lifecycle, from design to production support. Key principles discussed include automating infrastructure, measuring everything, and fostering a culture of collaboration between teams. The document outlines DevOps practices like continuous integration/delivery and monitoring, and provides checklists for starting a DevOps initiative at both the grassroots and management levels.
AWS re:Invent 2016: DevOps on AWS: Accelerating Software Delivery with the AW...Amazon Web Services
Today’s cutting edge companies have software release cycles measured in days instead of months. This agility is enabled by the DevOps practice of continuous delivery, which automates building, testing, and deploying all code changes. This automation helps you catch bugs sooner and accelerates developer productivity. In this session, we’ll share the processes followed by Amazon engineers and discuss how you can bring them to your company by using AWS CodePipeline and AWS CodeDeploy, services inspired by Amazon's internal developer tools and DevOps culture.
Continuous integration has gone mainstream. It has helped development teams move quicker, and has disrupted build management and put additional pressures on deployment groups. In this presentation, we look at how CI achieved such a disruptive, positive impact, how it is turning into Continuous Delivery, and where DevOps fits into the picture (And how DevOps will be just as disruptive).
The document defines environmental pollution and describes its three main types: air, water, and soil pollution. It provides details on the causes and effects of each type of pollution. Air pollution is caused by emissions from vehicles, factories, and burning of fossil fuels, and can lead to acid rain, haze, health issues, and depletion of the ozone layer. Water pollution results from industrial waste, oil spills, and waste disposal in rivers and oceans, harming wildlife and spreading disease. Soil pollution is caused by industrial chemicals, mining, pesticides, and landfills, contaminating groundwater and reducing soil fertility.
With an ever-increasing array of tools and technologies claiming to 'enable DevOps', 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; the recommendations may surprise you.
Microservices involve developing applications as suites of small, independent services that communicate via APIs. This avoids problems of monolithic architectures where all code is deployed together. Well-defined components that are independently replaceable and upgradeable define microservices. While allowing greater scalability, flexibility and continuous delivery, microservices architectures require more sophisticated infrastructure automation, monitoring and approaches to handle failures and distributed transactions across services.
A high level overview of the new technologies & architectures in the software market today. A more detailed presentation will be coming next to go in depth into different languages / async models & cloud solution maintenance.
Software Architecture as Systems DissolveEoin Woods
The way we build systems is changing. From our history of monolithic systems, then distributed systems, to Internet connected systems, we are now entering the era of cloud-hosted, microservice based, pay-for-usage system development. What does the history of software architecture tell us about the challenges of this new environment? And how does our approach to software architecture need to evolve in order to meet them?
Software architecture has been a mainstream discipline since the 1990s and in that time has become a recognised, widely researched and often valued part of the software engineering process. However architecture approaches must reflect the technologies and priorities of the systems we are building and in this regard its future has never looked more uncertain or more exciting. From our history of monolithic compile time architecture, to many tiered distributed systems, to Internet connected services, we are now entering the era of cloud-hosted, microservice-based, pay-for-usage systems development. In this new world the boundaries of “my” system are no longer so clear and our systems are dissolving into complex webs of independently owned and evolved services, with nothing more in common than a shared credit card for billing and an agreement on the format of network requests. What can the history of software architecture tell us about the likely challenges in this environment? And how must it develop in order to meet them?
This version of the talk was presented at GOTO London in October 2016.
The document discusses microservice architecture and compares it to monolithic architecture. It describes microservices as small, discrete, isolated services that can be deployed separately. A monolith is a single application combining all business logic and data access. The document outlines characteristics of microservices such as single responsibility, statelessness, independent data management and communication through APIs or message queues. It also covers deployment, testing, monitoring, metrics and the need for automation and a culture open to change when using microservice architecture.
Midori is a new operating system being developed by Microsoft Research as the successor to Windows. It is a cloud-based OS that aims to be lightweight and portable across devices. Midori uses a microkernel architecture and isolates application components through software processes (SIPs) to improve security and reliability. It is coded primarily in M#, a customized version of C#, and will support web technologies like HTML5. The goal of Midori is to provide a post-Windows OS that is optimized for cloud computing and used via the web.
DevOps and the cloud: all hail the (developer) king - Daniel Bryant, Steve PooleJAXLondon_Conference
1) The document discusses the rise of microservices and DevOps approaches in application development and deployment. It notes both the promises and challenges of these approaches, including increased complexity and the need for new tooling.
2) It describes lessons learned from early adoption of microservices, such as the problems that can arise from shared data stores and monolithic upgrades.
3) The document advocates for a "safety first" mindset with DevOps, emphasizing the importance of security, compliance, and understanding where data is located in cloud environments.
This document provides an overview of embedded systems in 3 paragraphs or less:
Embedded systems are computer systems that are part of larger mechanical or electrical systems, often with real-time computing constraints. They are controlled by software programs to perform specific functions like controlling locks, thermostats, pacemakers, and industrial and military applications. Embedded systems have requirements for real-time operation, small size, reliability, operating in harsh environments, and cost sensitivity. The document discusses examples of embedded systems and their applications, system organization and design requirements, software design issues, and future possibilities for more embedded processors in new applications like pervasive computing.
Guaranteed Delivery - Delivering Infrastructure and Code Together - Matt MoorAtlassian
This document summarizes Matt Moor's presentation on guaranteeing delivery of code and infrastructure together through continuous delivery practices. It discusses building code and infrastructure separately but integrating them through shared artifacts. The key steps are to automate infrastructure builds with tools like Packer and Puppet, integrate code and infrastructure through builds that deploy code to virtual machines, and tie it all together with build notifications and deployment. The goal is to avoid surprises at deployment time and establish common ground between development and operations.
Microservices: How loose is loosely coupled?John Rofrano
Microservice architecture is a popular design pattern for DevOps deployments of cloud native applications. It's single purpose, loosely coupled, bounded context design lends itself to the independent life cycle required to quickly deploy and scale in the cloud. Docker containerization of these services further aids in the zero down-time deployments of these horizontally scalable services. But how do you keep them loosely coupled? How do they communicate without knowing about each other? and how do you keep all of those containers patched from new vulnerabilities that are being discovered every day?
This talk discusses the implementation of a Container Vulnerability Remediation Services that itself is designed as a collection of loosely coupled microservices that communicate via publish/subscribe messaging model using Kafka, Cloud Functions (OpenWhisk), and REST APIs implemented in Python Flask. This design keeps each microservice independent and replaceable, while enabling expandability for new services to participate in business functions without any pre-determined knowledge of the business workflow.
JAXLondon 2015 "DevOps and the Cloud: All Hail the (Developer) King"Daniel Bryant
Last year we talked about DevOps, what it was, why it was important and how to get started. Boy, was it scary. Now we’re wiser. More battle-scarred. The scale of the challenge for application writers exploiting cloud and DevOps is clearer, but so is the path forward. Understanding the DevOps approach is important but equally you must understand specific deployment technologies. How to exploit them and how they effect the design of applications. Whether creating simple applications or sophisticated microservice architectures many of the challenges are the same.
Presented at JAXLondon 2015 with Steve Poole
Imagine we had the power to understand the code before its complied or embedding a backdoor or even stealing legitimate certificates of a well known vendor and using them to sign malware?
Join me in the journey of exploring security issues that tend to happen during Build Time in typical enterprise environments.
The .NET Framework is a platform created by Microsoft for developing applications using languages like C# and VB.NET. It includes a library and Common Language Runtime (CLR) that manages execution. Code is compiled to an intermediate language (CIL) then JIT compiled to native code for the target system. Applications are compiled into assemblies (.exe or .dll files) that can be reused. The CLR handles memory management, security, and debugging. Visual Studio is an IDE that exposes .NET features and allows running/debugging applications. Controls represent UI elements with associated events and handlers that respond to user interactions.
There is a good chance that you have heard of artificial intelligence, machine learning, blockchain and bots. However, do you know what the implications of each of these technologies are? How it can and will impact your business in the near future? In this talk, we will discuss these technological trends, as well as a few others, that you will need to be familiar with as your association prepares to compete over the next few years. Let's take a peek into the future that is already here!
Elastically scalable architectures with microservices. The end of the monolith?Javier Arias Losada
In the last years the microservices architecture style has been gaining traction with some companies such as Netflix, Yelp, Gilt, PayPal. Many of that companies abandoned their previous monolithic architecture and moved to a microservices approach.
Does that mean that monolithic architectures are a thing of the past?
In this talk we will review some key microservices concepts (and misconceptions), search for the essence of microservices architectures and discuss about different approaches to implement them from the industry.
- The document discusses using AWS to build a large-scale, Dockerized microservices architecture for moovel Group GmbH's mobility app.
- It outlines moovel's goals of simplifying mobility now and solving future challenges through a mobility-as-a-service platform.
- The architecture uses AWS services like ECS, SQS, and Kinesis along with Docker containers, microservices, and an API gateway to achieve scalability, independent development, and minimal operational effort across teams.
DCEU 18: From Monolith to MicroservicesDocker, Inc.
Jeff Nickoloff - Co-founder, Topple
Growth can be challenging to address once monolithic systems begin to fail under strain or internal software development processes begin to slow the release cadence. Many organizations are looking to microservices architecture to solve these application issues, whether they plan to write new applications or rewrite the monoliths into microservices. This talk will highlight the common technical and cultural issues that will make microservice architectures a challenge to adopt and maintain. Issues include impact of Dunbar's Number and Conway's Law, build-time vs runtime continuous integration, evolution of testability, API versioning impact, logistics overhead, artifact management, and strategies for iteration in a distributed environment. Attendees will learn: - How and why microservice architectures and ownership end up falling along organizational lines (and why that is a good thing) - How we can learn from monolith tooling to inform our tooling in a microservice environment - How you can achieve operational excellence at scale taking a logistical approach with Docker.
My (very brief!) presentation at Interzone.io on March 11, 2015. A more in depth exploration of these ideas can be found at http://www.slideshare.net/bcantrill/docker-and-the-future-of-containers-in-production video: https://www.joyent.com/developers/videos/docker-and-the-future-of-containers-in-production
Similar to Jenkins and the Future of Software Delivery (20)
In the last decade multiple IT organizations jumped head first into CI - in an utopian belief that with enough time and investment the CI pipeline will take them straight into the promised land of CD. But things rarely go as expected. The reality is that until now most of us can't continuously and safely deploy to production - if it's because of lack of confidence, security concerns or contractual obligations. The number of outages caused by production updates is growing and the ever-increasing observability of our systems doesn't make SRE work any less stressful. Cloud native technologies are supposed to make operating complex distributed systems easier - but the CD gap is still not closed.
New approaches such as GitOps and Progressive Delivery strategies are getting more widely known but are still hard to pull off for anyone but the most technologically advanced teams.
We at Canarian and Otomato believe CD doesn't have to be so hard. In the last 4 years we've helped a number of orgs with their continuous deployment effort - both for SaaS and enterprise systems. We clearly see the need for better tooling and semantic change management that will allow us to modify information systems with heightened agility, stability and built-in support for continuous experimentation.
I the talk I outline the CD solution we are working on, explain what features it brings to the table and how this will revolutionize software delivery in the cloud native world.
Escaping the Jungle - Migrating to Cloud Native CI/CDAnton Weiss
The document discusses migrating from a complex "jungle" of tools and technologies for continuous integration and continuous delivery (CI/CD) to a cloud-native approach. It describes some of the challenges of the jungle model, including decision waste, integration pains, and lack of common standards. The document then outlines key aspects of a cloud-native CI/CD model, including using Kubernetes as the integration platform, dynamic agents and environments, and decoupling delivery from release. It provides examples of implementing such a model using shared libraries, Jenkinsfiles, containerized agents, and standardized pipelines and workflows.
Envoy is a lightweight modern network proxy written in C++. It has quickly become the base component in most existing service mesh implementations. With such popularity - a new, safer, more scalable extensibility model was needed.
Much to our excitement - now one can extend Envoy network filtering with WebAssembly modules written (among other languages) in Rust.
We'll see a live demo of building and deploying such a filter.
The document discusses how service meshes like Istio can help address issues with microservices architectures like misconfigured fallbacks, retry storms, and cascading failures. It outlines Istio's features like smart routing, telemetry, and built-in security. The author advocates for using operators and "Otomators" to automate cluster management and progressive delivery strategies. Real ninjas are said to use Otomators to prevent developers from getting stuck in the mesh or it becoming clogged. Questions are raised about alternative meshes and ensuring otomators are developed.
Service meshes are all the buzz in cloud-native world.
How come only yesterday we didn't know such a thing existed and now everybody seems to want one?
If you're already running a microservice-based system or only starting out with one — you may be asking yourself: "Do I also need a mesh?"
In this session we'll try to answer what the mesh is good for, what problems it solves, what new questions it poses.
More specifically we will:
explore the SMI Spec;
understand why everybody wants a mesh;
see how the mesh helps with progressive delivery;
discuss if it's time for you to get into the mesh.
Optimizing the Delivery Pipeline for FlowAnton Weiss
The document discusses optimizing the software delivery pipeline using lean principles. It defines the delivery pipeline as a subset of the overall value stream. Key aspects covered include identifying types of waste, establishing base performance metrics like deployment frequency and change failure rate, 12 specific devops flow metrics, and techniques for enabling smooth flow like transparency, pull-based flows, and on-demand resources. It emphasizes the importance of measurement for management but cautions against the myth that what can't be measured can't be managed.
Cargo is the package manager for Rust. It is used to create new projects, manage dependencies, compile code, and publish packages. Cargo uses the Cargo.toml file to define metadata and dependencies, and Cargo.lock to lock dependency versions. Dependencies can come from Crates.io, Git repositories, or local paths. Build scripts allow generating code during compilation. Cargo can publish packages to Crates.io and supports workspaces, environment variables, custom commands, and unstable features for nightly builds.
Heralding change - How to Get Engineers On Board the DevOps ShipAnton Weiss
Anyone who has been involved with a DevOps transformation realizes that changing the mindset is the hardest part. Effective collaboration starts with trust. In this talk I've presented the challenges with winning engineers' trust and how we've tackled this in large enterprise organizations.
This document discusses managing chaos in complex systems like pipelines and plumbing. It suggests embracing failures and decentralization. Key concepts mentioned include feedback loops, self-organization, microservices, serverless architecture, blockchain, and chaos engineering. The document advocates for simplifying interaction between components rather than the components themselves. It also promotes open policy, observability, and dynamic policy definition for distributed systems.
Istio is a service mesh that provides intelligent routing, telemetry, and security for microservices. It handles concerns like service discovery, load balancing, failure recovery, metrics, and traffic management across microservices. Istio installs Envoy proxies alongside services to provide an abstraction layer for these capabilities without requiring changes to the services' code.
ChatOps - the Road to a Collaborative CLI Anton Weiss
This document discusses ChatOps and how it can be implemented. It introduces common chat bots like Hubot and how they integrate different systems through a team chat interface. It provides tips on choosing a bot framework, developing discoverability through commands, and balancing the signal to noise ratio in chat. The document warns about risks like vendor lock-in but emphasizes that the overall goal is to have fun while improving collaboration and learning. Real customer examples are given to demonstrate the benefits of ChatOps.
The Road to a Hybrid, Transparent PipelineAnton Weiss
The talk I originally gave at DevCon TLV X.
Abstract: CI/CD pipelines are all about communication patterns in an organisation. Integrated solutions don't scale because Continuous Delivery is not a commodity. Opt for a hybrid, modular pipeline and make all information visible to tackle complexity.
Openstack is one of the largest OSS projects today with hundreds of commits flowing in daily. This high rate of change requires an advanced CI infrastructure. The purpose of the talk is to provide an overview of this infrastructure, explaining the role of each tool and the pipelines along which changes have to travel before they find their way into the approved Openstack codebase.
Talk delivered at Openstack Day Israel 2016 : http://www.openstack-israel.org/#!agenda/cjg9
Continuous Delivery is not a commodity because no two Continuous Delivery pipelines are exactly the same. Continuous Delivery requires integration with multiple tools and frameworks, support for multiple operating systems, and customizable flows, dashboards, and reporting. While the principles of Continuous Delivery can be learned from others, each organization's Continuous Delivery process is unique and cannot simply be copied from another. Continuous Delivery is more of an art than a science that depends on people, not just technology.
How the use of Groovy language can help you manage your Jenkins instance and extend its functionality. Presentation given at Jenkins User Conference Israel 2015
This document discusses the concepts of DevOps, transparency, and self-service. It argues that self-service requires better technology, usability, and trust which is built through transparency. Transparency involves traceability, monitoring, reporting, logs, dashboards and feedback loops to create a culture of openness and understanding between teams. When implemented successfully, self-service can provide services like continuous integration, testing, provisioning and deployment in an automated and user-friendly way to help deliver better software faster.
Vagrant allows developers to easily create and configure consistent development environments across machines using configuration files and provisioning scripts. It works by defining a virtual environment using a Vagrantfile that specifies things like the base box image, networking, storage, and provisioning scripts. Vagrant then automates the setup of this virtual environment on the local machine, allowing developers to work with reproducible and portable development environments.
The document summarizes a presentation given by Anton Weiss at the Jenkins User Conference on July 5, 2012 in Herzelia, Israel about full cycle mobile build automation using Jenkins. The presentation covered getting source from ClearCase and SVN, building Java and Objective C mobile applications for Android, BlackBerry and iOS, running static code analysis and tests, notifying teams of results, and opportunities to improve build flows in Jenkins.
E-commerce Application Development Company.pdfHornet Dynamics
Your business can reach new heights with our assistance as we design solutions that are specifically appropriate for your goals and vision. Our eCommerce application solutions can digitally coordinate all retail operations processes to meet the demands of the marketplace while maintaining business continuity.
E-commerce Development Services- Hornet DynamicsHornet Dynamics
For any business hoping to succeed in the digital age, having a strong online presence is crucial. We offer Ecommerce Development Services that are customized according to your business requirements and client preferences, enabling you to create a dynamic, safe, and user-friendly online store.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
GraphSummit Paris - The art of the possible with Graph TechnologyNeo4j
Sudhir Hasbe, Chief Product Officer, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
Transform Your Communication with Cloud-Based IVR SolutionsTheSMSPoint
Discover the power of Cloud-Based IVR Solutions to streamline communication processes. Embrace scalability and cost-efficiency while enhancing customer experiences with features like automated call routing and voice recognition. Accessible from anywhere, these solutions integrate seamlessly with existing systems, providing real-time analytics for continuous improvement. Revolutionize your communication strategy today with Cloud-Based IVR Solutions. Learn more at: https://thesmspoint.com/channel/cloud-telephony
What is Augmented Reality Image Trackingpavan998932
Augmented Reality (AR) Image Tracking is a technology that enables AR applications to recognize and track images in the real world, overlaying digital content onto them. This enhances the user's interaction with their environment by providing additional information and interactive elements directly tied to physical images.
Atelier - Innover avec l’IA Générative et les graphes de connaissancesNeo4j
Atelier - Innover avec l’IA Générative et les graphes de connaissances
Allez au-delà du battage médiatique autour de l’IA et découvrez des techniques pratiques pour utiliser l’IA de manière responsable à travers les données de votre organisation. Explorez comment utiliser les graphes de connaissances pour augmenter la précision, la transparence et la capacité d’explication dans les systèmes d’IA générative. Vous partirez avec une expérience pratique combinant les relations entre les données et les LLM pour apporter du contexte spécifique à votre domaine et améliorer votre raisonnement.
Amenez votre ordinateur portable et nous vous guiderons sur la mise en place de votre propre pile d’IA générative, en vous fournissant des exemples pratiques et codés pour démarrer en quelques minutes.
Need for Speed: Removing speed bumps from your Symfony projects ⚡️Łukasz Chruściel
No one wants their application to drag like a car stuck in the slow lane! Yet it’s all too common to encounter bumpy, pothole-filled solutions that slow the speed of any application. Symfony apps are not an exception.
In this talk, I will take you for a spin around the performance racetrack. We’ll explore common pitfalls - those hidden potholes on your application that can cause unexpected slowdowns. Learn how to spot these performance bumps early, and more importantly, how to navigate around them to keep your application running at top speed.
We will focus in particular on tuning your engine at the application level, making the right adjustments to ensure that your system responds like a well-oiled, high-performance race car.
Takashi Kobayashi and Hironori Washizaki, "SWEBOK Guide and Future of SE Education," First International Symposium on the Future of Software Engineering (FUSE), June 3-6, 2024, Okinawa, Japan
Software Engineering, Software Consulting, Tech Lead, Spring Boot, Spring Cloud, Spring Core, Spring JDBC, Spring Transaction, Spring MVC, OpenShift Cloud Platform, Kafka, REST, SOAP, LLD & HLD.
Mobile App Development Company In Noida | Drona InfotechDrona Infotech
Looking for a reliable mobile app development company in Noida? Look no further than Drona Infotech. We specialize in creating customized apps for your business needs.
Visit Us For : https://www.dronainfotech.com/mobile-application-development/
AI Fusion Buddy Review: Brand New, Groundbreaking Gemini-Powered AI AppGoogle
AI Fusion Buddy Review: Brand New, Groundbreaking Gemini-Powered AI App
👉👉 Click Here To Get More Info 👇👇
https://sumonreview.com/ai-fusion-buddy-review
AI Fusion Buddy Review: Key Features
✅Create Stunning AI App Suite Fully Powered By Google's Latest AI technology, Gemini
✅Use Gemini to Build high-converting Converting Sales Video Scripts, ad copies, Trending Articles, blogs, etc.100% unique!
✅Create Ultra-HD graphics with a single keyword or phrase that commands 10x eyeballs!
✅Fully automated AI articles bulk generation!
✅Auto-post or schedule stunning AI content across all your accounts at once—WordPress, Facebook, LinkedIn, Blogger, and more.
✅With one keyword or URL, generate complete websites, landing pages, and more…
✅Automatically create & sell AI content, graphics, websites, landing pages, & all that gets you paid non-stop 24*7.
✅Pre-built High-Converting 100+ website Templates and 2000+ graphic templates logos, banners, and thumbnail images in Trending Niches.
✅Say goodbye to wasting time logging into multiple Chat GPT & AI Apps once & for all!
✅Save over $5000 per year and kick out dependency on third parties completely!
✅Brand New App: Not available anywhere else!
✅ Beginner-friendly!
✅ZERO upfront cost or any extra expenses
✅Risk-Free: 30-Day Money-Back Guarantee!
✅Commercial License included!
See My Other Reviews Article:
(1) AI Genie Review: https://sumonreview.com/ai-genie-review
(2) SocioWave Review: https://sumonreview.com/sociowave-review
(3) AI Partner & Profit Review: https://sumonreview.com/ai-partner-profit-review
(4) AI Ebook Suite Review: https://sumonreview.com/ai-ebook-suite-review
#AIFusionBuddyReview,
#AIFusionBuddyFeatures,
#AIFusionBuddyPricing,
#AIFusionBuddyProsandCons,
#AIFusionBuddyTutorial,
#AIFusionBuddyUserExperience
#AIFusionBuddyforBeginners,
#AIFusionBuddyBenefits,
#AIFusionBuddyComparison,
#AIFusionBuddyInstallation,
#AIFusionBuddyRefundPolicy,
#AIFusionBuddyDemo,
#AIFusionBuddyMaintenanceFees,
#AIFusionBuddyNewbieFriendly,
#WhatIsAIFusionBuddy?,
#HowDoesAIFusionBuddyWorks
OpenMetadata Community Meeting - 5th June 2024OpenMetadata
The OpenMetadata Community Meeting was held on June 5th, 2024. In this meeting, we discussed about the data quality capabilities that are integrated with the Incident Manager, providing a complete solution to handle your data observability needs. Watch the end-to-end demo of the data quality features.
* How to run your own data quality framework
* What is the performance impact of running data quality frameworks
* How to run the test cases in your own ETL pipelines
* How the Incident Manager is integrated
* Get notified with alerts when test cases fail
Watch the meeting recording here - https://www.youtube.com/watch?v=UbNOje0kf6E
1. Jenkins and the Future of
Software Delivery
Ant Weiss
twitter: @antweiss
Otomato - http://otomato.link
2. > whoami: “Ant Weiss”
• Delivering Software since 2000 (Y2K bug)
• Previously @: AT&T,BMC,Comverse,n+ startups
• Principal Consultant and CEO @Otomato
• CI/CD/DevOps Evangelism & Enablement
• Technical Training Enthusiast
• Jenkins TLV Area Meetup Organiser
• In love with the future.
http://otomato.link
3. The Future:
“The best thing about the future is that it
comes one day at a time.”
― Abraham Lincoln
5. The Future???
•We can’t predict the future
•We can calculate the odds
•It’s a percentage game
•We can’t avoid predicting the
future
•Focus on the large trends
6. The Past of Software Delivery:
• Co-located Teams
• No VCS -> Centralised VCS
• Manual Integration
• No QA! }8-0 -> Manual QA
• Waterfall
• Monolithic architectures
• Devs Vs. Ops
7. The Past of Software Delivery:
• Punchcards
• Floppy disks (save -> ]
• ISO images
• Custom Installers
• Bare Metal/Big Iron/Distributed Systems
• Manual Configuration Management
• Synchronous IPC
• Focus on: Reliability/Stability ( Past ]
8. The Present of Software Delivery:
• Geo-Distributed Teams
• Distributed VCS
• Continuous Integration/Delivery
• TDD
• Microservices
• Agile
• DevOps!!!
9. The Present of Software Delivery:
• Clouds!!!
• Virtualisation
• [I/P/S]AAS
• Infrastructure as Code
• Package Managers
• Containers
• Service Discovery
• Message Queues
• Mobile Devices
21. The Future of Software Delivery
•Computers writing the Code
•From non-human Gatekeepers to
non-human Contributors
•From Monitoring to Self-Healing
•Advanced Visualisation
•New Control Interfaces
•OTA delivery to multiple devices
24. Machines Write The Code
- Jenkins to provide insights and
optimisation suggestions
- Automatically fix syntax (finally!!!]
- IOT - Trigger re-writing and re-testing of
SW based on signals from edge systems.
- ever more testing and verification
25. Machines Talk To Each Other
- unified CI language (Jenkinsfile)
- SW components describe how they are built
- Pattern recognition
- Jenkins understands what a project needs
- delivery and automation are a part of
application (see Chef’s Habitat]
26. Advanced UI
- visualisation - shuffle stages around,
rewire on the fly, version everything
- trigger builds based on chat context (not
just commands]
- emit events to any communication channel
- finally - trigger SW deploys by power of
thought
27. Speed vs. Control
100s deploys a
day
production
issues
resolved in
minutes
zero-time updates
can we release machines from our
control?
28. The Future:
If you think in terms of a year, plant a
seed; if in terms of ten years, plant trees;
if in terms of 100 years, teach the people.
Confucius
Hello, dear Jenkins fans! Hello fellow engineers! How are you today? Are you feeling optimistic? Well, you have all the reasons to be - they’ll be serving beer right after my talk! But that’s short term. And what about the long term? Are you optimistic when you look into the future and try to see what it brings? Do you believe in robot apocalypse or the utopia of singularity? Do you think the world will change to the better or to the worse? Or are you just too busy fixing bugs in production and making sure all your systems are running smoothly?
I’m asking all these questions because it’s future I want to talk about here today. But first - a few words about myself.
So whoami? My name is Anton Weiss, but my friends call me Ant. I’ve been building and delivering software since year 2000 (or since the millennium bug, for those who remember)
Now talking about the future - I love this quote from Abraham Lincoln - “The best thing about the future is that it comes one day at a time.” Because when you think about it - the guy is actually talking nothing other than Continuous Delivery!
In a way we could say that doing CD is about building software for the future. As opposed to the way we used to deliver software previously - that was all about the past.
Now - this is the point where the sceptics among us will say that this whole ‘future’ blah-blah is pretty much senseless. In fact - historians have proven time after time that we can’t really predict the future. History is too complex and non-linear, there are too many factors. Moreover - history is a chaotic system of second order - it gets impacted by our predictions, but - in an unpredictable fashion. :) Nevertheless - financial analysts have taught us that we can calculate the odds, we can estimate the probability and make a couple of bucks in the process. And most importantly - we can’t really help trying to predict the future - because forward is the only direction we can be going and we need at the very least an illusion of control over our faith.
So what can we do? Well, common sense says: focus on large, slow-moving trends and you have a good chance to understand where it all is going. At least until the brits suddenly decide to leave the european union and explode the whole thing.
How do we identify the trends? We look at the past and compare it to the present. So what did we have in the not so distant past? First let’s look at the delivery processes and methodologies.
Now tools-wise. How did we deliver our software to the end users and target systems? So first we had punchcards, then we had floppy disks, that are probably staying with us forever in the form of the ‘save’ icon. I had to explain my kids recently why this is how the save icon looks - because they never saw a floppy disk in their whole life. Then we had caroms and ISO images and all types of custom installers. And we had all the big and heavy concepts: bare metal, big iron, mainframe and then distributed systems became all the buzz. And all the configuration was managed manually with main focus being stability and reliability of the systems we’re running. As I said - it was all about preserving the past, not about moving into the future, or even staying in sync with the present.
But - a lot has changed in the last decade! Now we predominantly have geo-distributed teams, distributed VCS systems, CI/CD have become the industry golden standard. Even if we’re not doing it, we at least know that TDD is a good thing. We’re breaking up our monoliths into micorservices, we’re containerising our apps, we’re being agile and we believe that dev and ops can live together in harmony.
And we have the technology to support all of these: we have cloud computing, virtualization, we have fifty shades of AAS, we have the tools to manage our infrastructure as code, we have great package managers and binary repositories (thank you Frog!), we have containers and service discovery and mobile devices so we can be connected anywhere.
Hell, we ourselves have changed. Instead of being specialists in our won field we are now expected to be full-stack whatever. Or even better - the T-shaped professionals. You know where we have the wide knowledge throughout the stack and deep knowledge in some specific field of expertise.
Now this wide knowledge has to be freaking wide. Because we’re not actually talking one stack. We’re talking dozens or even hundreds of stacks. In fact there’s one thing I’m totally certain about when I look at the future is that we’ll continue having even more variety.
By the way - the trends we’ve outlined are occurring in parallel in the way we build our organisations and in the way we build and deliver our software. All in line with the proverbial Conway’s law.
So we looked at our past and our present, and we see there are certain trends. But what do we know about the future? How do we see the future when looking at it from today? Well we definitely know that machines will continue learning, we know that our reality will become more and more augmented, we’ll continue genreating, shuffling around and mining our data in a hope of understanding new things about the world and our society. We’’ll have internet of things with with our coffe machine asking our fridge to pass the milk. We’ll be riding around in self-driving vehicles, we’ll be controlling machines with the power of thought and we’ll have nano-bots circulating in our blood stream to make sure we stay healthy and well.
Or to summarise it all - we’ll have the world swarming with self-organising non-biological intelligence with non-linear communication patterns.
That was about machines - but what about humans? We’ll definitely also see ourselves evolving from T-shaped professionals into n shaped, m shaped, and octopus-shaped professionals.
Now how does all this relate to software delivery?
Now the key to many of these changes - both in how we interact with each other and in how our machines interact with us and each other lies in communication. The medium becomes the message as communication enables collaboration on massive scale. You know they say the arab spring was brought on by the new channels of communication. And for effective communication - shared context is the key. We need to be speaking a common language and share the same abstractions. Or at least have a way to recognise each other’s patterns.
Are you already envisioning the future. Or just waiting for that beer? Whatever it is - let’s not forget why we are here today. We’re all here because of Jenkins - because we have this great open source project which allows us to be both its users and creators. Because this is a project we can actually take into the future - help it become whatever we want it to be. So let’s think what we can do with Jenkins in order to continuously deliver the future.
Now all this is great. It’s a vision to follow, but until that happens - we all have a lot of code to write and a lot of problems to solve. And to do that in an efficient matter - we need to continue learning and teaching. After all - the future can never be better if we don’t learn from the mistakes of the past. Before machines can dance we need to grow the humans who can teach them how to dance. That’s the reason we’re having conferences like this one, that’s why we’re giving answers on stack overflow and hold meetups. And this is a great occasion to invite you all to sign up for the Jenkins Tel Aviv Area Meetup Group and start sharing your knowledge for the brighter future of software delivery.