The document discusses the architecture of Cloud Foundry, summarizing the roles and responsibilities of its main components:
- The Router handles external traffic and maintains routing tables to direct traffic to application instances.
- The Cloud Controller maintains systems control, handles user accounts and provisioning, and provides a REST API.
- Droplet Execution Agents (DEAs) are containers that build, start, and stop applications as instructed by managing the application lifecycle.
- Buildpacks compile source code, deploy applications, and configure runtime environments.
- Service Brokers provide interfaces to connect external services and manage service instances and bindings.
- Health Managers monitor application uptime by checking for mismatches between expected and
The document discusses best practices for building and deploying Scala applications based on the 12 Factor App methodology. It covers topics like managing dependencies, separating configuration from code, building in a simple and automated way, scaling apps through stateless processes, achieving parity between development and production environments, and running admin tasks isolated from the main app. The presentation provides examples using tools like sbt, Dropwizard, and Heroku to demonstrate how to structure Scala apps according to the 12 factors.
The document discusses the 12 factor app methodology for building software-as-a-service applications. It covers the 12 factors which are codebase, dependencies, configuration, backing services, build/release/run, processes, port binding, concurrency, disposability, development/production parity, logs, and admin processes. The presentation provides examples and explanations of how to design apps adhering to these 12 factors for scalability, maintainability and portability.
The document discusses best practices for modern Java application deployment based on the 12 Factor App methodology. It covers topics like packaging applications as JAR files instead of WAR files, managing dependencies, separating configuration from code, building in an automated and isolated way, making processes stateless and portable, enabling concurrency, and achieving parity between development and production environments. The 12 factors of the methodology are also listed and described.
12 Factor App: Best Practices for JVM DeploymentJoe Kutner
Twelve Factor apps are built for agility and rapid deployment. They enable continuous delivery and reduce the time and cost for new developers to join a project. At the same time, they are architected to exploit the principles of modern cloud platforms while permitting maximum portability between them. Finally, they can scale up without significant changes to tooling, architecture or development practices. In this talk, you’ll learn the principles and best practices espoused by the Twelve Factor app. We’ll discuss how to structure your code, manage dependencies, store configuration, run admin tasks, capture log files, and more. You’ll learn how modern Java deployments can benefit
This document discusses 12 best practices for designing production-ready Docker containers based on the 12 Factor App methodology. It covers factors like having one codebase per container, declaring and isolating dependencies explicitly, storing config variables in environment variables rather than files, separating build, release and runtime stages, treating logs as event streams, and running admin processes as one-off containers. Examples are provided for implementing each factor using Docker.
Continuous Deployment into the Unknown with Artifactory, Bintray, Docker and ...Gilad Garon
VMware’s Common SaaS Platform (CSP) is a brand new offering designed to enhance the productivity of developers and cloud providers by equipping them with a set of common and configurable capabilities (such as Identity, Telemetry, Account Management, Billing etc.), thus enabling them to focus on their core businesses.
But enough with the product pitch.
CSP is distributed to numerous cloud providers around the globe, used by developers and IT alike to empower their services and better answer the business need of their customers.
Please join us and witness how we take continuous delivery to the next step where sometimes the target environment is not on our control and still seamlessly manage and deliver our unique collection of capabilities, packaged as platform for ease of use, using the best and shiniest tools the frogs can provide.
JavaEdge 2008: Your next version control systemGilad Garon
The next generation of VCS has a clear target ahead of them: making branching and merging easier. Until recently, Subversion was dominating the world of Version Control Systems, but now, Distributed Version Control Systems are growing in popularity and everywhere you go you hear about Git or Mercurial, and how they make branching and merging a breeze. But the Subversion team isn't going down quietly, they have a new weapon: the 1.5 version. Learn about the next generation of Version Control Systems is planning to solve your problems.
Slides from Workshop 'Cloud Foundry: Hands-on Deployment Workshop'
http://www.meetup.com/CloudFoundry/events/150601282/
In this workshop you will learn Cloud Foundry fundamental concepts, setup, deployment and operations. We’ll cover a couple of alternatives to deploy CF in a local environment for learning and testing purposes as well as deploying Cloud Foundry atop IaaS production level environment, being able to manage hundreds of components and thousands of applications.
If you did not have a chance to work with Cloud Foundry, it may be useful to test its features locally at first. Deploying this environment on a local machine allows you to get hands-on experience in the solution and, in case you are a contributor, to test some features before you commit them to a production environment.
The document discusses best practices for building and deploying Scala applications based on the 12 Factor App methodology. It covers topics like managing dependencies, separating configuration from code, building in a simple and automated way, scaling apps through stateless processes, achieving parity between development and production environments, and running admin tasks isolated from the main app. The presentation provides examples using tools like sbt, Dropwizard, and Heroku to demonstrate how to structure Scala apps according to the 12 factors.
The document discusses the 12 factor app methodology for building software-as-a-service applications. It covers the 12 factors which are codebase, dependencies, configuration, backing services, build/release/run, processes, port binding, concurrency, disposability, development/production parity, logs, and admin processes. The presentation provides examples and explanations of how to design apps adhering to these 12 factors for scalability, maintainability and portability.
The document discusses best practices for modern Java application deployment based on the 12 Factor App methodology. It covers topics like packaging applications as JAR files instead of WAR files, managing dependencies, separating configuration from code, building in an automated and isolated way, making processes stateless and portable, enabling concurrency, and achieving parity between development and production environments. The 12 factors of the methodology are also listed and described.
12 Factor App: Best Practices for JVM DeploymentJoe Kutner
Twelve Factor apps are built for agility and rapid deployment. They enable continuous delivery and reduce the time and cost for new developers to join a project. At the same time, they are architected to exploit the principles of modern cloud platforms while permitting maximum portability between them. Finally, they can scale up without significant changes to tooling, architecture or development practices. In this talk, you’ll learn the principles and best practices espoused by the Twelve Factor app. We’ll discuss how to structure your code, manage dependencies, store configuration, run admin tasks, capture log files, and more. You’ll learn how modern Java deployments can benefit
This document discusses 12 best practices for designing production-ready Docker containers based on the 12 Factor App methodology. It covers factors like having one codebase per container, declaring and isolating dependencies explicitly, storing config variables in environment variables rather than files, separating build, release and runtime stages, treating logs as event streams, and running admin processes as one-off containers. Examples are provided for implementing each factor using Docker.
Continuous Deployment into the Unknown with Artifactory, Bintray, Docker and ...Gilad Garon
VMware’s Common SaaS Platform (CSP) is a brand new offering designed to enhance the productivity of developers and cloud providers by equipping them with a set of common and configurable capabilities (such as Identity, Telemetry, Account Management, Billing etc.), thus enabling them to focus on their core businesses.
But enough with the product pitch.
CSP is distributed to numerous cloud providers around the globe, used by developers and IT alike to empower their services and better answer the business need of their customers.
Please join us and witness how we take continuous delivery to the next step where sometimes the target environment is not on our control and still seamlessly manage and deliver our unique collection of capabilities, packaged as platform for ease of use, using the best and shiniest tools the frogs can provide.
JavaEdge 2008: Your next version control systemGilad Garon
The next generation of VCS has a clear target ahead of them: making branching and merging easier. Until recently, Subversion was dominating the world of Version Control Systems, but now, Distributed Version Control Systems are growing in popularity and everywhere you go you hear about Git or Mercurial, and how they make branching and merging a breeze. But the Subversion team isn't going down quietly, they have a new weapon: the 1.5 version. Learn about the next generation of Version Control Systems is planning to solve your problems.
Slides from Workshop 'Cloud Foundry: Hands-on Deployment Workshop'
http://www.meetup.com/CloudFoundry/events/150601282/
In this workshop you will learn Cloud Foundry fundamental concepts, setup, deployment and operations. We’ll cover a couple of alternatives to deploy CF in a local environment for learning and testing purposes as well as deploying Cloud Foundry atop IaaS production level environment, being able to manage hundreds of components and thousands of applications.
If you did not have a chance to work with Cloud Foundry, it may be useful to test its features locally at first. Deploying this environment on a local machine allows you to get hands-on experience in the solution and, in case you are a contributor, to test some features before you commit them to a production environment.
My @TriangleDevops talk from 2013-10-17. I covered the work that led us to @NetflixOSS (Acme Air), the work we did on the cloud prize (NetflixOSS on IBM SoftLayer/RightScale) and the @NetflixOSS platform (Karyon, Archaius, Eureka, Ribbon, Asgard, Hystrix, Turbine, Zuul, Servo, Edda, Ice, Denominator, Aminator, Janitor/Conformity/Chaos Monkeys of the Simian Army).
GWT brings a lot to the table on the client side: the comprehensive browser compatibility and the ease of writing in java are just a few examples to name. But, when looking at the server side, GWT can be a bit lacking with the technologies it uses. Learn how to build powerful end to end Enterprise applications with GWT as your frontend and how to back it up with your favorite arsenal of tools, including, Spring, Guice and Hibernate
This document discusses Fn Project, an open source container-native serverless platform. It allows users to write small bits of code called functions that can be easily deployed, invoked and scaled independently in the cloud or on-premises. Fn Project supports many programming languages including Java, Go, Python and JavaScript. It uses Docker containers to wrap and run functions and provides tools for monitoring, management and rapid development of serverless applications.
Microcontainers and Tools for Hardcore Container DebuggingOracle Developers
The document discusses microcontainers and tools for debugging containers. It begins with introductions of the presenters and an agenda. It then provides information on what containers are, how they work, and common issues. Microcontainers are introduced as a way to reduce image size and security risks. The document demonstrates how to build microcontainers and debug containers using open source tools from Oracle. It concludes with links to more information and a question/answer section.
Spring Dynamic Modules for OSGi by Example - Martin Lippert, Consultantmfrancis
This document outlines the agenda for a presentation on Spring Dynamic Modules. The presentation introduces the Spring framework and how it simplifies enterprise application development. It then discusses Spring Dynamic Modules (Spring DM), which allows Spring applications to be implemented on OSGi frameworks. Spring DM exports Spring beans as OSGi services and imports OSGi services as beans, without dependencies on OSGi APIs. Examples are provided of Spring DM's support for web applications. The presentation concludes with an outlook on future Spring DM developments and links for more information.
5 steps to take setting up a streamlined container pipelineMichel Schildmeijer
The document outlines 5 steps to set up a container pipeline:
1. Use versioning and container registries like GitHub, Docker, and private registries to manage code versions and container images.
2. Use an orchestration engine like Kubernetes to manage and orchestrate container processes. Common options are AWS EKS, GCP GKE, and Oracle OKE.
3. Provision the Kubernetes cluster using scripts or Terraform on cloud infrastructure like OCI.
4. Implement container pipelines using tools like Oracle Container Pipelines to automate building, testing, and deploying containers.
5. Use Helm to package and deploy Kubernetes applications and integrate it into the CI/CD pipeline
This document provides an overview of Apache ActiveMQ, an open-source messaging server. It discusses ActiveMQ's features such as high performance, high availability, multiple protocols and transports. It also covers tools for benchmarking and performance tuning ActiveMQ brokers, including the ActiveMQ Performance Module, jms-benchmark, JMSTester, JMeter and OS monitoring tools. The document is intended to help understand how to approach performance tuning of ActiveMQ brokers.
Agenda
1. The changing landscape of IT Infrastructure
2. Containers - An introduction
3. Container management systems
4. Kubernetes
5. Containers and DevOps
6. Future of Infrastructure Mgmt
About the talk
In this talk, you will get a review of the components & the benefits of Container technologies - Docker & Kubernetes. The talk focuses on making the solution platform-independent. It gives an insight into Docker and Kubernetes for consistent and reliable Deployment. We talk about how the containers fit and improve your DevOps ecosystem and how to get started with containerization. Learn new deployment approach to effectively use your infrastructure resources to minimize the overall cost.
Cloud Foundry Open Tour India 2012 , Keynoterajdeep
VMware is a leading cloud infrastructure software provider with over $3.77 billion in revenues and over 300,000 customers including all of the Fortune 100 companies. The company's mission is to simplify and automate IT for customers by optimizing efficiency, enabling business agility, and empowering a more productive workforce. VMware is focusing on providing a more flexible, scalable infrastructure for all applications across existing datacenters and public clouds.
Real-world #microservices with Apache Camel, Fabric8, and OpenShiftChristian Posta
What are and aren't microservices?
Microservices is a validation of the open-source approach to integration and service implementation and a rebuff of the committee-driven SOA approach. In this
The document discusses IBM's use of Node.js microservices. It describes how IBM initially built monolithic applications but moved to microservices to allow for independent deployment of services and improved scalability. Some key aspects of IBM's microservices architecture using Node.js include having many independent services, communicating via message queues like RabbitMQ, and clustering services locally for horizontal scaling. While microservices provided benefits, the document also notes challenges around legal compliance, operations overhead, and integrating distributed services.
Developing Microservices with Apache Camel, by Claus IbsenJudy Breedlove
Claus Ibsen's presentation during Red Hat's "Microservices Journey with Apache Camel" events that took place in Atlanta on Oct 4th and Minneapolis on Oct 6th.
DCEU 18: 5 Patterns for Success in Application TransformationDocker, Inc.
Elton Stoneman - Developer Advocate, Docker
Legacy applications weren't designed to run in a modern distributed platform like Docker. They have their own ideas about logging, configuration and health which don't translate to the world of containers and make transformation projects hard.
This session shows you how to bring your old applications into the modern world, and integrate them with Docker - without changing code. We'll cover patterns for all the core application concerns:
* logging
* configuration
* monitoring
* health
* dependency management
The sample applications will be in .NET and Java, and will show you how to turn your existing applications into good Docker citizens.
Refactor your Java EE application using Microservices and Containers - Arun G...Codemotion
Codemotion Rome 2015 - This talk will provide a quick introduction to Docker images (build time), containers (run time), and registry (distribution). It shows how to take an existing Java EE application and package it as a monolithic application as a single Docker image. The application will then be refactored in to multiple microservices and assembled together using orchestration. Unit and integration testing of such applications will be discussed and shown as well. Design patterns and anti-patterns that show how to create cluster of such applications will be demonstrated and discussed.
Flexible Permissions Management with ACL TemplatesJeff Potts
This is was presented as an ignite-style lightning talk at DevCon 2018 in Lisbon. It discusses an open source add-on called ACL Templates which can be used to separate ACL settings from code.
This document discusses Docker and provides an introduction and overview for getting started with Docker. It begins with discussing the challenges of managing complex software stacks across different environments and how Docker addresses this through containerization and separation of concerns. It then covers downloading and installing Docker, basic Docker commands like run, images, ps, and explains a "Hello World" example. Finally, it demonstrates building a simple Whalesay image and running MySQL and WordPress in linked Docker containers using both the Docker CLI and Docker Compose.
Extreme performance with Oracle SOA Suite 12.2, Coherence and Exalogic can be achieved by configuring the platform to take advantage of the Exalogic infrastructure and optimizing SOA Suite and Coherence settings. Key aspects include using Coherence caching to minimize database transactions, configuring optimal WebLogic and JDBC settings for InfiniBand networking, and tuning SOA Suite dehydration and caching properties. This provides significant performance gains over a traditional architecture.
This document provides an overview of a presentation given at CamelOne 2013 in Boston on June 10-11, 2013 about the internals of Apache ActiveMQ. The presentation covered the major subcomponents of ActiveMQ including transports, the broker core, persistence adapters, and networking brokers. It provided details on architecture, configuration, and implementation of these different aspects of ActiveMQ.
Este documento presenta el proyecto de grado de Luis Alberto Robledo Benjumea sobre el manejo de los residuos generados en la construcción de obras civiles en Bello, Antioquia. El proyecto busca formular un modelo de gestión para los residuos desde la planificación de los proyectos basado en las etapas de generación, clasificación, almacenamiento, tratamiento y disposición final. El documento incluye la presentación personal de Luis, la justificación, objetivos, marco teórico y legal del proyecto, así como las fu
My @TriangleDevops talk from 2013-10-17. I covered the work that led us to @NetflixOSS (Acme Air), the work we did on the cloud prize (NetflixOSS on IBM SoftLayer/RightScale) and the @NetflixOSS platform (Karyon, Archaius, Eureka, Ribbon, Asgard, Hystrix, Turbine, Zuul, Servo, Edda, Ice, Denominator, Aminator, Janitor/Conformity/Chaos Monkeys of the Simian Army).
GWT brings a lot to the table on the client side: the comprehensive browser compatibility and the ease of writing in java are just a few examples to name. But, when looking at the server side, GWT can be a bit lacking with the technologies it uses. Learn how to build powerful end to end Enterprise applications with GWT as your frontend and how to back it up with your favorite arsenal of tools, including, Spring, Guice and Hibernate
This document discusses Fn Project, an open source container-native serverless platform. It allows users to write small bits of code called functions that can be easily deployed, invoked and scaled independently in the cloud or on-premises. Fn Project supports many programming languages including Java, Go, Python and JavaScript. It uses Docker containers to wrap and run functions and provides tools for monitoring, management and rapid development of serverless applications.
Microcontainers and Tools for Hardcore Container DebuggingOracle Developers
The document discusses microcontainers and tools for debugging containers. It begins with introductions of the presenters and an agenda. It then provides information on what containers are, how they work, and common issues. Microcontainers are introduced as a way to reduce image size and security risks. The document demonstrates how to build microcontainers and debug containers using open source tools from Oracle. It concludes with links to more information and a question/answer section.
Spring Dynamic Modules for OSGi by Example - Martin Lippert, Consultantmfrancis
This document outlines the agenda for a presentation on Spring Dynamic Modules. The presentation introduces the Spring framework and how it simplifies enterprise application development. It then discusses Spring Dynamic Modules (Spring DM), which allows Spring applications to be implemented on OSGi frameworks. Spring DM exports Spring beans as OSGi services and imports OSGi services as beans, without dependencies on OSGi APIs. Examples are provided of Spring DM's support for web applications. The presentation concludes with an outlook on future Spring DM developments and links for more information.
5 steps to take setting up a streamlined container pipelineMichel Schildmeijer
The document outlines 5 steps to set up a container pipeline:
1. Use versioning and container registries like GitHub, Docker, and private registries to manage code versions and container images.
2. Use an orchestration engine like Kubernetes to manage and orchestrate container processes. Common options are AWS EKS, GCP GKE, and Oracle OKE.
3. Provision the Kubernetes cluster using scripts or Terraform on cloud infrastructure like OCI.
4. Implement container pipelines using tools like Oracle Container Pipelines to automate building, testing, and deploying containers.
5. Use Helm to package and deploy Kubernetes applications and integrate it into the CI/CD pipeline
This document provides an overview of Apache ActiveMQ, an open-source messaging server. It discusses ActiveMQ's features such as high performance, high availability, multiple protocols and transports. It also covers tools for benchmarking and performance tuning ActiveMQ brokers, including the ActiveMQ Performance Module, jms-benchmark, JMSTester, JMeter and OS monitoring tools. The document is intended to help understand how to approach performance tuning of ActiveMQ brokers.
Agenda
1. The changing landscape of IT Infrastructure
2. Containers - An introduction
3. Container management systems
4. Kubernetes
5. Containers and DevOps
6. Future of Infrastructure Mgmt
About the talk
In this talk, you will get a review of the components & the benefits of Container technologies - Docker & Kubernetes. The talk focuses on making the solution platform-independent. It gives an insight into Docker and Kubernetes for consistent and reliable Deployment. We talk about how the containers fit and improve your DevOps ecosystem and how to get started with containerization. Learn new deployment approach to effectively use your infrastructure resources to minimize the overall cost.
Cloud Foundry Open Tour India 2012 , Keynoterajdeep
VMware is a leading cloud infrastructure software provider with over $3.77 billion in revenues and over 300,000 customers including all of the Fortune 100 companies. The company's mission is to simplify and automate IT for customers by optimizing efficiency, enabling business agility, and empowering a more productive workforce. VMware is focusing on providing a more flexible, scalable infrastructure for all applications across existing datacenters and public clouds.
Real-world #microservices with Apache Camel, Fabric8, and OpenShiftChristian Posta
What are and aren't microservices?
Microservices is a validation of the open-source approach to integration and service implementation and a rebuff of the committee-driven SOA approach. In this
The document discusses IBM's use of Node.js microservices. It describes how IBM initially built monolithic applications but moved to microservices to allow for independent deployment of services and improved scalability. Some key aspects of IBM's microservices architecture using Node.js include having many independent services, communicating via message queues like RabbitMQ, and clustering services locally for horizontal scaling. While microservices provided benefits, the document also notes challenges around legal compliance, operations overhead, and integrating distributed services.
Developing Microservices with Apache Camel, by Claus IbsenJudy Breedlove
Claus Ibsen's presentation during Red Hat's "Microservices Journey with Apache Camel" events that took place in Atlanta on Oct 4th and Minneapolis on Oct 6th.
DCEU 18: 5 Patterns for Success in Application TransformationDocker, Inc.
Elton Stoneman - Developer Advocate, Docker
Legacy applications weren't designed to run in a modern distributed platform like Docker. They have their own ideas about logging, configuration and health which don't translate to the world of containers and make transformation projects hard.
This session shows you how to bring your old applications into the modern world, and integrate them with Docker - without changing code. We'll cover patterns for all the core application concerns:
* logging
* configuration
* monitoring
* health
* dependency management
The sample applications will be in .NET and Java, and will show you how to turn your existing applications into good Docker citizens.
Refactor your Java EE application using Microservices and Containers - Arun G...Codemotion
Codemotion Rome 2015 - This talk will provide a quick introduction to Docker images (build time), containers (run time), and registry (distribution). It shows how to take an existing Java EE application and package it as a monolithic application as a single Docker image. The application will then be refactored in to multiple microservices and assembled together using orchestration. Unit and integration testing of such applications will be discussed and shown as well. Design patterns and anti-patterns that show how to create cluster of such applications will be demonstrated and discussed.
Flexible Permissions Management with ACL TemplatesJeff Potts
This is was presented as an ignite-style lightning talk at DevCon 2018 in Lisbon. It discusses an open source add-on called ACL Templates which can be used to separate ACL settings from code.
This document discusses Docker and provides an introduction and overview for getting started with Docker. It begins with discussing the challenges of managing complex software stacks across different environments and how Docker addresses this through containerization and separation of concerns. It then covers downloading and installing Docker, basic Docker commands like run, images, ps, and explains a "Hello World" example. Finally, it demonstrates building a simple Whalesay image and running MySQL and WordPress in linked Docker containers using both the Docker CLI and Docker Compose.
Extreme performance with Oracle SOA Suite 12.2, Coherence and Exalogic can be achieved by configuring the platform to take advantage of the Exalogic infrastructure and optimizing SOA Suite and Coherence settings. Key aspects include using Coherence caching to minimize database transactions, configuring optimal WebLogic and JDBC settings for InfiniBand networking, and tuning SOA Suite dehydration and caching properties. This provides significant performance gains over a traditional architecture.
This document provides an overview of a presentation given at CamelOne 2013 in Boston on June 10-11, 2013 about the internals of Apache ActiveMQ. The presentation covered the major subcomponents of ActiveMQ including transports, the broker core, persistence adapters, and networking brokers. It provided details on architecture, configuration, and implementation of these different aspects of ActiveMQ.
Este documento presenta el proyecto de grado de Luis Alberto Robledo Benjumea sobre el manejo de los residuos generados en la construcción de obras civiles en Bello, Antioquia. El proyecto busca formular un modelo de gestión para los residuos desde la planificación de los proyectos basado en las etapas de generación, clasificación, almacenamiento, tratamiento y disposición final. El documento incluye la presentación personal de Luis, la justificación, objetivos, marco teórico y legal del proyecto, así como las fu
Elementos importantes a tener en cuenta a la hora de dialogar con la Comunidad educativa para implementar una actuación de éxito, mejorar la convivencia y el aprendizaje.
This Georgian colonial home located in Mt. Lebanon, PA features 4 bedrooms and 2.5 bathrooms across three stories. The main level has a spacious living room with a fireplace, formal dining room, eat-in kitchen with stainless steel appliances, and a circular family room with exposed brick. The upper level contains the master bedroom with walk-in closet and private bath, two additional bedrooms, and a full bathroom. The partially finished basement provides storage and a laundry room. Exterior amenities include a front porch, back deck, 2-car detached garage, and fenced backyard. The home has undergone recent renovations including a new roof, deck, windows, and mechanical systems.
Este documento presenta un proyecto de investigación sobre el fortalecimiento integrado de la pesca artesanal en el departamento de La Guajira, Colombia. El proyecto busca mejorar los ingresos de los pescadores artesanales a través de la implementación de buenas prácticas pesqueras, comercio justo y mejoramiento de las condiciones socioeconómicas de las comunidades pesqueras. El proyecto analizará la situación actual de los pescadores, realizará un estudio de mercado y establecerá una metodología
La UGEL No15 de Huarochirí está convocando a tres profesionales en educación para el cargo de Acompañante Pedagógico en instituciones educativas primarias. Los postulantes deben tener experiencia docente en primaria, título pedagógico, y habilidades como análisis, planificación y comunicación. El contrato es por cinco meses con un sueldo de S/ 3,400 mensuales. El cronograma incluye la aprobación de la convocatoria en febrero y la publicación en el Servicio Nacional
La actividad explora la creación de música con el cuerpo mediante la atención a instrucciones visuales, la exploración de los sonidos y posibilidades del cuerpo propio, y la experimentación con sonidos fuertes y flojos.
Esta lista contiene palabras que contienen la letra "n" como prefijo o dentro de la palabra, incluyendo enano, pino, mano, mono, piano, lana, pimiento, atún y se repiten en el mismo orden.
Los delfines son mamíferos acuáticos con cuerpos aerodinámicos que miden hasta 4.5 metros y pesan 300 kg. Viven en manadas y se alimentan de crustáceos y calamares. Existen varios tipos de delfines, incluyendo el delfín austral, delfín común costero, delfín cruzado y delfín oscuro.
This presentation covers both the Cloud Foundry Elastic Runtime (known by many as just "Cloud Foundry") as well as the Operations Manager (known by many as BOSH). For each, the main components are covered with interactions between them.
A journey from Java EE to cloud-native microservices - Rabobank, JUG meetupVincent Oostindie
Slides from the presentation at the Utrecht Java User Group meetup at 15-10-2018, followed by Mark Heckler from Pivotal and Bruno Borges from Microsoft.
Cloud native microservices for systems and applications ieee rev2Prem Sankar Gopannan
This document discusses cloud native microservices and key components for implementing them. It provides an overview of microservices principles and design patterns, and describes the cloud native landscape including containers, Kubernetes, service meshes like Istio, and other open source tools. It also discusses architectures like ONAP and considerations for deploying virtual network functions using microservices.
An architect’s guide to leveraging your incumbencyMichael Elder
O'Reilly Software Architecture Conference 2018 (London)
Continuous delivery for 12-factor Microservices works because it’s by design. When you can architect a solution for continuous delivery, you control all the angles but what do you do when you don’t have that luxury? This session will highlight how modernizing existing IT infrastructure with containers enables you to manage change through continuous delivery and reduce ongoing operational costs.
Abstract
While the industry has promoted a dramatic trend to build new, improved styles of architecture; there remains a gap in how to address the ongoing and continuous improvement and operation of existing enterprise IT systems alongside these new 12-factor apps.
In this session, we will review why 12-factor apps are a natural fit for Kubernetes by design. We will demonstrate how Kubernetes addresses virtually all of the 12 factors for scalable web apps. Then we will take a step back and consider the important question: how well will stateful and transactional workloads that were not designed for 12-factor be able to run within Kubernetes?
Even with purist gaps from 12-factor for traditional enterprise workloads, there are real benefits to velocity and cost management to move stateful and transactional workloads to containers. With a container based orchestrator like Kubernetes, all workload types can take advantage of automated DevOps release pipelines, provide rich feedback loops with canary testing, leverage better automated failure recovery in production, and provide easier visibility into the operational health of services running within Kubernetes. Leveraging a standard platform for a blend of architectural types enables an enterprise to standardize operational practices for across the board. The end result might be the right path for your enterprise to drive your digital transformation.
Spring Cloud Services with Pivotal Cloud Foundry- Gokhan GoksuVMware Tanzu
- Pivotal Cloud Foundry (PCF) is a cloud application platform that supports Spring applications. It provides automated deployment of Spring and Spring Boot apps along with a services ecosystem.
- Spring Cloud Services (SCS) provides services for PCF like service registry, configuration management, and circuit breakers that integrate with Spring apps. It includes tools to manage credentials and integrate apps with services.
- The document discusses how PCF supports developers through services, buildpacks, and automation to deploy Spring apps and discusses integrating apps with services through SCS. It also provides an agenda for a demo of deploying Spring apps on PCF.
J-Spring 2018 - A journey from Java EE to Cloud Native microservicesVincent Oostindie
About a decade ago, when the world was still all about J2EE and WebSphere application servers, Rabobank introduced a new Online platform with a custom, intentionally self-built, portal framework. Since then our world has changed in many ways. Nobody does portlets anymore; instead we build rich front-end applications backed by services spitting out JSON. Like most of the rest of the world Rabobank moved from waterfall to Agile to DevOps. Microservices came along. Java is no longer the only preferred language on the server. Today, Rabobank is migrating to a new platform based on Pivotal Cloud Foundry, that intends to cope with all these changes. In this talk Vincent Oostindië will talk you through a decade of IT at Rabobank Online, of course focusing on the new platform and the underlying technologies used there, like Spring Boot and Spring Cloud Services.
Serverless integration with Knative and Apache Camel on KubernetesClaus Ibsen
This presentation will introduce Knative, an open source project that adds serverless capabilities on top of Kubernetes, and present Camel K, a lightweight platform that brings Apache Camel integrations in the serverless world. Camel K allows running Camel routes on top of any Kubernetes cluster, leveraging Knative serverless capabilities such as “scaling to zero”.
We will demo how Camel K can connect cloud services or enterprise applications using its 250+ components and how it can intelligently route events within the Knative environment via enterprise integration patterns (EIP).
Target Group: Developers, architects and other technical people - a basic understanding of Kubernetes is an advantage
Moderne Serverless-Computing-Plattformen sind in aller Munde und stellen ein Programmiermodell zur Verfügung, wo sich der Nutzer keine Gedanken mehr über die Administration der Server, Storage, Netzwerk, virtuelle Maschinen, Hochverfügbarkeit und Skalierbarkeit machen brauch, sondern sich auf das Schreiben von eigenen Code konzentriert. Der Code bildet die Geschäftsanforderungen modular in Form von kleinen Funktionspaketen (Functions) ab. Functions sind das Herzstück der Serverless-Computing-Plattform. Sie lesen von der (oft Standard-)Eingabe, tätigen ihre Berechnungen und erzeugen eine Ausgabe. Die zu speichernden Ergebnisse von Funktionen werden in einem permanenten Datastore abgelegt, wie z.B. der Autonomous Database gespeichert. Die Autonomous Database besitzt folgende drei Eigenschaften self-driving, self-repairing und self-securing, die für einen modernen Anwendungsentwicklungsansatz benötigt werden.
Devoxx 2018 - Pivotal and AxonIQ - Quickstart your event driven architectureBen Wilcock
Devoxx Belgium 2018 - Let Pivotal and AxonIQ take you on a journey into Axon Trader. Axon Trader is a new open-source reference architecture that demonstrates how to use Spring, Axon and Pivotal Cloud Foundry to deliver evolutionary microservice applications to prod in minutes.
The accompanying YouTube video can be found here: https://www.youtube.com/watch?v=15hzHUI4WNA
Eseguire Applicazioni Cloud-Native con Pivotal Cloud Foundry su Google Cloud ...VMware Tanzu
Eseguire Applicazioni Cloud-Native con Pivotal Cloud Foundry su Google Cloud Platform (Pivotal Cloud-Native Workshop: Milan)
Fabio Marinelli
7 February 2018
This document provides an overview of IBM's z/OS Connect Enterprise Edition (z/OS Connect EE) product and how it can be used to expose mainframe assets and applications as RESTful APIs. Some key points:
- z/OS Connect EE allows clients to expose existing mainframe applications and data as RESTful APIs to enable integration with modern systems of engagement.
- It provides tools for defining services that represent mainframe assets and tools for creating RESTful APIs that map to those services.
- The APIs can then be deployed to a z/OS Connect EE server to be consumed. The document outlines the high-level steps to create and deploy an API.
- It supports connecting to various
Kubernetes Ingress to Service Mesh (and beyond!)Christian Posta
Kubernetes users need to allow traffic to flow into and within the cluster. Treating the application traffic separately from the business logic allows presents new possibilities in how service to service traffic is served, controlled and observed — and provides a transition to intra cluster networking like Service Mesh. With microservices, there is a concept of both North / South traffic (incoming requests from end users to the cluster) and East / West (intra cluster) communication between the services. In this talk we will explain how Envoy Proxy works in Kubernetes as a proxy for both of these traffic directions and how it can be leveraged to do things like traffic shaping, security, and integrate the north/south to east/west behavior.
Christian Posta (@christianposta) is Global Field CTO at Solo.io, former Chief Architect at Red Hat, and well known in the community for being an author (Istio in Action, Manning, Istio Service Mesh, O'Reilly 2018, Microservices for Java Developers, O’Reilly 2016), frequent blogger, speaker, open-source enthusiast and committer on various open-source projects including Istio, Kubernetes, and many others. Christian has spent time at both enterprises as well as web-scale companies and now helps companies create and deploy large-scale, cloud-native resilient, distributed architectures. He enjoys mentoring, training and leading teams to be successful with distributed systems concepts, microservices, devops, and cloud-native application design.
This document discusses modernizing apps using Docker and the 12 Factor methodology. It begins by thanking sponsors and introducing new organizers. It then provides an overview of the evolution of application architectures from the late 90s to today. It notes the benefits of using Docker, such as faster deployments, version tracking, and security. It discusses moving from a monolith application to a microservices architecture using Docker and following the principles of the 12 Factor App methodology to address challenges of distributed systems, rapid deployments, and automation. The 12 factors are then each explained in detail and how Docker can help implement them for building modern, scalable apps.
IBM BP Session - Multiple CLoud Paks and Cloud Paks Foundational Services.pptxGeorg Ember
Diese Präsentation beinhaltet Erfahrungen, Empfehlungen und Planungs-Gedanken, die man beachten sollte, wenn man multiple IBM Cloud Paks auf der Container Platform OpenShift installieren / deployen möchte. Es beschreibt die Grundlagen zu "common services", auch "foundational services" genannt, die als Basis-Services die Lauffähigkeit dieser Cloud Paks auf OpenShift erläutert und wie man Cloud Paks auch logisch trennen kann auf OpenShift worker nodes über taints und node selectors.
This talk, a case study in application deployment models, was given at IBM InterConnect 2017 in Las Vegas, NV on March 21, 2017 by Lin Sun & Phil Estes of IBM Cloud.
In this talk, Lin & Phil provided a background of IBM Bluemix compute offerings across Cloud Foundry, Containers + Kubernetes, and FaaS/serverless via OpenWhisk and then used a demo application to describe the tradeoffs between using the various deployment models and technology. The application is open source and available at https://github.com/estesp/flightassist
ATO 2018 - What is Serverless Useful For?BerndtJung
This document discusses serverless computing and introduces Dispatch, an open source serverless platform from VMware. It describes how serverless uses functions to provide a serverless computing experience across multiple clouds. Dispatch provides a production-ready functions stack that supports cloud events and can integrate with various identity providers and services. The document demonstrates Dispatch's capabilities through an example using Dispatch and Slack for chat-based automation and management of virtual machines and events. It outlines Dispatch's roadmap, including both standalone and Knative-based versions, and invites the reader to get involved.
Similar to 12 Factor Apps and Cloud Foundry - Twin Cities Code Camp (20)
This document discusses DevOps in action and provides examples of tools and practices that can be used at different stages of the development pipeline to optimize resources, accelerate delivery, improve measurement of deployment rates and downtime, and increase frequency of releases. It outlines values and measures at the dev, stage, and production stages when using practices like continuous integration, automated testing, infrastructure as code, and monitoring.
This document outlines an agenda for an all day container conference including vendors, customers, lightning talks, suggestions, and talk tracks. One of the talk tracks is a Docker Swarm overview presentation by Dave Strebel from Microsoft about Docker, the Docker CLI, and Swarm.
This document discusses running Cloud Foundry on Microsoft Azure. It provides an overview of Azure regions and datacenter infrastructure. It then lists several Azure services that can be used with Cloud Foundry and links to documentation on deploying Cloud Foundry on Azure, including using the open source BOSH release or purchasing a preconfigured solution from the Azure Marketplace. Finally, it briefly describes the Meta Azure Service Broker for integrating Azure services with Cloud Foundry.
Twin Cities Code Camp - DevOps In ActionDavid Strebel
This document discusses DevOps in action and provides an overview of DevOps concepts and tools. It outlines a DevOps workflow involving monitoring and learning from production, developing and testing features, integrating and deploying code, and then measuring key metrics like release frequency, downtime, and resource optimization. Common DevOps tools are also listed including version control systems, configuration management, and monitoring solutions.
Introduction To Microsoft Windows ContainersDavid Strebel
Containers provide a way for developers to create applications quickly without disrupting IT's ability to manage servers and maintain control. Developers are able to focus on innovation without worrying about infrastructure differences between their machines and production servers. Containers allow applications to run consistently across environments. However, IT needs to integrate unfamiliar applications from developers while also protecting servers and ensuring compliance. Containers help address this by allowing consistent deployment of applications alongside management of infrastructure and resources.
CenturyLink Cloud's SafeHaven disaster recovery service replicates customer virtual machines and data to an off-site location to protect against disasters like datacenter outages. It works by creating replicas of protected virtual machines that are kept in sync at a remote site using replication traffic. If the primary site goes down, control traffic directs failover to the recovery virtual machines at the remote site to maintain availability and services. SafeHaven provides disaster protection for on-premises CenturyLink Cloud customers.
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...Tatiana Kojar
Skybuffer AI, built on the robust SAP Business Technology Platform (SAP BTP), is the latest and most advanced version of our AI development, reaffirming our commitment to delivering top-tier AI solutions. Skybuffer AI harnesses all the innovative capabilities of the SAP BTP in the AI domain, from Conversational AI to cutting-edge Generative AI and Retrieval-Augmented Generation (RAG). It also helps SAP customers safeguard their investments into SAP Conversational AI and ensure a seamless, one-click transition to SAP Business AI.
With Skybuffer AI, various AI models can be integrated into a single communication channel such as Microsoft Teams. This integration empowers business users with insights drawn from SAP backend systems, enterprise documents, and the expansive knowledge of Generative AI. And the best part of it is that it is all managed through our intuitive no-code Action Server interface, requiring no extensive coding knowledge and making the advanced AI accessible to more users.
Nunit vs XUnit vs MSTest Differences Between These Unit Testing Frameworks.pdfflufftailshop
When it comes to unit testing in the .NET ecosystem, developers have a wide range of options available. Among the most popular choices are NUnit, XUnit, and MSTest. These unit testing frameworks provide essential tools and features to help ensure the quality and reliability of code. However, understanding the differences between these frameworks is crucial for selecting the most suitable one for your projects.
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Digital Marketing Trends in 2024 | Guide for Staying AheadWask
https://www.wask.co/ebooks/digital-marketing-trends-in-2024
Feeling lost in the digital marketing whirlwind of 2024? Technology is changing, consumer habits are evolving, and staying ahead of the curve feels like a never-ending pursuit. This e-book is your compass. Dive into actionable insights to handle the complexities of modern marketing. From hyper-personalization to the power of user-generated content, learn how to build long-term relationships with your audience and unlock the secrets to success in the ever-shifting digital landscape.
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Fueling AI with Great Data with Airbyte WebinarZilliz
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
This presentation provides valuable insights into effective cost-saving techniques on AWS. Learn how to optimize your AWS resources by rightsizing, increasing elasticity, picking the right storage class, and choosing the best pricing model. Additionally, discover essential governance mechanisms to ensure continuous cost efficiency. Whether you are new to AWS or an experienced user, this presentation provides clear and practical tips to help you reduce your cloud costs and get the most out of your budget.
Best 20 SEO Techniques To Improve Website Visibility In SERPPixlogix Infotech
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
5th LF Energy Power Grid Model Meet-up SlidesDanBrown980551
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
A Comprehensive Guide to DeFi Development Services in 2024Intelisync
DeFi represents a paradigm shift in the financial industry. Instead of relying on traditional, centralized institutions like banks, DeFi leverages blockchain technology to create a decentralized network of financial services. This means that financial transactions can occur directly between parties, without intermediaries, using smart contracts on platforms like Ethereum.
In 2024, we are witnessing an explosion of new DeFi projects and protocols, each pushing the boundaries of what’s possible in finance.
In summary, DeFi in 2024 is not just a trend; it’s a revolution that democratizes finance, enhances security and transparency, and fosters continuous innovation. As we proceed through this presentation, we'll explore the various components and services of DeFi in detail, shedding light on how they are transforming the financial landscape.
At Intelisync, we specialize in providing comprehensive DeFi development services tailored to meet the unique needs of our clients. From smart contract development to dApp creation and security audits, we ensure that your DeFi project is built with innovation, security, and scalability in mind. Trust Intelisync to guide you through the intricate landscape of decentralized finance and unlock the full potential of blockchain technology.
Ready to take your DeFi project to the next level? Partner with Intelisync for expert DeFi development services today!
leewayhertz.com-AI in predictive maintenance Use cases technologies benefits ...alexjohnson7307
Predictive maintenance is a proactive approach that anticipates equipment failures before they happen. At the forefront of this innovative strategy is Artificial Intelligence (AI), which brings unprecedented precision and efficiency. AI in predictive maintenance is transforming industries by reducing downtime, minimizing costs, and enhancing productivity.
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on automated letter generation for Bonterra Impact Management using Google Workspace or Microsoft 365.
Interested in deploying letter generation automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
30. The router shapes and routes all
external system traffic (HTTP/API)
and application traffic from the
internet/intranet. It maintains a
dynamic routing table for each
load-balanced app instance with
IP addresses and ports.
How It Works:
• Load balancing
• Maintaining an active routing table
• Access logs
• Supports web-sockets
Responsible For:
Router
31. The Cloud Controller maintains
command and control systems,
including interface with clients (CLI,
Web UI, Spring STS), account and
provisioning control. It also provides
RESTful interface to domain objects
(apps, services, organizations, spaces,
service instances, user roles, and
more).
How It Works:
• Expected App state, state
transitions, and desired
convergence
• Permissions/Auth
• Orgs/Spaces/Users
• Services management
• App placement
• Auditing/Journaling and billing
events
• Blob storage
Responsible For:
Cloud Controller
32. “Droplet Execution Agents” are secure
and fully isolated containers. DEAs are
responsible for an Apps lifecycle:
building, starting and stopping Apps
as instructed. They periodically
broadcast messages about their state
via the NATS message bus.
How It Works:
• Managing Linux containers (Warden)
• Monitoring resource pools
• Process
• File system
• Network
• Memory
• Managing app lifecycle
• App log and file streaming
• DEA heartbeats (NATS to CC, HM)
Responsible For:
DEA
33. Buildpacks are Ruby scripts that
detect application
runtimes/frameworks/plugins, compile
the source code into executable
binaries, and release the app to an
assigned DEA. Runtime components
can be cached for faster execution of
subsequent app pushes.
How It Works:
• Staging*
• /bin/detect
• /bin/compile
• /bin/release
• Configure droplet
• Runtime
(Ruby/Java/Node/Python)
• Container
(Tomcat/Websphere/Jetty)
• Application (.WAR, .rb, .js, .py)
Responsible For:
Buildpacks
34. Service Brokers provide an interface
for native and external 3rd party
services. Service processes run on
Service Nodes or with external as-a-
service providers (e.g., email,
database, messaging, etc.).
How It Works:
• Advertising service catalog
• Makes create/delete/bind/unbind
calls to service nodes
• Requests inventory of existing
instances and bindings from cloud
controller for caching, orphan
management
• SaaS marketplace gateway
• Implemented as HTTP enpoint,
written in any language.
Responsible For:
Service Broker
35. UPSI (formerly “Service Connectors”)
store meta-data in the Service Broker
to enable Cloud Foundry to connect
to local services that are NOT
managed by Cloud Foundry (e.g.,
OracleDB, DB2, SQLServer, etc.)
How It Works:
• Metadata management
Responsible For:
User Provided Service Instances
36. Health Manager monitors application
uptime by listening to the NATS
message bus for mismatched
application states (expected vs.
actual). The Cloud Controller publishes
expected state and the DEAs publish
actual state. State mismatches are
reported to the Cloud Controller.
How It Works:
• Maintains the actual state of apps
• Compares to expected state
• Sends suggestions to make actual
match expected (cannot make
state changes itself – only CC can
do that!)
Responsible For:
Health Manager
Editor's Notes
But first, here is my story.
CenturyLink – where we control one of the largest pools of IT infrastructure in the world that customers can slice up into subscription services of various shapes and sizes.
I work on our Cloud Specialist Team, where our mission is to help customers understand the value of our platform and to make them succesful on the platform.
Then blah…blah….blah
But first, here is my story.
CenturyLink – where we control one of the largest pools of IT infrastructure in the world that customers can slice up into subscription services of various shapes and sizes.
I work on our Cloud Specialist Team, where our mission is to help customers understand the value of our platform and to make them succesful on the platform.
Then blah…blah….blah
Put all your code in a source control system. Heck, just put it up on GitHub from the start.
All your application code lives in one repository. Once you get big, you may have a distributed system with multiple apps talking to each other (like a web application and a backend API), at which point you can treat them as separate apps with their own code repositories (still in source control, of course).
A codebase is run by developers on their local machines, and deployed to any number of other environments, like a set of testing machines, and the live production servers.
All the environments your code runs in need to have some dependencies, like a database, or an image processing library, or a command-line tool. Never let your application assume those things will be in place on a given machine. Ensure it by baking those dependencies into your software system.
Most languages and frameworks provide a natural way to do this. You list all the versions of all the libraries you expect to have in place, and when the code is deployed, a command is run to download all the right versions and put them in place. No guesswork, everything as it needs to be.
This philosophy extends to your devs or devops team managing entire machine configurations using management tools like Chef and Puppet
Importance: High Without this, your team will have a constant slow time-suck of confusion and frustration, multiplied by their size and number of applications. Spare yourself.
Configuration is anything that may vary between different environments. Code is all the stuff that doesn’t.
The code that talks to your database will always be the same. But the location of that database (which machine it’s running on) will be different for a local developer machine than it will for your production servers. Likewise, in your testing environment, you might want to log debugging information about each web request, but in production that would be overkill.
Usernames and passwords for various servers and services also count as configuration, and should never be stored in the code. This is especially true because your code is in source control (see I. above) which means that anyone with access to the source will know all your service passwords, which is a bad security hole as your team grows.
All configuration data should be stored in a separate place from the code, and read in by the code at runtime. Usually this means when you deploy code to an environment, you copy the correct configuration files into the codebase at that time.
Importance: Medium Lots of companies get away without this, but you’re sloppy if you do.
Your code will talk to many services, like a database, a cache, an email service, a queueing system, etc. These should all be referenced by a simple endpoint (URL) and maybe a username and password. They might be running on the same machine, or they might be on a different host, in a different datacenter, or managed by a cloud SaaS company. The point is, your code shouldn’t know the difference.
This allows great flexibility, so someone from your team could replace a local instance of Redis with one served by Amazon through Elasticache, and your code wouldn’t have to change.
This is another case where defining your dependencies cleanly keeps your system flexible and each part is abstracted from the complexities of the others…a core tenet of good architecture.
Importance: High Given the current bindings to services, there’s little reason not to adhere to this best-practice.
The process of turning the code into a bundle of scripts, assets and binaries that run the code is the build. The release sends that code to a server in a fresh package together with the nicely-separate config files for that environment (See III. above). Then the code is run so the application is available on those servers.
The idea here is that the build stage does a lot of heavy lifting, and developers manage it. The run stage should be simple and bullet-proof so that your team can sleep soundly through the night, knowing that the application is running well, and that if a machine gets restarted (say, a power failure happens) that the app will start up again on launch without the need for human intervention.
Importance: Conceptual From a practical perspective, the tools and framework you use will define best-practices for building, deploying, and running your app. Some do a better job than others of enforcing strict separation, but you should be okay if you follow your framework’s suggested mechanisms.
It’s likely you will have your application running on many servers, because that makes it more fault tolerant, and because you can support more traffic. As a rule, you want each of those instances of running code to be stateless. In other words, the state of your system is completely defined by your databases and shared storage, and not by each individual running application instance.
Let’s say you have a signup workflow, where a user has to enter 3 screens of information to create their profile. One (wrong) model would be to store each intermediate state in the running code, and direct the user back to the same server until the signup process is complete. The right approach is to store intermediate data in a database or persistent key-value store, so even if the web server goes down in the middle of the user’s signup, another web server can handle the traffic, and the system is none-the-wiser.
Importance: High Not only is a stateless app more robust, but it’s easier to manage, generally incurs fewer bugs, and scales better.
We’re getting a bit technical now, but stick with me. This factor is an extension of factor IV. above. The idea is that, just like all the backing services you are consuming, your application also interfaces to the world using a simple URL.
Usually you get this for free because your application is already presenting itself through a web-server. But let’s say you have an API that’s used by both your customers in the outside world (untrusted) and your internal website (trusted). You might create a separate URL to your API that your website can use which doesn’t go through the same security (firewall and authentication), so it’s a bit faster for you than for untrusted clients.
Importance: Medium Most runtime frameworks will give you this for free. If not, don’t sweat it. It’s a clean way to work, but it’s generally not hard to change later.
When running your code, the idea is that lots of little processes are handling specific needs. So you might have dozens of handlers at the ready to process web requests, and another dozen to handle API calls for your enterprise users. And still another half-dozen processing background welcome-emails going to new users, or sending tweets for your users sharing things on your social media service.
By keeping all these small parts working independently, and running them as separate processes (in a low-level technical sense), your application will scale better. In particular, you’ll be able to do more stuff concurrently, by smoothly adding additional servers, or additional CPU/RAM and taking full advantage of it through the use of more of these small, independent processes.
Importance: Low Don’t worry about this factor until you get pretty deep into scaling considerations. Trust your chief architect or CTO to raise the red flag if this is going to become an issue for you.
When you deploy new code, you want that new version to launch right away and start to handle traffic. If an application has to do 20 seconds of work (say, loading giant mapping files into RAM) before it’s ready to handle real traffic, you’ve made it harder to rapidly release code, and you’ve introduced more churn on the system to stop/start independent processes.
With the proliferation of so many 3rd party libraries in today’s software systems, sub–1-second startup times are less and less common. But beyond loading code, your application should have everything it needs waiting in high-speed databases or caches, so it can start up snappily and be ready to serve requests.
Further, your application should be robust against crashing. Meaning, if it does crash, it should always be able to start back up cleanly. You should never do any mandatory “cleanup” tasks when the app shuts down that might cause problems if they failed to run in a crash scenario.
Importance: Medium Depending on how often you are releasing new code (hopefully many times per day, if you can), and how much you have to scale your app traffic up and down on demand, you probably won’t have to worry about your startup/shutdown speed, but be sure to understand the implications for your app.
It has become in vogue in recent years to have a much more rapid cycle between developing a change to your app and deploying that change into production. For many companies, this happens in a matter of hours. In order to facilitate that shorter cycle, and the risk that something breaks when entering production, it’s desirable to keep a developer’s local environment as similar as possible to production.
This means using the same backing services, the same configuration management techniques, the same versions of software libraries, and so on.
This is often accomplished by letting developers use a tool like Vagrant to manage their own personal virtual server that’s configured just like production servers.
Importance: Medium Developers will feel like taking shortcuts if their local environment is working “well enough”. Talk them out of it and take a hard-line stance instead, it’ll pay off long-term.
Log files keep track of a variety of things, from the mundane (your app has started successfully) to the critical (users are receiving thousands of errors).
In an ideal situation, those logs are viewed by developers in their local consoles, and in production they are automatically captured as a stream of events and pushed into a real-time consolidated system for long-term archival and data-mining like Hadoop.
At the very least, you should be capturing errors and sending them to an error reporting service like New Relic or AirBrake. You can take a more general approach and send your logs to a service like PaperTrail or Splunk Storm.
Importance: Low If you are relying on logs as a primary forensic tool, you are probably already missing out on better solutions. Be sure to consolidate your logs for convenience, but beyond that, don’t worry about being a purist here.
You’ll want to do lots of one-off administrative tasks once you have a live app. For example, doing data cleanup on bad data you discover; running analytics for a presentation you are putting together, or turning on and off features for A/B testing.
Usually a developer will run these tasks, and when they do, they should be doing it from a machine in the production environment that’s running the latest version of the production code. In other words, run one-off admin tasks from an identical environment as production. Don’t run updates directly against a database, don’t run them from a local terminal window.
Importance: High Having console access to a production system is a critical administrative and debugging tool, and every major language/framework provides it. No excuses for sloppiness here.
Fully Isolated containers which are warden containers, but will be called garden container that will support build packs, docker, .NET containers.
DEA also manages lifecycle management for the app, so that would include starting, stopping apps as instructed by the cloud controller
Advertises the service catalog, so things like caching, message queues,.Emplemneted as a HTTP Endpoint and can support user defined services that live outside the platform. So for Example you could define an Oracle DB as an endpoint.
User provides instances are for services that live outside the platform, so for instance an Oracle DB, or maybe even a haddoop cluster.
Manages actual state and reports back to the cloud controller
So we’ve covered making sure you are aligned on defintions, defining your purpose and selecting a provider, now lets pass on some success characteristics we’ve seen utilized by customers we’ve seen successfully make the transition to cloud