This document summarizes the evolution of cloud computing technologies from virtual machines to containers to serverless computing. It discusses how serverless computing uses cloud functions that are fully managed by the cloud provider, providing significant cost savings over virtual machines by only paying for resources used. While serverless computing reduces operational overhead, it is not suitable for all workloads and has some limitations around cold start times and vendor lock-in. The document promotes serverless computing as the next wave in cloud that can greatly reduce costs and complexity while improving scalability and availability.
This is the slide deck for the DFW Azure User Group meetup of 18 July 2017, presented by Doug Vanderweide and discussing Azure's services that support a microservices architecture.
DockerCon SF 2015: Using Docker to Keep Houses Warm: Highly Distributed Micro...Docker, Inc.
Eric Feliksik's Slides from his DockerCon presentation:
Nerdalize is a Dutch start-up that provides affordable and green computing power with an innovative approach. We heat living rooms with CPUs, as high-performance computer hardware is fit into a beautiful design radiator. While home owners heat for free, a massive distributed compute infrastructure becomes available.
In this talk, we give a detailed overview of how Docker, Rancher and other tools in the ecosystem enable us to leverage such a highly distributed micro-datacenter architecture. We discuss how our approach drastically eliminates data center infrastructure costs, and how we aim to change the environmental impact of the compute industry.
This presentation, given at the Fort Worth .NET User Group on 19 Sept. 2017, talks about serverless technology: What it is, when it's best to use, its features and limitations. It specifically focuses on Azure Functions and Azure Logic Apps.
Using apache camel for microservices and integration then deploying and managing on Docker and Kubernetes. When we need to make changes to our app, we can use Fabric8 continuous delivery built on top of Kubernetes and OpenShift.
Highlights the services in Azure that provide microservices, including App Service, Logic Apps, Functions, Azure SQL Database, Service Bus, containers, Traffic Manager, etc.
This is the slide deck for the DFW Azure User Group meetup of 18 July 2017, presented by Doug Vanderweide and discussing Azure's services that support a microservices architecture.
DockerCon SF 2015: Using Docker to Keep Houses Warm: Highly Distributed Micro...Docker, Inc.
Eric Feliksik's Slides from his DockerCon presentation:
Nerdalize is a Dutch start-up that provides affordable and green computing power with an innovative approach. We heat living rooms with CPUs, as high-performance computer hardware is fit into a beautiful design radiator. While home owners heat for free, a massive distributed compute infrastructure becomes available.
In this talk, we give a detailed overview of how Docker, Rancher and other tools in the ecosystem enable us to leverage such a highly distributed micro-datacenter architecture. We discuss how our approach drastically eliminates data center infrastructure costs, and how we aim to change the environmental impact of the compute industry.
This presentation, given at the Fort Worth .NET User Group on 19 Sept. 2017, talks about serverless technology: What it is, when it's best to use, its features and limitations. It specifically focuses on Azure Functions and Azure Logic Apps.
Using apache camel for microservices and integration then deploying and managing on Docker and Kubernetes. When we need to make changes to our app, we can use Fabric8 continuous delivery built on top of Kubernetes and OpenShift.
Highlights the services in Azure that provide microservices, including App Service, Logic Apps, Functions, Azure SQL Database, Service Bus, containers, Traffic Manager, etc.
Dockerizing CS50: From Cluster to Cloud to Appliance to Container by David Ma...Docker, Inc.
CS50 is Harvard University's introduction to the intellectual enterprises of computer science and the art of programming for majors and non-majors alike. The course is Harvard's largest, with 800 students in Cambridge, as well as Yale University's largest, with 300 students in New Haven. The course is also edX's largest MOOC, with 700,000 registrants online.
Prior to 2008, the course relied on a load-balanced cluster of Linux machines on campus on which students had shell accounts with which to write and debug code. In 2008, we moved the course into the cloud, replicating that infrastructure with virtual machines (VMs) using Amazon EC2. And in 2009, we moved those VMs back on campus using VMware ESX. Our goals were both technical and pedagogical. As computer scientists, we wanted more control over our course's infrastructure. As teachers, we wanted easier access to our students' work as well as the ability to grow and shrink our infrastructure as problem sets' computational requirements demanded.
In 2011, though, we replaced our centralized infrastructure with the CS50 Appliance, a client-side VM for students' own laptops and desktops. Not only did the appliance enable us to provide students with more familiar graphical interfaces, it also enabled us to provide students with their own local servers. Moreover, the appliance ensured that the course's workload no longer required constant Internet access, particularly of students abroad. And the appliance alleviated load on the course's servers, with execution of students' programs now distributed across students' own CPUs.
In 2015, we began to Dockerize the course, replacing the CS50 Appliance with CS50 IDE, a web-based equivalent based on Cloud9, underneath which is a container for each student. We also began to migrate the course's own web apps to Docker. Among our goals were to ease deployment, isolate services, and equip the course's developers with identical environments.
We present in this talk what we did right, what we did wrong, and how we did both.
YouTube Link: https://youtu.be/sNxli6VwQTs
**DevOps Certification Courses - https://www.edureka.co/devops-certification-training**
This Edureka PPT on ‘Docker architecture’ will discuss the underlying architecture of Docker and the various components that constitute the architecture.
This PPT will focus on pointers like:
0:58 Traditional vs Docker
3:58 Docker Workflow
5:18 Docker Architecture
5:38 Docker Client
5:56 Docker Host
6:47 Docker Objects
11:11 Docker Registry
Follow us to never miss an update in the future.
YouTube: https://www.youtube.com/user/edurekaIN
Instagram: https://www.instagram.com/edureka_learning/
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
Castbox: https://castbox.fm/networks/505?country=in
Using Packer to Migrate XenServer Infrastructure to CloudStackTim Mackey
When adopting IaaS cloud solutions, one of the biggest challenges will be template management. Creating that first template can easily be more challenging that deploying the cloud software itself. In this presentation two options are presented for template creation, using a kickstart file or cloning a running VM with Packer from packer.io as the core framework.
This presentation was delivered at CloudStack Days 2015 in Austin Texas. Two demos were given. The first demo used an existing XenServer environment to create a golden master from ISO and kickstart file, then automatically upload it to a CloudStack management server for deployment. The second demo cloned a running VM and created a template which was then uploaded to CloudStack. In the case of the running VM, migration occurred without any user interruption. The VM in question was a CentOS 7 image, and the hypervisor for both source infrastructure and CloudStack compute was XenServer based
First steps into developing an application as a suite of small services, and analysis of tools and architecture approaches to be used.
Topics covered:
1) What is a micro service architecture
2)Advantages in code procedures, team dynamics and scaling
3) How container services such as docker assist in its implementation
4) How to deploy code in a micro services architecture
5) Container Management tools and resource efficiency (mesos, kubernetes, aws container service)
6) Scaling up
By PeoplePerHour team
presented by CTO Spyros Lambrinidis & Senior DevOps Panagiotis Moustafellos @ Docker Athens Meetup 18/02/2015
This talk covered the OpenStack basics that VMware Administrators need to be aware of to be successful in their deployments. We also had the Tesora team join us on stage to discuss the importance of Database-as-a-Service with the Trove project!
DCSF19 Transforming a 15+ Year Old Semiconductor Manufacturing EnvironmentDocker, Inc.
Jeanie Schwenk, Jireh Semiconductor
Jireh Semiconductor bought the Hillsboro fab and its contents including the manufacturing tools, servers, and software running the fab. The previous company had been winding down for years so server and software upgrades had not been on the radar for some time. In 2011 Jireh became the proud owner of the building, the tools, and its legacy software running on servers that weren’t even made any more.
That's when I started my adventure with Jireh in September 2016 with a charter to modernize the applications running the manufacturing facility process and move them into VMs with no impact to manufacturing. That led me down a path of exploration and questions. “What’s the goal?”
The goal wasn't to move to VMs. It was to become independent of the aging PA-RISC architecture, bring forward the ~230 java 1.4.2 applications (10-15 years old), scale to allow increased the load on the software and hardware in order to ramp the factory output to numbers never seen previously. And do it without manufacturing downtime.
The solution included a transition from waterfall and silo development to agile scrum. Rather than simply migrating to VMs, it became obvious the lynch pin for a successful software transition with the required uptime, flexibility, and scalability was Docker Enterprise.
Join me for this session where I'll talk about my journey modernizing 15+ year old applications and infrastructure at Jireh.
(SCALE 12x) OpenStack vs. VMware - A System Administrator PerspectiveStackStorm
By Dmitri Zimine, CTO of StackStorm (www.stackstorm.com)
SCALE 12x Conference
February 22, 2014
Los Angeles, CA
VMware has achieved broad usage, with some studies indicating that 80% or more of enterprises now use some VMware products. OpenStack, on the other hand, has quickly become the most important OpenSource community since Linux itself.
What’s it like to use OpenStack for virtualization and private cloud? And how does that compare to VMware’s solutions?
User Transparent Service Migration to the CloudTim Mackey
While creating a cloud such as OpenStack is fairly easy, template management is more challenging. In this session we discuss how systems engineering and tooling can be combined to allow legacy infrastructure and virtual machines to be converted to templates without downtime. These templates can then be deployed within the cloud and users migrated with minimal interruption. This deck is as delivered at CloudOpen 2015 in Seattle.
Netflix Open Source Meetup Season 4 Episode 3aspyker
In this episode, we will focus on security in the cloud at scale. We’ll have Netflix speakers discussing existing and upcoming security-related OSS releases, and we’ll also have external speakers from organizations that are using and contributing to Netflix security OSS.
First, Patrick Kelley from Netflix’s Security Operations team will speak about RepoMan, an upcoming OSS release designed to right-size AWS permissions. Then, Wes Miaw from Netflix’s Security Engineering team will discuss MSL (Message Security Layer).
We have two external speakers for this event - Chris Dorros from OpenDNS/Cisco will talk about his use of and contributions to Lemur, and Ryan Lane from Lyft will talk about their use of BLESS.
After the talks, we’ll have OSS authors at demo stations to answer questions and provide demos of Netflix security OSS, including Lemur, MSL, and Security Monkey.
Speakers: Ning Kuang & Kundana Palagiri, Azure Compute
To learn more about Pivotal Cloud Foundry, visit http://www.pivotal.io/platform-as-a-service/pivotal-cloud-foundry.
Introduction to Apache CloudStack by David Nalleybuildacloud
Apache CloudStack is a mature, easy to deploy IaaS platform. That doesn't mean that it can be done without thought or preparation. Learn how CloudStack can be most efficiently deployed, and the problems to avoid in the process.
About David Nalley
David is a recovering sysadmin with a decade of experience. He’s a committer on the Apache CloudStack (incubating) project, a contributor to the Fedora Project and the Vice President of Infrastructure at the Apache Software Foundation.
DCSF 19 Modern Orchestrated IT for Enterprise CMSDocker, Inc.
Wiley’s Education Services (WES) leverages a mix of CMS platforms across their 50+ student information sites for major universities throughout the world. Traditionally these sites have been housed as part of a multi-site CMS install on a single VM, and eventually across 2 VMs. Failure of either one of these VMs would mean an outage for one or all of the hosted sites. As Wiley’s leadership looked forward, they recognized the risks involved with their current design and identified Docker as a way to mitigate these risks.
WES began their investigation in to Docker to address issues of fault tolerance, consistency, and portability. They used this opportunity to modernize their workflows and reduce risk by promoting Docker images through their dev, preview, and production environments using CI/CD. This increased their confidence in deployments and reduced the need for maintenance windows. Early in the process, WES brought in BoxBoat as subject matter experts to accelerate their migration, and architect their Docker EE solution. Through the use of well-defined workflows and persistent storage, applications are continually redeployed and restored between environments with zero downtime and no loss of data. Additionally developers can pull down and run any of the sites independently with configuration that matches production. Join this sessions to learn about the challenges and triumphs that Wiley faced when orchestrating CMS deployments in Docker!
Introduction to Docker | Docker and Kubernetes TrainingShailendra Chauhan
Learn to build modern infrastructure using docker and Kubernetes containers. Develop and deploy your ASP.NET Core application using Docker. Leverage to learn container technology to build your ASP.NET Core application.
Dockerizing CS50: From Cluster to Cloud to Appliance to Container by David Ma...Docker, Inc.
CS50 is Harvard University's introduction to the intellectual enterprises of computer science and the art of programming for majors and non-majors alike. The course is Harvard's largest, with 800 students in Cambridge, as well as Yale University's largest, with 300 students in New Haven. The course is also edX's largest MOOC, with 700,000 registrants online.
Prior to 2008, the course relied on a load-balanced cluster of Linux machines on campus on which students had shell accounts with which to write and debug code. In 2008, we moved the course into the cloud, replicating that infrastructure with virtual machines (VMs) using Amazon EC2. And in 2009, we moved those VMs back on campus using VMware ESX. Our goals were both technical and pedagogical. As computer scientists, we wanted more control over our course's infrastructure. As teachers, we wanted easier access to our students' work as well as the ability to grow and shrink our infrastructure as problem sets' computational requirements demanded.
In 2011, though, we replaced our centralized infrastructure with the CS50 Appliance, a client-side VM for students' own laptops and desktops. Not only did the appliance enable us to provide students with more familiar graphical interfaces, it also enabled us to provide students with their own local servers. Moreover, the appliance ensured that the course's workload no longer required constant Internet access, particularly of students abroad. And the appliance alleviated load on the course's servers, with execution of students' programs now distributed across students' own CPUs.
In 2015, we began to Dockerize the course, replacing the CS50 Appliance with CS50 IDE, a web-based equivalent based on Cloud9, underneath which is a container for each student. We also began to migrate the course's own web apps to Docker. Among our goals were to ease deployment, isolate services, and equip the course's developers with identical environments.
We present in this talk what we did right, what we did wrong, and how we did both.
YouTube Link: https://youtu.be/sNxli6VwQTs
**DevOps Certification Courses - https://www.edureka.co/devops-certification-training**
This Edureka PPT on ‘Docker architecture’ will discuss the underlying architecture of Docker and the various components that constitute the architecture.
This PPT will focus on pointers like:
0:58 Traditional vs Docker
3:58 Docker Workflow
5:18 Docker Architecture
5:38 Docker Client
5:56 Docker Host
6:47 Docker Objects
11:11 Docker Registry
Follow us to never miss an update in the future.
YouTube: https://www.youtube.com/user/edurekaIN
Instagram: https://www.instagram.com/edureka_learning/
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
Castbox: https://castbox.fm/networks/505?country=in
Using Packer to Migrate XenServer Infrastructure to CloudStackTim Mackey
When adopting IaaS cloud solutions, one of the biggest challenges will be template management. Creating that first template can easily be more challenging that deploying the cloud software itself. In this presentation two options are presented for template creation, using a kickstart file or cloning a running VM with Packer from packer.io as the core framework.
This presentation was delivered at CloudStack Days 2015 in Austin Texas. Two demos were given. The first demo used an existing XenServer environment to create a golden master from ISO and kickstart file, then automatically upload it to a CloudStack management server for deployment. The second demo cloned a running VM and created a template which was then uploaded to CloudStack. In the case of the running VM, migration occurred without any user interruption. The VM in question was a CentOS 7 image, and the hypervisor for both source infrastructure and CloudStack compute was XenServer based
First steps into developing an application as a suite of small services, and analysis of tools and architecture approaches to be used.
Topics covered:
1) What is a micro service architecture
2)Advantages in code procedures, team dynamics and scaling
3) How container services such as docker assist in its implementation
4) How to deploy code in a micro services architecture
5) Container Management tools and resource efficiency (mesos, kubernetes, aws container service)
6) Scaling up
By PeoplePerHour team
presented by CTO Spyros Lambrinidis & Senior DevOps Panagiotis Moustafellos @ Docker Athens Meetup 18/02/2015
This talk covered the OpenStack basics that VMware Administrators need to be aware of to be successful in their deployments. We also had the Tesora team join us on stage to discuss the importance of Database-as-a-Service with the Trove project!
DCSF19 Transforming a 15+ Year Old Semiconductor Manufacturing EnvironmentDocker, Inc.
Jeanie Schwenk, Jireh Semiconductor
Jireh Semiconductor bought the Hillsboro fab and its contents including the manufacturing tools, servers, and software running the fab. The previous company had been winding down for years so server and software upgrades had not been on the radar for some time. In 2011 Jireh became the proud owner of the building, the tools, and its legacy software running on servers that weren’t even made any more.
That's when I started my adventure with Jireh in September 2016 with a charter to modernize the applications running the manufacturing facility process and move them into VMs with no impact to manufacturing. That led me down a path of exploration and questions. “What’s the goal?”
The goal wasn't to move to VMs. It was to become independent of the aging PA-RISC architecture, bring forward the ~230 java 1.4.2 applications (10-15 years old), scale to allow increased the load on the software and hardware in order to ramp the factory output to numbers never seen previously. And do it without manufacturing downtime.
The solution included a transition from waterfall and silo development to agile scrum. Rather than simply migrating to VMs, it became obvious the lynch pin for a successful software transition with the required uptime, flexibility, and scalability was Docker Enterprise.
Join me for this session where I'll talk about my journey modernizing 15+ year old applications and infrastructure at Jireh.
(SCALE 12x) OpenStack vs. VMware - A System Administrator PerspectiveStackStorm
By Dmitri Zimine, CTO of StackStorm (www.stackstorm.com)
SCALE 12x Conference
February 22, 2014
Los Angeles, CA
VMware has achieved broad usage, with some studies indicating that 80% or more of enterprises now use some VMware products. OpenStack, on the other hand, has quickly become the most important OpenSource community since Linux itself.
What’s it like to use OpenStack for virtualization and private cloud? And how does that compare to VMware’s solutions?
User Transparent Service Migration to the CloudTim Mackey
While creating a cloud such as OpenStack is fairly easy, template management is more challenging. In this session we discuss how systems engineering and tooling can be combined to allow legacy infrastructure and virtual machines to be converted to templates without downtime. These templates can then be deployed within the cloud and users migrated with minimal interruption. This deck is as delivered at CloudOpen 2015 in Seattle.
Netflix Open Source Meetup Season 4 Episode 3aspyker
In this episode, we will focus on security in the cloud at scale. We’ll have Netflix speakers discussing existing and upcoming security-related OSS releases, and we’ll also have external speakers from organizations that are using and contributing to Netflix security OSS.
First, Patrick Kelley from Netflix’s Security Operations team will speak about RepoMan, an upcoming OSS release designed to right-size AWS permissions. Then, Wes Miaw from Netflix’s Security Engineering team will discuss MSL (Message Security Layer).
We have two external speakers for this event - Chris Dorros from OpenDNS/Cisco will talk about his use of and contributions to Lemur, and Ryan Lane from Lyft will talk about their use of BLESS.
After the talks, we’ll have OSS authors at demo stations to answer questions and provide demos of Netflix security OSS, including Lemur, MSL, and Security Monkey.
Speakers: Ning Kuang & Kundana Palagiri, Azure Compute
To learn more about Pivotal Cloud Foundry, visit http://www.pivotal.io/platform-as-a-service/pivotal-cloud-foundry.
Introduction to Apache CloudStack by David Nalleybuildacloud
Apache CloudStack is a mature, easy to deploy IaaS platform. That doesn't mean that it can be done without thought or preparation. Learn how CloudStack can be most efficiently deployed, and the problems to avoid in the process.
About David Nalley
David is a recovering sysadmin with a decade of experience. He’s a committer on the Apache CloudStack (incubating) project, a contributor to the Fedora Project and the Vice President of Infrastructure at the Apache Software Foundation.
DCSF 19 Modern Orchestrated IT for Enterprise CMSDocker, Inc.
Wiley’s Education Services (WES) leverages a mix of CMS platforms across their 50+ student information sites for major universities throughout the world. Traditionally these sites have been housed as part of a multi-site CMS install on a single VM, and eventually across 2 VMs. Failure of either one of these VMs would mean an outage for one or all of the hosted sites. As Wiley’s leadership looked forward, they recognized the risks involved with their current design and identified Docker as a way to mitigate these risks.
WES began their investigation in to Docker to address issues of fault tolerance, consistency, and portability. They used this opportunity to modernize their workflows and reduce risk by promoting Docker images through their dev, preview, and production environments using CI/CD. This increased their confidence in deployments and reduced the need for maintenance windows. Early in the process, WES brought in BoxBoat as subject matter experts to accelerate their migration, and architect their Docker EE solution. Through the use of well-defined workflows and persistent storage, applications are continually redeployed and restored between environments with zero downtime and no loss of data. Additionally developers can pull down and run any of the sites independently with configuration that matches production. Join this sessions to learn about the challenges and triumphs that Wiley faced when orchestrating CMS deployments in Docker!
Introduction to Docker | Docker and Kubernetes TrainingShailendra Chauhan
Learn to build modern infrastructure using docker and Kubernetes containers. Develop and deploy your ASP.NET Core application using Docker. Leverage to learn container technology to build your ASP.NET Core application.
Serverless Toronto User Group - Let's go Serverless!Daniel Zivkovic
Presentation slides from the first Toronto Kickoff Meetup. Topics covered:
1. Debunking Serverless Myths
2. How did we get here? Serverless past, present and the future
3. Serverless vs. FaaS vs. BaaS
4. Products Landscape
5. Popular Use Cases & Design Patterns
6. How to leverage The Serverless Framework to start building cloud-native applications!
7. Serverless forecast: How big will serverless be?
8. Learning Serverless & Serverless Tips
9. Adopting Serverless in your organization
10. Planning Serverless Toronto next steps...
[Capitole du Libre] #serverless - mettez-le en oeuvre dans votre entreprise...Ludovic Piot
Tout comme le Cloud IaaS avant lui, le serverless promet de faciliter le succès de vos projets en accélérant le Time to Market et en fluidifiant les relations entre Devs et Ops.
Mais sa mise en œuvre au sein d’une entreprise reste complexe et coûteuse.
Après 2 ans à mettre en place des plateformes managées de ce type, nous partagons nos expériences de ce qu’il faut faire pour mettre en œuvre du serverless en entreprise, en évitant les douleurs et en limitant les contraintes au maximum.
Tout d’abord l’architecture technique, avec 2 implémentations très différentes : Kubernetes et Helm d’un côté, Clever Cloud on-premise de l’autre.
Ensuite, la mise en place et l’utilisation d’OpenFaaS. Comment tester et versionner du Function as a Service. Mais aussi les problématiques de blue/green deployment, de rolling update, d’A/B testing. Comment diagnostiquer rapidement les dépendances et les communications entre services.
Enfin, en abordant les sujets chers à la production : * vulnerability management et patch management, * hétérogénéïté du parc, * monitoring et alerting, * gestion des stacks obsolètes, etc.
This presentation explains what serverless is all about, explaining the context from Devs & Ops points of view, and presenting the various ways to achieve serverless (Functions a as Service, BaaS....). It also presents the various competitors on the market and demo one of them, openfaas. Finally, it enlarges the pictures, positionning serverless, combined with Edge computing & IoT, as a valuable triptic cloud vendors are leveraging on top of, to create end-to-end offers.
Best of re:Invent 2016 meetup presentationLahav Savir
At re:Invent 2016, AWS announced major and exciting services which finalized their product pipeline providing customers with a comprehensive end-to-end solution in all product realms including Data and BI, CI/ CD, Serverless Applications, Security and Mobile. Join us and find out what’s coming next and learn how to utilize the complete AWS platform.
(RivieraDev 2018) #serverless - 2 ans de retourS d'expérienceLudovic Piot
Le serverless est le buzzword du moment. Il a même une conférence à son nom ! :smile:
Et à juste titre !
Comme le Cloud IaaS avant lui, il promet de fluidifier la collaboration entre les devs et les ops et d'accélérer le fameux Time to Market des projets.
Il faut reconnaître que bon nombre de technos facilitent plus que jamais sa mise en œuvre : Infra as Code, cloud public, Docker, Kubernetes…
Oui mais… Comment s'est passé le dernier projet de cloud privé dans votre entreprise ? Et le run de production, ça va ? A quel prix ? Alors imaginez les efforts et les coûts nécessaires pour implémenter cette plateforme, encore plus complexe, à la stack technique encore plus riche, plus dente !
Dans cette session, nous irons au-delà du POC et de la démonstration du potentiel de ces technologies.
Nous vous présenterons comment nous gérons, depuis 2 ans, en 24/7, des plateformes serverless de production.
Leur implémentation, à base de Terraform / Ansible / Kubernetes, dans le Cloud public IaaS, ou on-premise, sur du VMware. Ou bien à base du savoir-faire de Clever Cloud sur du bare-metal. Les adaptations organisationnelles que ça implique entre les Devs et les Ops. La gestion des patches et des vulnérabilités au quotidien. La gestion de la supervision et de l'alerting de la plateforme et des stacks techniques embarquées.
Since AWS launched Lambda in 2014, the term “serverless” has been used (and misused) to describe compute models, technologies, architectural patterns, operational constructs, and even rebranded cgi-bins. The term is now used so broadly that it’s turning into a buzzword with no discernible meaning.
In this talk, we’ll cut through all the marketing hype, and discuss why the underlying concept of “serverless”, and the superpowers that come with it, are much more important than the name itself.
AWS Serverless Community Day Keynote and Vendia Launch 6-26-2020Tim Wagner
Hear Tim Wagner, CEO and co-founder of Vendia and "Father of Serverless" talk about the evolution of Serverless over the years and how Vendia is taking it into a cross-cloud future.
Introduction to amazon web services for developersCiklum Ukraine
Introduction to Amazon Web Services for developers
About presenter
Roman Gomolko with 11 years of experience in development including 4 years of day-to-day work with Amazon Web Services.
Disclaimer
Cloud-hosting is buzz-word for a while and in my talk I would like to give an introduction to Amazon Web Services (AWS).
We will talk about basic building blocks of AWS like EC2, ELB, ASG, S3, CloudFront, RDS, IAM, VPC and other scary or funny abbreviations.
Then we will discuss how to migrate existing applications to AWS. This topic includes:
• how to design infrastructure and services to use when migrating
• how to choose proper instance types
• how to estimate infrastructure cost
• how it will affect performance of application migrated
Then we will make an overview of services provided by AWS and possible apply in your current of future applications:
• SQS
• DynamoDB
• Kinesis
• CloudSearch
• CodeDeploy
• CloudFormation
And if we survive we will talk a little how to design Cloud applications. That’s mainly about general principles.
My talk mostly targeted towards decision makers and decisions pushers of small and medium size companies which are consider “going cloud” or already moving into this direction. Everyone interested in gaining knowledge in these areas are welcomed as well.
We will spend around 2–3 hours together and you will be able to pitch-in any questions until we totally goes away from original plan.
Cloud computing is a type of Internet-based computing that provides shared computer processing resources and data to computers and other devices on demand. It is a model for enabling ubiquitous, on-demand access to a shared pool of configurable computing resources (e.g., computer networks, servers, storage, applications and services),
Serverless Apps on Google Cloud: more dev, less opsJoseph Lust
Serverless on GCP is a perfect match to do more dev and less ops. We discuss the many GCP serverless services used @ mabl and how they reduce both time to market and operating expenses. We focus on the nuances of Google Cloud Functions and many way to optimize your serverless apps.
Serverless Apps on Google Cloud: more dev, less opsmabl
From mabl Software Engineer Joseph Lust.
Serverless on GCP is a perfect match to do more dev and less ops. We discuss the many GCP serverless services used @ mabl and how they reduce both time to market and operating expenses. We focus on the nuances of Google Cloud Functions and many way to optimize your serverless apps.
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
1. THE NEXT BIG THING:
SERVERLESS
Doug Vanderweide
@dougvdotcom
linkedin.com/in/dougvdotcom
doug@linuxacademy.com
2. Before we
start …
■ If you need to step out, please do so. Please return if
you can! Just do so as inconspicuously as possible,
thank you
■ Help yourself to drinks in the cooler to your right
■ Bathrooms: To the left of the room
■ Emergency exits: Just past the bathroom; also, same
way you entered
■ Need to take a call/text/email/Slack? Please step
out to the lobby
3. About me
■ Microsoft Certified Solutions Developer: Azure Solutions Architect
■ Microsoft Certified Solutions Expert: Cloud Platform and Infrastructure
■ CompTIA CTT+ Certified Technical Trainer
■ 20+ years in Web development (LAMP/.NET) and DevOps
■ Built real-world serverless solutions
■ Azure instructor / SME for Linux Academy
■ I know next to nothing about Linux
4. BUT ENOUGH ABOUT ME …
Let's talk about you. Or, more specifically, your DevOps.
7. In the beginning
■ Cloud-based virtual machines appear ~2006 (EC2, AWS)
■ and they're AWESOME
■ Significant savings over on-prem bare metal
■ Provision what you need, discard it when done
■ Quick provisioning (hours, not weeks)
■ Theoretically bulletproof
– One breaks? Make another from same image
– Better yet, make 2; they're cheap
8. And then everything is terrible again
■ "Lift-and-shift" workloads have all their old problems, with
all-new security and connectivity problems added in
■ We wind up replicating on-prem solutions to cloud-based
issues, such as routing, ACLs, gateways, etc.
■ You're still administering servers and networks and it's still
awful, terrible work
■ Same orchestration/DevOps experience as on-prem
9. The dawn of 'Platform as a Service'
■ Google App Engine (2007), Elastic Beanstalk (AWS, 2011) ,
Cloud Services (~2010, Micosoft Azure)
■ Mostly Web-based workloads
■ Abstracts underlying OS and runtime configurations with
pre-defined offerings
■ Easier to scale to demand (scale in-out)/failover than IaaS
machines
■ Faster deployment times
10. Cloud matures with supporting services
■ Databases as a Service (SimpleDB/RDS/DynamoDB, AWS; Azure SQL
Database/CosmosDB, Azure)
■ Message queues (SQS/SNS, AWS; Service Bus/Notification Hubs,
Azure)
■ DNS-based solutions (Route 53, AWS; Traffic Manager, Azure)
■ Content delivery networks (CloudFront, AWS; Azure CDN)
■ These tools enable simpler balancing of workloads and the
emergence of microservices architecture
12. Microservices: A new pattern
■ Break tasks into smaller workloads
■ Build these workloads as HTTP-based APIs
– or event/message listeners
■ Communicate status via queues and triggers/webhooks
■ Recycle common workloads among solutions
18. Containers make microservices work
■ Build container to meet a workload
– Create as needed
– Destroy when done
■ Deploy multiple containers to a single host
– Scale container to meet workload
■ Move containers among hosts seamlessly
■ Repeatable results
■ Automation, automation, automation!
20. What the
world needs
now …
■ Lightning-fast deployment
■ Maximum automation
– build
– deployment
– monitoring
– resilience
■ Predicatable, repeatable
results
■ Built-in high availability /
disaster recovery /
business continuity
22. server·less
ˈsərvərləs (adj)
via Wikipedia
a cloud computing code execution model
in which the cloud provider
fully manages starting and stopping of
a function's container platform as a service (PaaS)
as necessary to serve requests,
and requests are billed by an abstract measure
of the resources required to satisfy the request,
rather than per virtual machine, per hour.
23. Serverless features
■ You write code that runs on the platform; the provider does
the rest
■ Anonymous, generalized virtual machine instances
■ Completely managed by the cloud provider
■ Provisioned when you need them, deprovisioned when
you're done
■ Billed by executions and resource consumption, not an
hourly rate
27. Serverless function features
■ Base OS (Linux, Windows) with a generalized config
■ Supports any code written in a given language: Node.js,
Python, .NET Core, Java, etc.
■ Provider can quickly provision these instances because
they're all the same
■ Instance started > code retrieved > code executed >
instance deprovisioned
29. Serverless features
■ Instances started as needed, stopped when inactive
– Less sprawl
– Truly pay for what you use
■ Open architecture supports service reuse
■ No server management = less operations
■ Allows you to focus on the code, not infrastructure
31. Pricing models
■ VMs: Pay per CPU core, memory use, disk storage, software
fees
■ Containers: Also pay for VM use, but pack more work into
the same VM
■ Serverless: Pay for the resources you actually use
32. VM vs serverless pricing
Azure VM D2v2 AWS VM t2.large Azure Function AWS Lambda
$104.16 $69.94 $25.60 $26.67
Assumption:
• 500,000 executions per month
• 4 GB-secs for each execution
33. VM vs serverless pricing
Azure VM
A4m v2
AWS VM
t2.2xlarge
Azure Function AWS Lambda
$220.97 $279.74 $121.80 $129.86
Assumption:
• 2 million executions per month
• 4 GB-secs for each execution
34. VM vs serverless pricing
Azure VM A1v2 AWS VM t2.small Azure Function AWS Lambda
$31.99 $17.12 FREE FREE
Assumption:
• 20,000 executions per month
• 512 MB-secs for each execution
35. The serverless 'long tail'
■ Everything the same = dirt cheap to provide
■ Each new instance is effectively profitable
■ Only a small number of users need to exceed the free
threshold periodically to turn a major profit
■ Long-tail pricing model
36. Serverless vs VMs
(and to a lesser degree, containers)
■ Similar workloads cost
less to run
■ You don't pay for unused
capacity
■ No more sprawl
■ No "Detroit dilemmas"
37. NOT QUITE 'NO OPS'
But drastically reduced lead times and staffing requirements
38. 'No Ops'
■ Automation, abstraction and cloud vendor services
eliminate several DevOps tasks (and positions)
– build and deployment
■ Sprint develop, build, test and deploy
■ Focus is shifted to rapid development
■ Continuous integration / deployment
■ Extensive monitoring and metrics
39. Highly available, easily scaled
■ Bad code downtime limited by microservices
■ Functions scale automatically and quickly
■ High availability is built in
■ Regional outage is the only real threat
– Use standard cloud business continuity strategies
■ e.g., multi-region presence, DNS-based switchover
40. Serverless recap
■ Lower real infrastructure costs
■ Easier SDLC via modular workloads/microservices
■ No servers to manage
■ Faster deployment via CI/CD/automation
■ HA/DR built in
■ Usual cloud-based business continuity strategies
42. With AWS Lambda, we eliminate the need
to worry about operations.
We just write code, deploy it, and it scales infinitely;
no one really has to deal with
infrastructure management.
The size of our team is half of what is normally needed
to build and operate a site of this scale.
-- Tyler Love, CTO, Bustle
43. In 5 years, every modern business will have
a substantial portion of their systems
running the cloud.
But that’s only the first step.
The next step comes when you
free your developers from the tedious work
of configuring and deploying
even virtual cloud-based servers.
-- Greg DeMichillie, Head of Developer Platform and Infrastructure, Adobe
44. Workflows for the masses
■ What if everyone could program?
■ Microservices are the building blocks of workflows
■ AI/big data are already tacking semantics
■ Orchestrate your vision, yourself
45.
46. The combination of multi-device,
AI everywhere
and serverless computing
is driving this new era of intelligent cloud and
intelligent edge.
-- Microsoft
48. Starting over is expensive
■ Microservices mean
rebuilding workloads
■ Huge up-front costs
■ Requires revisiting
existing partnerships
■ N-tier ports well to
containers
49. When containers/VMs
are a better choice
■ Small, non-scaling workloads
■ Solutions that depend on the environment/many services
■ Massive, constant computing power requirements
50. Serverless weaknesses
■ Laggy startups for cold code
■ Lag/drops in microservice communication
■ Immature technology
■ Somewhat wedded to the vendor
■ Restrictions in code you can run
■ Somewhat limited library access
■ Event-input-output model might not work
51. In summary ■ Serverless is the next wave in
cloud computing
■ Huge time and cost savings,
low TCO
■ Significant benefits to cloud
vendors
■ Built-in HA/DR, business
continuity is simple
■ Fast deployment and sensible
architecture
■ But it's not for every workload
52. Your turn:
Questions? Insights? Let's talk!
@dougvdotcom
linkedin.com/in/dougvdotcom
doug@linuxacademy.com
Thanks to Linux Academy for the space,
food and swag!
https://linuxacademy.com
This deck:
Our Meetup group:
https://www.meetup.com/Keller-Cloud-
Computing-Group/
