The slide deck from our meetup at Booxware Karlsruhe on 2017-06-21.
Meetup: https://www.meetup.com/booxware-events/events/239298065/
Talk: https://www.youtube.com/watch?v=CgQ0DsKHSyg
Demo: https://youtu.be/CgQ0DsKHSyg?t=1452
This document summarizes the challenges of automating the build and deployment of a legacy application at Cable & Wireless Communications (CWC). It faced issues like multiple version control systems, separate build tools for each tier, and a reliance on highly skilled individuals. To address this, CWC adopted a continuous integration/delivery approach using Subversion as the single version control system, Jenkins as the build server, and DeployIt for managing deployments. This simplified the process and reduced risk by removing dependencies on specific skills or people.
The Fn project is a container-native Apache 2.0 licensed serverless platform that you can run anywhere – on any cloud or on-premise. It’s easy to use, supports every programming language, and is extensible and performant. This YourStory-Oracle Developer Meetup covers various design aspects of Serverless for polyglot programming, implementation of Saga pattern, etc. It also emphasizes on the monitoring aspect of Fn project using Prometheus and Grafana
Rising Above the Noise: Continuous Integration, Delivery and DevOpsIBM UrbanCode Products
This document discusses continuous integration (CI), continuous delivery (CD), and DevOps. It defines CI as integrating code frequently through automated testing to determine code quality. CD builds on CI by automatically deploying code through test environments to production. DevOps aims to break down silos between development and operations by automating infrastructure and deployment. The future will see more private clouds, platform as a service, and tools that integrate CI, deployment automation, and environment provisioning.
Docker is a containerization platform that packages applications into standardized units called containers. Azure Container Service simplifies creating clusters of virtual machines preconfigured to run containerized applications using open-source orchestration tools like Docker Swarm, DC/OS, and Kubernetes. The presentation demonstrated Docker and container orchestration on Azure through Visual Studio tools for building, debugging, and deploying containerized applications as well as a continuous integration/deployment pipeline using DC/OS on Azure Container Service.
Unified Deployment: Including the Mainframe in Enterprise DevOpsXebiaLabs
Compuware’s Mark Schettenhelm and XebiaLabs’ Tim Buntel demo and discuss how the integration between Compuware’s ISPW mainframe DevOps solution and XebiaLabs’ XL Release Continuous Delivery technology helps enterprises engage in cross-platform release orchestration and create business agility.
This session will demonstrate how to use the Zowe open source framework to extend modern devops tooling and practices to the mainframe and to enhance the mainframe developer experience. A follow-up to the overview session, the hosts will drill into the Zowe architecture while demoing key capabilities including the command line interface (CLI) and API Mediation Layer.
Organized by the Linux Foundation’s Open Mainframe Project, Zowe opens the mainframe to the next generation of talent. Join this interactive session to learn how to “un-silo” the mainframe to accelerate software delivery and drive true cross-platform applications.
This document summarizes the challenges of automating the build and deployment of a legacy application at Cable & Wireless Communications (CWC). It faced issues like multiple version control systems, separate build tools for each tier, and a reliance on highly skilled individuals. To address this, CWC adopted a continuous integration/delivery approach using Subversion as the single version control system, Jenkins as the build server, and DeployIt for managing deployments. This simplified the process and reduced risk by removing dependencies on specific skills or people.
The Fn project is a container-native Apache 2.0 licensed serverless platform that you can run anywhere – on any cloud or on-premise. It’s easy to use, supports every programming language, and is extensible and performant. This YourStory-Oracle Developer Meetup covers various design aspects of Serverless for polyglot programming, implementation of Saga pattern, etc. It also emphasizes on the monitoring aspect of Fn project using Prometheus and Grafana
Rising Above the Noise: Continuous Integration, Delivery and DevOpsIBM UrbanCode Products
This document discusses continuous integration (CI), continuous delivery (CD), and DevOps. It defines CI as integrating code frequently through automated testing to determine code quality. CD builds on CI by automatically deploying code through test environments to production. DevOps aims to break down silos between development and operations by automating infrastructure and deployment. The future will see more private clouds, platform as a service, and tools that integrate CI, deployment automation, and environment provisioning.
Docker is a containerization platform that packages applications into standardized units called containers. Azure Container Service simplifies creating clusters of virtual machines preconfigured to run containerized applications using open-source orchestration tools like Docker Swarm, DC/OS, and Kubernetes. The presentation demonstrated Docker and container orchestration on Azure through Visual Studio tools for building, debugging, and deploying containerized applications as well as a continuous integration/deployment pipeline using DC/OS on Azure Container Service.
Unified Deployment: Including the Mainframe in Enterprise DevOpsXebiaLabs
Compuware’s Mark Schettenhelm and XebiaLabs’ Tim Buntel demo and discuss how the integration between Compuware’s ISPW mainframe DevOps solution and XebiaLabs’ XL Release Continuous Delivery technology helps enterprises engage in cross-platform release orchestration and create business agility.
This session will demonstrate how to use the Zowe open source framework to extend modern devops tooling and practices to the mainframe and to enhance the mainframe developer experience. A follow-up to the overview session, the hosts will drill into the Zowe architecture while demoing key capabilities including the command line interface (CLI) and API Mediation Layer.
Organized by the Linux Foundation’s Open Mainframe Project, Zowe opens the mainframe to the next generation of talent. Join this interactive session to learn how to “un-silo” the mainframe to accelerate software delivery and drive true cross-platform applications.
Containers have changed the mind of IT in DevOps. They enable developers to work with dev, test, stage and production environments identically. Containers provide the right abstraction for Microservices and many cloud platforms have integrated them into deployment pipelines. DevOps and Containers together help companies to achieve their business goals faster and more effectively. At this session we will review the current landscape of DevOps with Containers. In addition, we will discuss known issues and solutions for enterprise Java applications in Containers.
Whether you are a Zowe User, Contribor, Extender or simply interested in what's happening with Zowe - please join us for the launch of the Zowe Quarterly Update Webinar. This is the first in the series of webinars we plan to host each quarter. The webinar will include:
A focus topic / speaker
A brief Zowe update
Upcoming Community Events Overview
Interactive Polls
Join us on this webinar to learn how we are extending the Zowe ZSS (z/OS back-end) to facilitate building in-depth (cross-memory, privileged, system-level) mainframe products with little-to-no assembler code required.
DevOps for the IBM Mainframe environmentMicro Focus
Establishing a model that works across enterprise IT –
including mainframe systems
The solutions and methodologies tackling business challenges are constantly evolving. From waterfall to agile and on to continuous integration and DevOps, successful software development is about achieving the improved efficiencies needed to meet ever-growing business requirements.
DevOps - a blend of Development and Operations - is not a straightforward fit for the mainframe environment. But change is required if enterprises are going to match more agile operations in meeting efficiency targets against a background of increasing application complexity.
Successful Practices for Continuous Delivery CodeCPHMandi Walls
The document discusses successful practices for continuous delivery including:
1) Implementing dynamic infrastructure through automation of infrastructure provisioning and configuration using infrastructure as code which is versioned, tested, and repeatable.
2) Adopting a DevOps culture through practices like ubiquitous automation, continuous integration, and embedding security and compliance into software development.
3) Implementing a continuous delivery pipeline to enable rapid and low risk software releases through techniques like infrastructure and applications as code, automated testing, and consistent environments.
Introducing Serena Dimensions CM 14, Discussion and product demonstration (We...Serena Software
Serena Dimensions CM 14 introduces new capabilities including:
- Implementation of changesets and versioned streams for distributed development.
- Change and branch visualization tools to provide insight into release readiness and change timelines.
- Integrated peer review to improve code quality and collaboration.
- A native developer experience with support for mobile IDEs and integrations.
Open Source Investments in Mainframe Through the Next Generation - Showcasing...Open Mainframe Project
In it's 3rd year, the Open Mainframe Project continues to invest in the open source ecosystem on mainframe through it's summer internship program. This year's class focused on improving mainframe open source packaging and support of modern technologies such as Cloud Foundry and Kubernetes.
In this session, interns will present their work and experience in working in the internship program.
Urban code deploy helps with traditional websphere app server migrationLaurel Dickson-Bull
IBM UrbanCode Deploy is an enterprise application deployment automation utility that combines ease-of-use with fine-grain control for managing the deployment of applications through multiple environments. IBM UrbanCode automates and manages the deployments of business applications made of many component pieces such as Web Services, databases, content, CICS and mobile apps. Through automation, costly errors and manual labor are drastically reduced, time-to-market is accelerated, cost is driven down and risk is lowered. UrbanCode Deploy also provides capabilieis for designing and deploying full-stack environments on cloud and updating configurations for existing cloud environments.In the related products listing on this page we have provided subset of the strongest interactions with other IBM tools. However, IBM UrbanCode Deploy has over 180 different plugins across various types and discipline areas to provide extensive integrations. The UrbanCode family of products as whole has over 400 plugins.
The document discusses leveraging DevOps practices to improve mainframe application delivery. It describes how traditional mainframe development and testing causes delays due to shared, restricted resources and inefficient processes. The solution presented uses DevOps tools and practices like continuous integration/delivery, dependency virtualization, and automated quality testing to enable more efficient mainframe application development and testing. This allows development and operations teams to work in parallel, validate code quality earlier, and deploy applications more frequently.
An Integrated Pipeline for Private and Public Clouds with Jenkins, Artifactor...VMware Tanzu
This presentation was delivered jointly with a hands-on demo. The presentation briefly discusses how Cloud Foundry enables organizations to continuously deliver high-quality software and highlights an integrated development process built with Jenkins, Artifactory and Cloud Foundry.
This document provides information on top DevOps solution providers. It discusses the services offered by CloudBees, CloudHesive, Plutora, XenonStack, OpenMake Software, Cloudmunch, and Shippable. The services include continuous integration, continuous delivery, infrastructure automation, release management, and DevOps consulting. Pricing models vary between free trials, pay-per-use, and monthly subscriptions. The document aims to help users choose a DevOps solution that best fits their needs and budget.
Easing Cloud Migrations with Software Pipelines as a Service - Christopher J...AWS Chicago
This document discusses Morningstar's efforts to implement "Software Pipelines as a Service" (SPaaS) to help product teams migrate applications to AWS more efficiently. It describes how Morningstar developed centralized pipelines using tools like Jenkins, Chef, and Terraform that teams could use rather than building their own. While initial results were mixed, Morningstar is now taking a second pass at SPaaS using a pipeline generator that defines the structure in a declarative domain-specific language processed by ANTLR. This approach aims to provide flexibility while enforcing standard processes across teams.
Cloud and agile software projects: Overview and BenefitsGuillaume Berche
Slides from the session "Cloud and agile software projects: Overview and Benefits" at Agile Grenoble 2014, co presented by Guillaume Berche and Alain Delafosse.
http://agile-grenoble.org/
Docker allows applications to be packaged into standardized units called containers that can run on any infrastructure. IBM Bluemix supports Docker containers and provides services for building, managing, and hosting containerized applications in a hybrid cloud environment. Key benefits of Docker containers include increased portability and efficiency in development and deployment across physical and cloud infrastructure.
Feilong is a Python toolkit for managing cloud resources in a LinuxONE environment. It allows developers to create plugins that interface with the REST API to perform tasks like managing guest images, networking, and disk volumes. Feilong is installed in a "Bring Your Own Linux" virtual machine and governed by the Open Mainframe Project. It was originally created by IBM in 2017 to function as a z/VM Cloud Connector and interface with the LinuxONE hypervisor to enable management of virtual machines and resources.
Solutions for IT Organizations on The Journey to The Digital Enterpriseandreas kuncoro
This document discusses Red Hat Cloud Solutions for organizations transitioning to digital enterprises. It outlines challenges such as slow delivery, lack of agility and scalability, and siloed teams. Red Hat proposes addressing these with cloud infrastructure, DevOps practices, and policy-driven automation to accelerate delivery, optimize resources, modernize development, and deliver scalable solutions. Case studies demonstrate benefits like reduced costs, improved compliance and resource utilization. The document promotes starting with a discovery session to identify opportunities.
According to the document:
1. Phillip Shipley of Cisco's WebEx business unit discussed a recent project using Zend and VMware to deploy a new free trials platform for WebEx products.
2. The previous free trials platform was developed over many years without standards and was difficult to maintain and scale. The new platform was built from scratch using Zend Framework, Zend Server, and VMware virtualization.
3. Key benefits of the new platform included a 68% reduction in sign-up time, an 800% increase in trial completion rates, and dramatically faster times to market and increased capacity. The project aligned WebEx development with business needs and delivered significant improvements.
The document provides an overview of SAP Cloud Platform, including key use cases for integrating apps and data, extending existing cloud and on-premise apps, and building new cloud apps. It also discusses connecting people and data. Customer stories demonstrate how companies are using SAP Cloud Platform for integration, innovation, Internet of Things applications, and digital experiences. Architectural blueprints illustrate potential implementations involving SAP and non-SAP systems and applications.
To Kill a Monolith: Slaying the Demons of a Monolith with Node.js Microservic...Tony Erwin
Originally presented at CF Summit Europe 2017 in Basel, Switzerland. The abstract of the talk was:
The Bluemix UI (which runs on CloudFoundry) is the front-end to Bluemix, IBM’s open cloud hosting platform. The original implementation as a single-page, monolithic Java web app brought with it many demons, such as poor performance, lack of scalability, inability to push small updates, and difficulty for other teams to contribute code. Over the last 2 years, the team has been on a mission to slay these demons by embracing cloud native principles and splitting the monolith into smaller Node.js microservices. The effort to migrate to a more modern and scalable architecture has paid large dividends, but has also left behind a few battle scars from wrestling with the added complexity cloud native can bring. The team had to tackle problems in a wide variety of areas, including: large-scale deployments, continuous integration, monitoring, problem determination, high availability, and security. Tony Erwin will discuss the advantages of microservice architectures, ways that Node.js has increased developer productivity, approaches to phasing microservices into a live product, and real-life lessons learned in the deployment and management of Node.js microservices across multiple CloudFoundry environments. His war stories will prepare you to wage your own battles against monoliths everywhere -- happy slaying!
Containers have changed the mind of IT in DevOps. They enable developers to work with dev, test, stage and production environments identically. Containers provide the right abstraction for Microservices and many cloud platforms have integrated them into deployment pipelines. DevOps and Containers together help companies to achieve their business goals faster and more effectively. At this session we will review the current landscape of DevOps with Containers. In addition, we will discuss known issues and solutions for enterprise Java applications in Containers.
Whether you are a Zowe User, Contribor, Extender or simply interested in what's happening with Zowe - please join us for the launch of the Zowe Quarterly Update Webinar. This is the first in the series of webinars we plan to host each quarter. The webinar will include:
A focus topic / speaker
A brief Zowe update
Upcoming Community Events Overview
Interactive Polls
Join us on this webinar to learn how we are extending the Zowe ZSS (z/OS back-end) to facilitate building in-depth (cross-memory, privileged, system-level) mainframe products with little-to-no assembler code required.
DevOps for the IBM Mainframe environmentMicro Focus
Establishing a model that works across enterprise IT –
including mainframe systems
The solutions and methodologies tackling business challenges are constantly evolving. From waterfall to agile and on to continuous integration and DevOps, successful software development is about achieving the improved efficiencies needed to meet ever-growing business requirements.
DevOps - a blend of Development and Operations - is not a straightforward fit for the mainframe environment. But change is required if enterprises are going to match more agile operations in meeting efficiency targets against a background of increasing application complexity.
Successful Practices for Continuous Delivery CodeCPHMandi Walls
The document discusses successful practices for continuous delivery including:
1) Implementing dynamic infrastructure through automation of infrastructure provisioning and configuration using infrastructure as code which is versioned, tested, and repeatable.
2) Adopting a DevOps culture through practices like ubiquitous automation, continuous integration, and embedding security and compliance into software development.
3) Implementing a continuous delivery pipeline to enable rapid and low risk software releases through techniques like infrastructure and applications as code, automated testing, and consistent environments.
Introducing Serena Dimensions CM 14, Discussion and product demonstration (We...Serena Software
Serena Dimensions CM 14 introduces new capabilities including:
- Implementation of changesets and versioned streams for distributed development.
- Change and branch visualization tools to provide insight into release readiness and change timelines.
- Integrated peer review to improve code quality and collaboration.
- A native developer experience with support for mobile IDEs and integrations.
Open Source Investments in Mainframe Through the Next Generation - Showcasing...Open Mainframe Project
In it's 3rd year, the Open Mainframe Project continues to invest in the open source ecosystem on mainframe through it's summer internship program. This year's class focused on improving mainframe open source packaging and support of modern technologies such as Cloud Foundry and Kubernetes.
In this session, interns will present their work and experience in working in the internship program.
Urban code deploy helps with traditional websphere app server migrationLaurel Dickson-Bull
IBM UrbanCode Deploy is an enterprise application deployment automation utility that combines ease-of-use with fine-grain control for managing the deployment of applications through multiple environments. IBM UrbanCode automates and manages the deployments of business applications made of many component pieces such as Web Services, databases, content, CICS and mobile apps. Through automation, costly errors and manual labor are drastically reduced, time-to-market is accelerated, cost is driven down and risk is lowered. UrbanCode Deploy also provides capabilieis for designing and deploying full-stack environments on cloud and updating configurations for existing cloud environments.In the related products listing on this page we have provided subset of the strongest interactions with other IBM tools. However, IBM UrbanCode Deploy has over 180 different plugins across various types and discipline areas to provide extensive integrations. The UrbanCode family of products as whole has over 400 plugins.
The document discusses leveraging DevOps practices to improve mainframe application delivery. It describes how traditional mainframe development and testing causes delays due to shared, restricted resources and inefficient processes. The solution presented uses DevOps tools and practices like continuous integration/delivery, dependency virtualization, and automated quality testing to enable more efficient mainframe application development and testing. This allows development and operations teams to work in parallel, validate code quality earlier, and deploy applications more frequently.
An Integrated Pipeline for Private and Public Clouds with Jenkins, Artifactor...VMware Tanzu
This presentation was delivered jointly with a hands-on demo. The presentation briefly discusses how Cloud Foundry enables organizations to continuously deliver high-quality software and highlights an integrated development process built with Jenkins, Artifactory and Cloud Foundry.
This document provides information on top DevOps solution providers. It discusses the services offered by CloudBees, CloudHesive, Plutora, XenonStack, OpenMake Software, Cloudmunch, and Shippable. The services include continuous integration, continuous delivery, infrastructure automation, release management, and DevOps consulting. Pricing models vary between free trials, pay-per-use, and monthly subscriptions. The document aims to help users choose a DevOps solution that best fits their needs and budget.
Easing Cloud Migrations with Software Pipelines as a Service - Christopher J...AWS Chicago
This document discusses Morningstar's efforts to implement "Software Pipelines as a Service" (SPaaS) to help product teams migrate applications to AWS more efficiently. It describes how Morningstar developed centralized pipelines using tools like Jenkins, Chef, and Terraform that teams could use rather than building their own. While initial results were mixed, Morningstar is now taking a second pass at SPaaS using a pipeline generator that defines the structure in a declarative domain-specific language processed by ANTLR. This approach aims to provide flexibility while enforcing standard processes across teams.
Cloud and agile software projects: Overview and BenefitsGuillaume Berche
Slides from the session "Cloud and agile software projects: Overview and Benefits" at Agile Grenoble 2014, co presented by Guillaume Berche and Alain Delafosse.
http://agile-grenoble.org/
Docker allows applications to be packaged into standardized units called containers that can run on any infrastructure. IBM Bluemix supports Docker containers and provides services for building, managing, and hosting containerized applications in a hybrid cloud environment. Key benefits of Docker containers include increased portability and efficiency in development and deployment across physical and cloud infrastructure.
Feilong is a Python toolkit for managing cloud resources in a LinuxONE environment. It allows developers to create plugins that interface with the REST API to perform tasks like managing guest images, networking, and disk volumes. Feilong is installed in a "Bring Your Own Linux" virtual machine and governed by the Open Mainframe Project. It was originally created by IBM in 2017 to function as a z/VM Cloud Connector and interface with the LinuxONE hypervisor to enable management of virtual machines and resources.
Solutions for IT Organizations on The Journey to The Digital Enterpriseandreas kuncoro
This document discusses Red Hat Cloud Solutions for organizations transitioning to digital enterprises. It outlines challenges such as slow delivery, lack of agility and scalability, and siloed teams. Red Hat proposes addressing these with cloud infrastructure, DevOps practices, and policy-driven automation to accelerate delivery, optimize resources, modernize development, and deliver scalable solutions. Case studies demonstrate benefits like reduced costs, improved compliance and resource utilization. The document promotes starting with a discovery session to identify opportunities.
According to the document:
1. Phillip Shipley of Cisco's WebEx business unit discussed a recent project using Zend and VMware to deploy a new free trials platform for WebEx products.
2. The previous free trials platform was developed over many years without standards and was difficult to maintain and scale. The new platform was built from scratch using Zend Framework, Zend Server, and VMware virtualization.
3. Key benefits of the new platform included a 68% reduction in sign-up time, an 800% increase in trial completion rates, and dramatically faster times to market and increased capacity. The project aligned WebEx development with business needs and delivered significant improvements.
The document provides an overview of SAP Cloud Platform, including key use cases for integrating apps and data, extending existing cloud and on-premise apps, and building new cloud apps. It also discusses connecting people and data. Customer stories demonstrate how companies are using SAP Cloud Platform for integration, innovation, Internet of Things applications, and digital experiences. Architectural blueprints illustrate potential implementations involving SAP and non-SAP systems and applications.
To Kill a Monolith: Slaying the Demons of a Monolith with Node.js Microservic...Tony Erwin
Originally presented at CF Summit Europe 2017 in Basel, Switzerland. The abstract of the talk was:
The Bluemix UI (which runs on CloudFoundry) is the front-end to Bluemix, IBM’s open cloud hosting platform. The original implementation as a single-page, monolithic Java web app brought with it many demons, such as poor performance, lack of scalability, inability to push small updates, and difficulty for other teams to contribute code. Over the last 2 years, the team has been on a mission to slay these demons by embracing cloud native principles and splitting the monolith into smaller Node.js microservices. The effort to migrate to a more modern and scalable architecture has paid large dividends, but has also left behind a few battle scars from wrestling with the added complexity cloud native can bring. The team had to tackle problems in a wide variety of areas, including: large-scale deployments, continuous integration, monitoring, problem determination, high availability, and security. Tony Erwin will discuss the advantages of microservice architectures, ways that Node.js has increased developer productivity, approaches to phasing microservices into a live product, and real-life lessons learned in the deployment and management of Node.js microservices across multiple CloudFoundry environments. His war stories will prepare you to wage your own battles against monoliths everywhere -- happy slaying!
This document provides an overview of Cloud Foundry, including:
1. Cloud Foundry is an open source platform as a service that allows developers to build, test, deploy and scale applications.
2. Cloud Foundry uses a distributed architecture that is self-healing with no single point of failure to allow for horizontal scaling.
3. The Cloud Foundry architecture includes layers like the cloud controller, stager, DEA execution agents, services, router, and uses BOSH for automated virtual infrastructure deployment and management of Cloud Foundry clusters.
C* Summit 2013: Cassandra on Cloud Foundry by Renat Khasanshyn and Cornelia D...DataStax Academy
Speakers: Renat Khasanshyn, Founder and CEO at Altoros and Cornelia Davis, Senior Technologist at Pivotal
Coupling Cassandra with a Platform as a Service may significantly simplify the process of deploying Cassandra and applications that utilize it, reduce the cost of managing Cassandra within the organization, and to allow infrastructure service providers a simple path to offering database as a service to their customers. Attendees will learn why and when use Cassandra atop of Cloud Foundry, the history of Cassandra service within Cloud Foundry, the State of Cassandra integration with Cloud Foundry, how to create and manage Cassandra nodes on Cloud Foundry and what to expect in the next 6 months.
This document summarizes a presentation about Docker and microservices and what they mean for enterprise DevOps strategies. It discusses what Docker and microservices are, how they will impact development, operations, and other teams. It recommends that enterprises investigate these technologies, understand how to integrate them into existing systems and processes, and quantify the potential business benefits before adopting them. The presentation also discusses how the tool vendor XebiaLabs is helping customers prepare for and adopt containers and microservices.
Docker concepts and microservices architecture are discussed. Key points include:
- Microservices architecture involves breaking applications into small, independent services that communicate over well-defined APIs. Each service runs in its own process and communicates through lightweight mechanisms like REST/HTTP.
- Docker allows packaging and running applications securely isolated in lightweight containers from their dependencies and libraries. Docker images are used to launch containers which appear as isolated Linux systems running on the host.
- Common Docker commands demonstrated include pulling public images, running interactive containers, building custom images with Dockerfiles, and publishing images to Docker Hub registry.
Modern apps in a microservices age May meet up Architecting for InnovationAndrew Blades
The document discusses how modern applications are built and managed. It describes how:
1) Traditionally, organizations used siloed teams and waterfall development methods that resulted in long development cycles.
2) Modern applications are built as modular microservices architectures using containers, serverless functions, and other cloud technologies to increase agility.
3) DevOps practices emphasize self-sufficient teams that have full responsibility for applications from development to operations.
4) MongoDB Atlas allows development teams to easily manage the database tier of their containerized microservices applications without operating database infrastructure themselves.
The document discusses the shift towards cloud native application development. Some key points discussed include:
1. Cloud native originated in customer-facing tech companies and emphasizes building applications in, for, and maximizing the benefits of the cloud.
2. When developing new applications, organizations should focus on functional and non-functional requirements to determine the appropriate architecture, runtime environment, and degree of "cloudiness".
3. Cloud native development requires learning new topics like microservices, DevOps, serverless computing, and distributed systems.
Containers, microservices and serverless for realistsKarthik Gaekwad
The document discusses containers, microservices, and serverless applications for developers. It provides an overview of these topics, including how containers and microservices fit into the DevOps paradigm and allow for better collaboration between development and operations teams. It also discusses trends in container usage and orchestration as well as differences between platforms as a service (PaaS) and serverless applications.
This document discusses microservices architecture and how Docker has changed application development. It covers:
- The rise of microservices architecture which breaks applications into independently deployable small services.
- How Docker brings development and operations teams closer together through standardized deployment of services.
- How Docker provides consistency for continuous integration testing by allowing identical environments.
- How Docker enables collaboration through sharing of pre-built application containers.
Presentation created for Third and Final Year students of , The Department of Information Technology, Bharati Vidyapeeth (Deemed to be University) College of Engineering, Pune. Collage has invited myself for a training program on “Recent Trends in Information Technology”. I presented on topic of "Serverless Microservices". It is Level-100 Session.
I Love APIs 2015
Chris Munns, Amazon
@chrismunns
http://www.amazon.com/
As computing costs decreased and computing power grew over time, so increased the complexity of the problems computers were called to solve and complexity of software. Enterprise applications quickly went through the stage of monolithic applications to client-server to multiple tier and beyond – to the land of massively distributed architectures. We arrived at the point where enterprise software is well beyond the capability of a single person or even a reasonably practical group of people to understand and control. Are microsevices the answer? Join Chris Munns to learn about how microservices are scaled at Amazon.
Live Introduction to the Cloud Native Microservices Platform – open, manageab...Lucas Jellema
The microservices architecture promises flexibility, scalability and optimal use of compute resources. Through independent components with well-defined scope and responsibility, interface and ownership that are evolved and managed in an automated DevOps process, this architecture leverages current technologies and lessons learned. The Oracle Microservices Platform is an open source runtime for deploying, running and managing container based microservices. This platform offers a distributed container runtime based on Kubernetes and on top of that API management, a build in event bus, a service broker to link in external services, advanced inter microservice traffic control and load balancing and extensive monitoring. It supports the pure pay-per-use and scale-on-request serverless paradigm. The platform can run anywhere: your laptop our data center, a third party cloud or as an Oracle managed cloud service. This session introduces this Microservices Platform and demonstrates how it is used to roll out and manage a set of collaborative microservices, both locally and in the cloud.
Kubernetes has become the defacto standard platform for managing containerized microservices. However, with just Kubernetes this platform is not yet complete. We also need facilities for managing traffic between microservices - monitor, route, authorize - as well as handle events. We need to support the Serverless architecture style - with triggered functions instead of pre-allocated servers. And we need a governance strategy around new versions of functions and microservices.
Oracle will launch an open (source) microservices platform with all these capabilities preintegrated. This platform is based on Kubernetes and also leverages Kafka, Project Fn, OpenServiceBroker and Istio along with monitoring using Prometheus, Grafana and Kibana. The platform can be run locally or on any IaaS platform. Oracle hopes to make money from a managed cloud service for this platform.
In this session, I want to explore the need for a microservices platform and the essential components it should provide. I will then demonstrate this open microservices platform proposed by Oracle.
Microservices: Why and When? - Alon Fliess, CodeValue - Cloud Native Day Tel ...Cloud Native Day Tel Aviv
Do more with less, the pain of the modern architect. High cohesion & low coupling, high availability & scale, ease of DevOps. Our systems need to support all these quality attributes, while providing more functionality with less resources. We need to be agile, we need to embrace changes, we need to have a better way! Micro-Service-Architecture (MSA) promises to bring cure to the architect's pains, but does it really deliver? This lecture presents the essence of MSA, how does it answer main concerns of modern distributed systems, how to get started, how to migrate current solutions to MSA by adopting an evolution migration path. What to be careful about and the signs that we are on the right track. We will talk about SA evolution, the CAP theorem and eventually consistency, MSA principles, hosting. containers, versioning, orchestrators & decoupling business processes. By the end of this lecture the participant will have a better understanding of why, when and how to embrace MSA.
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.
Sviluppare velocemente applicazioni sicure con SUSE CaaS Platform e SUSE ManagerSUSE Italy
The document describes an event called Expert Days 2019 focused on developing secure applications quickly using SUSE CaaS Platform and SUSE Manager. It includes an agenda with topics on IT transformation for innovation, terminology around SUSE CaaS Platform and SUSE Manager, and a live demo of a jTracker microservices application running on containers. Partners BS Company and SUSE will provide real experiences using these open source tools to reduce development time while maintaining enterprise security standards.
This session introduces the key patterns in Cloud Native application development. It highlights the need of a unique architecture style, further, the fitment of DevOps, usage of Microservices and the runtime of Cloud Native application (* as a Service). The precautions of distributed computing gives insights of how to plan the application design and architecture.
Martin Fowler defines microservices as an architectural style where single applications are developed as independent services that communicate with each other via lightweight mechanisms often using HTTP. Microservices are built around business capabilities, independently deployable, and owned by small teams. When developing microservices, continuous integration, deployment and automated testing are required. An API is not the same as a microservice - APIs expose data and behavior via contracts while microservices implement business capabilities. Microservices should only be used for large, complex systems that are hard to manage as a monolith.
This document provides an overview of microservices architecture compared to monolithic architecture. It discusses key concepts like SOA, containers with Docker, principles of microservices including loose coupling and decentralization, and industry examples from Netflix, Twitter, and others. The presenter's goal is to explain why microservices are important and how organizations can transition applications from monolithic to microservices using tools like Docker and orchestration.
Business and IT agility through DevOps and microservice architecture powered ...Lucas Jellema
IT needs to run in production in order to generate business value. DevOps is among other things a way of thinking focusing on production software. A business application requires a tailor made platform to generate business value. The combination of application and its platform is a DevOps product. The DevOps team has full responsibility for that product through its entire lifecycle.
The microservices architecture promises flexibility, scalability, and optimal use of compute resources. Via independent components with well-defined scope and responsibility, interface, and ownership that are evolved and managed in an automated DevOps process, this architecture leverages current technologies and hard-learned insights from past decades.
This session defines the objectives of Business with IT, of microservices and DevOps and introduces Containers and the container platform Kubernetes as crucial ingredients for making DevOps happen.
[QCon London 2020] The Future of Cloud Native API Gateways - Richard LiAmbassador Labs
The introduction of microservices, Kubernetes, and cloud technology has provided many benefits for developers. However, the age-old problem of getting user traffic routed correctly to the API of your backend applications can still be an issue, and may be complicated with the adoption of cloud native approaches: applications are now composed of multiple (micro)services that are built and released by independent teams; the underlying infrastructure is dynamically changing; services support multiple protocols, from HTTP/JSON to WebSockets and gRPC, and more; and many API endpoints require custom configuration of cross-cutting concerns, such as authn/z, rate limiting, and retry policies.
A cloud native API gateway is on the critical path of all requests, and also on the critical path for the workflow of any developer that is releasing functionality. Join this session to learn about the underlying technology and the required changes in engineering workflows. Key takeaways will include:
A brief overview of the evolution of API gateways over the past ten years, and how the original problems being solved have shifted in relation to cloud native technologies and workflow
Two important challenges when using an API gateway within Kubernetes: scaling the developer workflow; and supporting multiple architecture styles and protocols
Strategies for exposing Kubernetes services and APIs at the edge of your system
Insight into the (potential) future of cloud native API gateways
https://qconlondon.com/london2020/presentation/future-cloud-native-api-gateways
Presentazione dello speech tenuto da Carmine Spagnuolo (Postdoctoral Research Fellow - Università degli Studi di Salerno/ ACT OR) dal titolo "Technology insights: Decision Science Platform", durante il Decision Science Forum 2019, il più importante evento italiano sulla Scienza delle Decisioni.
Similar to Meetup: Platform-as-a-Service / Cloud Foundry (20)
Optimizing Gradle Builds - Gradle DPE Tour Berlin 2024Sinan KOZAK
Sinan from the Delivery Hero mobile infrastructure engineering team shares a deep dive into performance acceleration with Gradle build cache optimizations. Sinan shares their journey into solving complex build-cache problems that affect Gradle builds. By understanding the challenges and solutions found in our journey, we aim to demonstrate the possibilities for faster builds. The case study reveals how overlapping outputs and cache misconfigurations led to significant increases in build times, especially as the project scaled up with numerous modules using Paparazzi tests. The journey from diagnosing to defeating cache issues offers invaluable lessons on maintaining cache integrity without sacrificing functionality.
Batteries -Introduction – Types of Batteries – discharging and charging of battery - characteristics of battery –battery rating- various tests on battery- – Primary battery: silver button cell- Secondary battery :Ni-Cd battery-modern battery: lithium ion battery-maintenance of batteries-choices of batteries for electric vehicle applications.
Fuel Cells: Introduction- importance and classification of fuel cells - description, principle, components, applications of fuel cells: H2-O2 fuel cell, alkaline fuel cell, molten carbonate fuel cell and direct methanol fuel cells.
Advanced control scheme of doubly fed induction generator for wind turbine us...IJECEIAES
This paper describes a speed control device for generating electrical energy on an electricity network based on the doubly fed induction generator (DFIG) used for wind power conversion systems. At first, a double-fed induction generator model was constructed. A control law is formulated to govern the flow of energy between the stator of a DFIG and the energy network using three types of controllers: proportional integral (PI), sliding mode controller (SMC) and second order sliding mode controller (SOSMC). Their different results in terms of power reference tracking, reaction to unexpected speed fluctuations, sensitivity to perturbations, and resilience against machine parameter alterations are compared. MATLAB/Simulink was used to conduct the simulations for the preceding study. Multiple simulations have shown very satisfying results, and the investigations demonstrate the efficacy and power-enhancing capabilities of the suggested control system.
artificial intelligence and data science contents.pptxGauravCar
What is artificial intelligence? Artificial intelligence is the ability of a computer or computer-controlled robot to perform tasks that are commonly associated with the intellectual processes characteristic of humans, such as the ability to reason.
› ...
Artificial intelligence (AI) | Definitio
Electric vehicle and photovoltaic advanced roles in enhancing the financial p...IJECEIAES
Climate change's impact on the planet forced the United Nations and governments to promote green energies and electric transportation. The deployments of photovoltaic (PV) and electric vehicle (EV) systems gained stronger momentum due to their numerous advantages over fossil fuel types. The advantages go beyond sustainability to reach financial support and stability. The work in this paper introduces the hybrid system between PV and EV to support industrial and commercial plants. This paper covers the theoretical framework of the proposed hybrid system including the required equation to complete the cost analysis when PV and EV are present. In addition, the proposed design diagram which sets the priorities and requirements of the system is presented. The proposed approach allows setup to advance their power stability, especially during power outages. The presented information supports researchers and plant owners to complete the necessary analysis while promoting the deployment of clean energy. The result of a case study that represents a dairy milk farmer supports the theoretical works and highlights its advanced benefits to existing plants. The short return on investment of the proposed approach supports the paper's novelty approach for the sustainable electrical system. In addition, the proposed system allows for an isolated power setup without the need for a transmission line which enhances the safety of the electrical network
Rainfall intensity duration frequency curve statistical analysis and modeling...bijceesjournal
Using data from 41 years in Patna’ India’ the study’s goal is to analyze the trends of how often it rains on a weekly, seasonal, and annual basis (1981−2020). First, utilizing the intensity-duration-frequency (IDF) curve and the relationship by statistically analyzing rainfall’ the historical rainfall data set for Patna’ India’ during a 41 year period (1981−2020), was evaluated for its quality. Changes in the hydrologic cycle as a result of increased greenhouse gas emissions are expected to induce variations in the intensity, length, and frequency of precipitation events. One strategy to lessen vulnerability is to quantify probable changes and adapt to them. Techniques such as log-normal, normal, and Gumbel are used (EV-I). Distributions were created with durations of 1, 2, 3, 6, and 24 h and return times of 2, 5, 10, 25, and 100 years. There were also mathematical correlations discovered between rainfall and recurrence interval.
Findings: Based on findings, the Gumbel approach produced the highest intensity values, whereas the other approaches produced values that were close to each other. The data indicates that 461.9 mm of rain fell during the monsoon season’s 301st week. However, it was found that the 29th week had the greatest average rainfall, 92.6 mm. With 952.6 mm on average, the monsoon season saw the highest rainfall. Calculations revealed that the yearly rainfall averaged 1171.1 mm. Using Weibull’s method, the study was subsequently expanded to examine rainfall distribution at different recurrence intervals of 2, 5, 10, and 25 years. Rainfall and recurrence interval mathematical correlations were also developed. Further regression analysis revealed that short wave irrigation, wind direction, wind speed, pressure, relative humidity, and temperature all had a substantial influence on rainfall.
Originality and value: The results of the rainfall IDF curves can provide useful information to policymakers in making appropriate decisions in managing and minimizing floods in the study area.
3. 3
AGENDA
What are 'Platform-as-a-Service' and 'Cloud Foundry'
how can microservice architectures benefit from them,
how they play into DevOps,
and how Booxware uses them to address challenges
9. 9
AS-A-SERVICE
• Providers leverage existing customer base
• Less pressure on growing user base
• Continuous revenue stream
• Opposed to spikes with new release
• Shift in goals
• New killer features that customers like
• Increase customer satisfaction
• New features
• Availability, Stability
• Performance, Support
SUBSCRIPTION LICENSING MODEL
• Flexible pricing for consumers
• Less risk due to high investments
• Upgrade on-demand
• Try it out and adjust
• Outsourcing lets consumers focus on
their core business
12. 12
MICROSERVICES
"[…]The benefit of decomposing an application into
different smaller services is that it improves modularity
and makes the application easier to understand, develop
and test. It also parallelizes development by enabling
small autonomous teams to develop, deploy and scale
their respective services independently. […]"
OVERVIEW BY WIKIPEDIA
17. 17
CONWAY'S LAW
"organizations which design systems ... are
constrained to produce designs which are
copies of the communication structures of
these organizations"
~ M. Conway
18. 18
MICROSERVICES
• Small / domain specific
• Strong modularization
• Loosely coupled
• Less things to consider
• Less coordination
• Testing in isolation
EASIER TO UNDERSTAND, DEVELOP AND TEST
💾👑 💾🐧
💾🍀 💾🎃
21. 21
MICROSERVICES
"It also parallelizes development by
enabling small autonomous teams to
develop, deploy and scale their
respective services independently."
25. 25
MICROSERVICES
"It also parallelizes development by
enabling small autonomous
teams to develop, deploy and scale
their respective services independently."
27. 27
DEVOPS
"I went to the Deliverey of Things conference and it
was interesting to see that while everyone agrees
DevOps is a thing and should be done, everyone
struggles at actually implementing it."
~ Philipp Deutscher,
Director IT Operations,
Booxware
33. 33
DEVOPS
It is not about handoffs between
teams, but about communication
and collaboration within teams.
IMHO: HANDOFFS
34. 34
DEVOPS
IMHO: HANDOFFS
Dev Ops
Handoffs do not scale.
On the local level, teams do not share the same goals and priorities.
"We are all in
the same boat"
"Improve
collaboration"
"Improve
communication"
35. 35
DEVOPS
• Test-driven development suggests Developers write tests themselves
• Exposure to untestable code
• Application of clean code principles and dependency injection
• Overall better code quality as a "side effect"
• Operators struggle with hard to operate code
• Assumptions made, hardcoded values, not scalable
• Bad or missing logs and monitoring
• How would developers react to the pain of hard to operate code?
PAIN AS MOTIVATOR
36. 36
DEVOPS
"Developers operating their own code
make their own code easy to operate"
"Engineering teams need to operate their
code themselves for DevOps to scale"
THESIS
40. 40
DEVOPS
• Teams need to know all layers to bring value to the customer
• Software
• Runtime
• Operating system
• Virtual machines
• Servers, Network, Storage
• Teams need to be isolated from each other, but share resources
• Team A ought to not impact team B
• Resources ought to be efficiently pooled
ASSUMING FULL END-TO-END RESPONSIBILITY
50. 50
PLATFORM-AS-A-SERVICE
•National Institute of Standards & Technology (NIST)
• Branch of U.S. Department of Commerce
•"The NIST Definition of Cloud Computing"
• NIST Special Publication 800-145
51. 51
PLATFORM-AS-A-SERVICE
• Essential Characteristics
• On-demand self-service
• Broad network access
• Resource pooling
• Rapid elasticity
• Measured service
• Service Models
• Software as a Service (SaaS)
• Platform as a Service (PaaS)
• Infrastructure as a Service (IaaS)
NIST DEFINITION OF CLOUD COMPUTING
• Deployment Models
• Private cloud
• Community cloud
• Public cloud
• Hybrid cloud
52. 52
PLATFORM-AS-A-SERVICE
"The capability provided to the consumer is to deploy onto the cloud
infrastructure consumer-created or acquired applications created using
programming languages, libraries, services, and tools supported by the provider
(This capability does not necessarily preclude the use of compatible
programming languages, libraries, services, and tools from other sources). The
consumer does not manage or control the underlying cloud infrastructure
including network, servers, operating systems, or storage, but has control over
the deployed applications and possibly configuration settings for the
application-hosting environment."
NIST DEFINITION OF CLOUD COMPUTING
53. 53
PLATFORM-AS-A-SERVICE
A self-service system which engineers can use to
• deploy a microservice and specify a configuration,
• start, stop, restart apps,
• scale instances,
• forward logs to logging system
without needing to care how or when.
WHAT
61. 61
CLOUD FOUNDRY
• Deploy an application
• Configure an application
• Start, stop, restart application
• Scale an application
• Stream application logs
• Connect to application container via ssh
OVERVIEW
62. 62
CLOUD FOUNDRY
• Isolation of users
• Authentication and Authorization based on RBAC
• Integrates with LDAP and SAML
• Users can only manage apps they have access to
• Quotas control maximum resource consumption
• Isolation of applications
• Every application runs within a container
• Isolation segments separate compute resources
OVERVIEW
64. 64
CLOUD FOUNDRY
• Bulletin Board System
• Maintains a real-time representation
of the state of the Diego cluster
• Checks against desired state
• Brain
• Coordinates work placement on
cluster through auction algorithm
• Cell
• Runs Tasks and Long Running
Processes (LRP)
DIEGO
65. 65
CLOUD FOUNDRY
• Router automatically distributes load between instances
• No direct connection to app instance
• Diego runs containers and keeps them running
• Custom healthchecks (process, port, http)
• Buildpacks turn code into containers
• Java, Golang, Ruby, Python, NGINX, .net, php, node.js
• Write your own or use community buildpacks
• Run docker images
72. 72
CLOUD FOUNDRY
• Replace individual instances of an existing app to monitor the behavior
• Application with three instances
• Create a new independent app with 1 instance
• Add target route to new app
• Scale down 1 instance on old app
• Scale up 1 instance on new app
• Scale down 1 instance on old app
• Scale up 1 instance on new app
• Repeat until new app has take fully over
• Cleanup
CANARY/ROLLING DEPLOYMENT
81. 81
CLOUD FOUNDRY
• I. Codebase
One codebase tracked in revision control, many deploys
• II. Dependencies
Explicitly declare and isolate dependencies
• III. Config
Store config in the environment
• IV. Backing services
Treat backing services as attached resources
• V. Build, release, run
Strictly separate build and run stages
• VI. Processes
Execute the app as one or more stateless processes
12-FACTORS
82. 82
CLOUD FOUNDRY
• VII. Port binding
Export services via port binding
• VIII. Concurrency
Scale out via the process mode
• lIX. Disposability
Maximize robustness with fast startup and graceful shutdown
• X. Dev/prod parity
Keep development, staging, and production as similar as possible
• XI. Logs
Treat logs as event streams
• XII. Admin processes
Run admin/management tasks as one-off processes
12-FACTORS
84. 84
CLOUD FOUNDRY
• Integration of services via Service Broker API
• Databases, message-queues, caches, etc
• Users can create service instances via the platform
• Bind service instances to application
• CF injects config into app's environment
• Client lib can read them
89. 89
BOSH
"Release engineering is the difference between
manufacturing software in small teams or startups and
manufacturing software in an industrial way that is
repeatable, gives predictable results, and scales well."
~ Boris Debic
Release Engineer
Google
RELEASE ENGINEERING
90. 90
BOSH
• Identifiability
• Being able to identify all of the source, tools, environment, and other components that make up a
particular release.
• Reproducibility
• The ability to integrate source, third party components, data, and deployment externals of a software
system in order to guarantee operational stability.
• Consistency
• The mission to provide a stable framework for development, deployment, audit, and accountability for
software components.
• Agility
• The ongoing research into what are the repercussions of modern software engineering practices on the
productivity in the software cycle, i.e. continuous integration.
RELEASE ENGINEERING
91. 91
BOSH
• Stemcell
• A stemcell is a versioned Operating System image wrapped with IaaS specific packaging.
• Release
• A release is a versioned collection of configuration properties, configuration templates,
start up scripts, source code, binary artifacts, and anything else required to build and deploy
software in a reproducible way.
• Deployment
• A deployment is a collection of VMs, built from a stemcell, that has been populated with
specific releases and disks that keep persistent data. These resources are created based on
a manifest file in the IaaS and managed by the BOSH Director, a centralized management
server.
TERMINOLOGY
94. 94
SUMMARY
As-a-Service
allows focusing on core business
Microservices
increase operational complexity
DevOps
requires self-service systems
Platform-as-
a-Service
Cloud Foundry
BOSH
95. 95
SUMMARY
A self-service system which engineers can use to
• deploy a microservice and specify a configuration,
• start, stop, restart apps,
• scale instances,
• forward logs to logging system
without needing to care how or when.
97. 97
SUMMARY
We believe that engineering teams ought to
• bring features into production at their pace,
• be responsible for their product end-to-end, and
• be in control of their workflow.
BOOXWARE