Talk given at SpringOne 2015
The third platform, characterized by a fluid infrastructure where virtualized servers come into and out of existence, and workloads are constantly being moved about and scaled up and down to meet variable demand, calls for new design patterns, processes and even culture. One of the most well known descriptions of these new paradigms is the Twelve Factor App (12factor.net), which describes elements of cloud native applications. Many of these needs are squarely met through the Spring Framework, others require support from other systems. In this session we will examine each of the twelve factors and present how Spring, and platforms such as Cloud Foundry satisfy them, and in some cases we’ll even suggest that responsibility should shift from Spring to platforms. At the conclusion you will understand what is needed for cloud-native applications, why and how to deliver on those requirements.
Devops @ VMworld 2015 Presentation.
DevOps requires a separation of concerns between the application-focused teams and the platform-focused teams. While Platform and Application Operations have many similarities (monitor, logs, scale, upgrade, etc.) each is done with a different frame of reference. This workshop will provide an in-depth view into how a modern platform like Pivotal Cloud Foundry can eliminate the barriers between Development and Operations.
The workshop will showcase the difference in contexts for the application operations and platform operations teams, including monitoring, log analysis, capacity management, and upgrading. As well as show how separating the concerns of application operators (and application teams) from platform operators can remove the barriers between Dev and Ops. At this session we bring together both Dev and Ops with a combination of presentations and demos highlighting the capabilities of a modern platform. Monitor, log, scale, upgrade, and more, all with an integrated and auditable workflow for developers and operators.
Running your Spring Apps in the Cloud Javaone 2014cornelia davis
Walk through what it took to bring a Srping App initially built for 2nd platform (infrastructure dependent) deployment, and make it deployable to 3rd platform (Cloud Foundry).
Devops: Who Does What? - Devops Enterprise Summit 2016cornelia davis
Within the IT organizational structures that have dominated the last several decades roles and responsibilities are fairly standardized. But with the dramatic changes that DevOps practices and supporting toolsets bring, many are left feeling a bit off balance - it’s no longer clear who is responsible for even things as “straight-forward” as development or operations.
In this talk I will take traditional roles that are distributed across fairly standard IT structures and sort them into a new organizational context. What is the role of the Enterprise Architect? Who does capacity planning and how? How can change management step out of the way all while still satisfying the requirements of safe deployments? How do agile teams interface with personnel responsible for maintaining legacy systems? I’ll leave the audience with a blueprint for a new organizational structure.
Linux Collaboration Summit Keynote: Transformation: It Takes a Platformcornelia davis
The last decade has seen a revolution in the manner in which digital experiences are brought to consumers. The companies who are not just meeting increased consumer expectations, but are defining them, are operating within very different organizational structures than their predecessors, and are wrapping new processes around them. And they are using a fundamentally different toolset than before. In this talk we will cover a set of processes that serve this new paradigm and we’ll study the patterns that must be present in supporting software development and runtime platforms.
Devops Enterprise Summit: My Great Awakening: Top “Ah-ha” Moments As Former ...cornelia davis
After spending her entire career as a software developer, with nary a moment doing operations, Cornelia Davis found herself working on an application platform that serves operations as much as development. In order to better understand that world, she spent one month on the team that runs that platform in production. The experience brought lessons in organizational design, the value of pair-ops (in addition to pair programming) and test-driven development, the importance of addressing continuous integration as a first class concern, and how separating infrastructure ops from application ops serves the business and their customers better. In this session Cornelia will share the “prod incidents” that brought these teachings; the audience will gain an appreciation not only for what, but why the lessons are so important.
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.
Cloud-native Data: Every Microservice Needs a Cachecornelia davis
Presented at the Pivotal Toronto Users Group, March 2017
Cloud-native applications form the foundation for modern, cloud-scale digital solutions, and the patterns and practices for cloud-native at the app tier are becoming widely understood – statelessness, service discovery, circuit breakers and more. But little has changed in the data tier. Our modern apps are often connected to monolithic shared databases that have monolithic practices wrapped around them. As a result, the autonomy promised by moving to a microservices application architecture is compromised.
With lessons from the application tier to guide us, the industry is now figuring out what the cloud-native architectural patterns are at the data tier. Join us to explore some of these with Cornelia Davis, a five year Cloud Foundry veteran who is now focused on cloud-native data. As it happens, every microservice needs a cache and this evening will drill deep on that topic. She’ll cover a variety of caching patterns and use cases, and demonstrate how their use helps preserve the autonomy that is driving agile software delivery practices today.
Declarative Infrastructure with Cloud Foundry BOSHcornelia davis
Initially built to deploy and manage the Cloud Foundry “Elastic Runtime”, the platform that allows application developers and operators to easily deploy and manage applications and services through the entire app lifecycle (including production!), Cloud Foundry BOSH is a system that manages any virtual machine clusters of arbitrarily complex, distributed systems. You define your release through packages (what gets installed on the VMs), jobs (what is run on the VMs) and a deployment manifest (declaration of the cluster) and BOSH will first deploy and then continue to maintain your cluster to match that desired state. The result is a self-healing, eventually consistent system that markedly reduces the operational burdens and supports a great number of other Devops functions such as canary, zero-downtime upgrades, autoscaling, built in high availability and more. In this session we’ll show you how to create, deploy and manage a BOSH release, and we’ll watch what BOSH does when bad things happen.
Devops @ VMworld 2015 Presentation.
DevOps requires a separation of concerns between the application-focused teams and the platform-focused teams. While Platform and Application Operations have many similarities (monitor, logs, scale, upgrade, etc.) each is done with a different frame of reference. This workshop will provide an in-depth view into how a modern platform like Pivotal Cloud Foundry can eliminate the barriers between Development and Operations.
The workshop will showcase the difference in contexts for the application operations and platform operations teams, including monitoring, log analysis, capacity management, and upgrading. As well as show how separating the concerns of application operators (and application teams) from platform operators can remove the barriers between Dev and Ops. At this session we bring together both Dev and Ops with a combination of presentations and demos highlighting the capabilities of a modern platform. Monitor, log, scale, upgrade, and more, all with an integrated and auditable workflow for developers and operators.
Running your Spring Apps in the Cloud Javaone 2014cornelia davis
Walk through what it took to bring a Srping App initially built for 2nd platform (infrastructure dependent) deployment, and make it deployable to 3rd platform (Cloud Foundry).
Devops: Who Does What? - Devops Enterprise Summit 2016cornelia davis
Within the IT organizational structures that have dominated the last several decades roles and responsibilities are fairly standardized. But with the dramatic changes that DevOps practices and supporting toolsets bring, many are left feeling a bit off balance - it’s no longer clear who is responsible for even things as “straight-forward” as development or operations.
In this talk I will take traditional roles that are distributed across fairly standard IT structures and sort them into a new organizational context. What is the role of the Enterprise Architect? Who does capacity planning and how? How can change management step out of the way all while still satisfying the requirements of safe deployments? How do agile teams interface with personnel responsible for maintaining legacy systems? I’ll leave the audience with a blueprint for a new organizational structure.
Linux Collaboration Summit Keynote: Transformation: It Takes a Platformcornelia davis
The last decade has seen a revolution in the manner in which digital experiences are brought to consumers. The companies who are not just meeting increased consumer expectations, but are defining them, are operating within very different organizational structures than their predecessors, and are wrapping new processes around them. And they are using a fundamentally different toolset than before. In this talk we will cover a set of processes that serve this new paradigm and we’ll study the patterns that must be present in supporting software development and runtime platforms.
Devops Enterprise Summit: My Great Awakening: Top “Ah-ha” Moments As Former ...cornelia davis
After spending her entire career as a software developer, with nary a moment doing operations, Cornelia Davis found herself working on an application platform that serves operations as much as development. In order to better understand that world, she spent one month on the team that runs that platform in production. The experience brought lessons in organizational design, the value of pair-ops (in addition to pair programming) and test-driven development, the importance of addressing continuous integration as a first class concern, and how separating infrastructure ops from application ops serves the business and their customers better. In this session Cornelia will share the “prod incidents” that brought these teachings; the audience will gain an appreciation not only for what, but why the lessons are so important.
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.
Cloud-native Data: Every Microservice Needs a Cachecornelia davis
Presented at the Pivotal Toronto Users Group, March 2017
Cloud-native applications form the foundation for modern, cloud-scale digital solutions, and the patterns and practices for cloud-native at the app tier are becoming widely understood – statelessness, service discovery, circuit breakers and more. But little has changed in the data tier. Our modern apps are often connected to monolithic shared databases that have monolithic practices wrapped around them. As a result, the autonomy promised by moving to a microservices application architecture is compromised.
With lessons from the application tier to guide us, the industry is now figuring out what the cloud-native architectural patterns are at the data tier. Join us to explore some of these with Cornelia Davis, a five year Cloud Foundry veteran who is now focused on cloud-native data. As it happens, every microservice needs a cache and this evening will drill deep on that topic. She’ll cover a variety of caching patterns and use cases, and demonstrate how their use helps preserve the autonomy that is driving agile software delivery practices today.
Declarative Infrastructure with Cloud Foundry BOSHcornelia davis
Initially built to deploy and manage the Cloud Foundry “Elastic Runtime”, the platform that allows application developers and operators to easily deploy and manage applications and services through the entire app lifecycle (including production!), Cloud Foundry BOSH is a system that manages any virtual machine clusters of arbitrarily complex, distributed systems. You define your release through packages (what gets installed on the VMs), jobs (what is run on the VMs) and a deployment manifest (declaration of the cluster) and BOSH will first deploy and then continue to maintain your cluster to match that desired state. The result is a self-healing, eventually consistent system that markedly reduces the operational burdens and supports a great number of other Devops functions such as canary, zero-downtime upgrades, autoscaling, built in high availability and more. In this session we’ll show you how to create, deploy and manage a BOSH release, and we’ll watch what BOSH does when bad things happen.
Cloud Foundry and Microservices: A Mutualistic Symbiotic RelationshipMatt Stine
As delivered to the Cloud Foundry Summit 2014 in San Francisco, CA:
With businesses built around software now disrupting multiple industries that appeared to have stable leaders, the need has emerged for enterprises to create "software factories" built around the following principles:
* Streaming customer feedback directly into rapid, iterative cycles of application development
* Horizontally scaling applications to meet user demand
* Compatibility with an enormous diversity of clients, with mobility (smartphones, tablets, etc.) taking the lead
* Continuous delivery of value, shrinking the cycle time from concept to cash
Infrastructure has taken the lead in adapting to meet these needs with the move to the cloud, and Platform as a Service (PaaS) has raised the level of abstraction to a focus on an ecosystem of applications and services. However, most applications are still developed as if we're living in the previous generation of both business and infrastructure: the monolithic application. Microservices - small, loosely coupled applications that follow the Unix philosophy of "doing one thing well" - represent the application development side of enabling rapid, iterative development, horizontal scale, polyglot clients, and continuous delivery. They also enable us to scale application development and eliminate long term commitments to a single technology stack.
While microservices are simple, they are certainly not easy. It's recently been said that "microservices are not a free lunch". Interestingly enough, if you look at the concerns expressed here about microservices, you'll find that they are exactly the challenges that a PaaS is intended to address. So while microservices do not necessarily imply cloud (and vice versa), there is in fact a symbiotic relationship between the two, with each approach somehow compensating for the limitations of the other, much like the practices of eXtreme Programming.
The primary goals of this presentation are to:
- Show how to easily deploy Pivotal Cloud Foundry to CenturyLink Cloud with CenturyLink’s Blueprint technology
- Do a deep dive into the CF architecture via animated slides illustrating push, stage, deploy, scale and health management.
- Discuss in depth how Pivotal Cloud Foundry simplifies many traditional operator concerns such as managing application updates, availability, user/quota management and monitoring.
- Provide a brief introduction to BOSH, including why BOSH, what it is and animations of how it works.
- Discuss the value adds to CF BOSH OSS that Pivotal brings through the Pivotal Ops Manager product and our associated ecosystem of data and mobile services.
We are in the midst of a revolution. The ways in which software and value is delivered to users and the role that very frequent user feedback plays in the development lifecycle is radically different from legacy models that had software delivered on yearly cycles. The IT processes in place today cannot meet the new demands for weekly or daily releases, so we must change them. But these existing processes are serving a purpose, ensuring the quality, robustness, security and compliance of the software.
Today’s processes are centered on the client-server architectures that have reigned since the 1990s, and as a result the steps in the software development lifecycle (SDLC) predominantly involve performing operations on servers (and storage and networks). Further, IT job functions have been established to execute those processes.
In this talk we look at key existing requirements such as security and compliance, as well as some new ones such as rapid experimentation. We will rethink processes to satisfy these requirements and propose new organizational structures to execute them (spoiler alert, it is not a plan/build/run structure). Finally, we will detail some of the requirements on the IT system architectures that will allow these marked process changes. Session participants will leave with a concrete framework for transforming current IT practices, roles and responsibilities, and a clear understanding of the key technology enablers thereof.
Cloud Foundry Platform Operations - CF Summit 2015cornelia davis
In this session Cornelia will share lessons learned from a month spent on a team that operates a production instance of Cloud Foundry. From her first morning addressing a prod incident, through building ops dashboards, documenting how a crashed micro-bosh is recovered, and prod deploys, she will share lessons on the value of declarative, immutable infrastructure, cloud-native application design and proper abstractions. Tried and true practices such as checklists and jumpboxes remain, while new ones such as primetime deploys and even live experimentation in prod emerge. The punchline? Even as an ops novice, she was immediately productive. In this session Cornelia will present specific techniques for using BOSH, system metrics and logging, dashboards, alerting systems and more to manage your CF deployment.
Part 4: Custom Buildpacks and Data Services (Pivotal Cloud Platform Roadshow)VMware Tanzu
Custom Buildpacks & Data Services
The primary goals of this session are to:
Give an overview of the extension points available to Cloud Foundry users.
Provide a buildpack overview with a deep focus on the Java buildpack (my target audience has been Java conferences)
Provide an overview of service options, from user-provided to managed services, including an overview of the V2 Service Broker API.
Provide two hands-on lab experiences:
Java Buildpack Extension
via customization (add a new framework component)
via configuration (upgrade to Java 8)
Service Broker Development/Management
deploy a service broker for “HashMap as a Service (HaaSh).”
Register the broker, make the plan public.
create an instance of the HaaSh service
deploy a client app, bind to the service, and test it
Pivotal Cloud Platform Roadshow is coming to a city near you!
Join Pivotal technologists and learn how to build and deploy great software on a modern cloud platform. Find your city and register now http://bit.ly/1poA6PG
Evolving Devops: The Benefits of PaaS and Application Dial Tonecornelia davis
Differentiate between Infrastructure as a Service (IaaS), enhanced IaaS (Iaas+) and Platform as a Service (PaaS). We define IaaS+, which remains an infrastructure virtualization solution, and make clear the benefits of providing making the application (instead of the virtual machine) the first class abstraction with which developers and operations teams interact. When enough functionality is available around the *application* devops practices provide greater value.
These slides were presented as a part a Pivotal webinar - a replay can be accessed here: http://www.pivotal.io/platform-as-a-service/evolving-devops-the-benefits-of-paas-and-application-dial-tone
Driving Enterprise Architecture Redesign: Cloud-Native Platforms, APIs, and D...Chris Haddad
High performance architecture is rapidly changing due to three fundamental drivers:
Cloud-Native Platforms - change the way we think about operational infrastructure
DevOps - changes application lifecycle practices
APIs - change how we integrate and evolve infrastructure and applications, especially Mobile apps
In this session, Chris will illustrate:
Why you should consider Cloud-Native architecture components in your Enterprise Architecture
What is DevOps impact on App and API design guidelines
How API-centric focus revises Enterprise Architecture
At this joint NYC Cloud Foundry and NY PHP meetup, we'll discuss the shift to Platform-as-a-Service and what it means for PHP development on the cloud.
First, we'll take a look at the "traditional" cloud Infrastructure-as-a-Service (virtual servers and disks) model and describe how Platform-as-a-Service builds upon it to provide the runtimes and data services for hosting PHP applications.
We'll then demonstrate how a PHP developer can use buildpacks and services within a Cloud Foundry PaaS to deploy scalable and resilient apps to his or her cloud of choice.
Along the way we'll compare the variety of buildpacks available to PHP developers, show techniques for binding to services, and highlight best practices for creating born-on-the-cloud apps based on a microservices architecture.
Special thanks to Dan Mikusa for helping with the buildpack comparison.
PHP developers: Please give all three build packs a try. Provide your feedback and submit pull requests on GitHub.
12 Factor, or Cloud Native Apps - What EXACTLY Does that Mean for Spring Deve...VMware Tanzu
SpringOne Platform 2016
Speaker: Thomas Gamble; Director, Development, Home Depot
Your team is excited about getting started with Spring Boot and Cloud Native, but you're not entirely sure you're ready to have the team continuously delivering to prod using cf push from their local desktops. The freedom of cloud native development can be very empowering for developers, but it shouldn't be something that terrifies the operations and security teams. We'll discuss how you can setup a fast and reliable deployment process, as well as some interesting things to thing about in the future. One of the most well known descriptions of these new paradigms is the Twelve Factor App (12factor.net), which describes elements of cloud native applications. Many of these needs are squarely met through the Spring Framework, others require support from other systems. In this session we will examine each of the twelve factors and present how Spring, and platforms such as Cloud Foundry satisfy them, and in some cases we’ll even suggest that responsibility should shift from Spring to platforms. At the conclusion you will understand what is needed for cloud‐native applications, why and how to deliver on those requirements.
SpringOne Platform 2016
Speakers: Neville George; Principal Engineer, Comcast & Sergey Matochkin; Principal Architect, Comcast
Over the course of the last year, Comcast has matured its Cloud Foundry platform from proof-of-concept to production ready. The platform currently supports some of our most critical applications while also being an incubator for more innovation. Transitioning to a new platform is never easy and we have had to win over skeptics with operational excellence. Join us to hear about our experience with:
-Reducing Time to Market for new applications and services with PaaS
-Enabling DevOps with Cloud Foundry PaaS
-Extending Pivotal Cloud Foundry with new capabilities to meet DevOps needs
Cloud Native: Designing Change-tolerant Softwarecornelia davis
Delivered at Interop ITX 2017: http://info.interop.com/itx/2017/scheduler/session/cloud-native-designing-change-tolerant-software
Cloud-native applications are characterized by highly distributed topologies consisting of many relatively small components (yup, usually called microservices). But the thing that sets them apart from the previous generation of apps is that they are expected to function flawlessly even while the environment they are running in is constantly changing, or even failing. All of this requires applying a new set of design patterns and practices and this session will introduce the key ones. The Twelve Factor App (12factor.net) is a high-level articulation of some of these techniques that you may well have heard of, but its descriptions are relatively dense and the industry knowledge has evolved a fair bit since its publication.
Cornelia Davis will go through the best practices for cloud-native applications and clear some of the mystery that shrouds 12-factor today. At the conclusion, attendees will understand what is needed for cloud-native applications, as well as why and how to deliver on those requirements.
Creating Polyglot Communication Between Kubernetes Clusters and Legacy System...VMware Tanzu
SpringOne 2021
Session Title: Creating Polyglot Communication Between Kubernetes Clusters and Legacy Systems with an Event Mesh
Speakers: Michael Hilmen, Principal Architect at Solace; Robbie Jerrom, Principal SE - Office of the CTO at VMware
The 12 Factors for Building Cloud-Native SoftwareVMware Tanzu
Each slide covers one of the 12 factors, including what it is, why it's important and suggestions for how to implement it (with a focus on dot net applications). By Ed King, Pivotal.
https://drive.google.com/file/d/13_lD7Ve68_VbLeew7iqlkEpBVuPy7wXO/view
<November 2017 Updated from earlier presentations on Cloud-native Data>
Cloud-native applications form the foundation for modern, cloud-scale digital solutions, and the patterns and practices for cloud-native at the app tier are becoming widely understood – statelessness, service discovery, circuit breakers and more. But little has changed in the data tier. Our modern apps are often connected to monolithic shared databases that have monolithic practices wrapped around them. As a result, the autonomy promised by moving to a microservices application architecture is compromised.
What we need are patterns and practices for cloud-native data. The anti-patterns of shared databases and simple proxy-style web services to front them give way to approaches that include use of caches (Netflix calls caching their hidden microservice), database per service and polyglot persistence, modern versions of ETL and data integration and more. In this session, aimed at the application developer/architect, Cornelia will look at those patterns and see how they serve the needs of the cloud-native application.
Lattice: A Cloud-Native Platform for Your Spring ApplicationsMatt Stine
As presented at SpringOne2GX 2015 in Washington, DC.
Lattice is a cloud-native application platform that enables you to run your applications in containers like Docker, on your local machine via Vagrant. Lattice includes features like:
Cluster scheduling
HTTP load balancing
Log aggregation
Health management
Lattice does this by packaging a subset of the components found in the Cloud Foundry elastic runtime. The result is an open, single-tenant environment suitable for rapid application development, similar to Kubernetes and Mesos Applications developed using Lattice should migrate unchanged to full Cloud Foundry deployments.
Lattice can be used by Spring developers to spin up powerful micro-cloud environments on their desktops, and can be useful for developing and testing cloud-native application architectures. Lattice already has deep integration with Spring Cloud and Spring XD, and you’ll have the opportunity to see deep dives into both at this year’s SpringOne 2GX. This session will introduce the basics:
Installing Lattice
Lattice’s Architecture
How Lattice Differs from Cloud Foundry
How to Package and Run Your Spring Apps on Lattice
Cloud Foundry and Microservices: A Mutualistic Symbiotic RelationshipMatt Stine
As delivered to the Cloud Foundry Summit 2014 in San Francisco, CA:
With businesses built around software now disrupting multiple industries that appeared to have stable leaders, the need has emerged for enterprises to create "software factories" built around the following principles:
* Streaming customer feedback directly into rapid, iterative cycles of application development
* Horizontally scaling applications to meet user demand
* Compatibility with an enormous diversity of clients, with mobility (smartphones, tablets, etc.) taking the lead
* Continuous delivery of value, shrinking the cycle time from concept to cash
Infrastructure has taken the lead in adapting to meet these needs with the move to the cloud, and Platform as a Service (PaaS) has raised the level of abstraction to a focus on an ecosystem of applications and services. However, most applications are still developed as if we're living in the previous generation of both business and infrastructure: the monolithic application. Microservices - small, loosely coupled applications that follow the Unix philosophy of "doing one thing well" - represent the application development side of enabling rapid, iterative development, horizontal scale, polyglot clients, and continuous delivery. They also enable us to scale application development and eliminate long term commitments to a single technology stack.
While microservices are simple, they are certainly not easy. It's recently been said that "microservices are not a free lunch". Interestingly enough, if you look at the concerns expressed here about microservices, you'll find that they are exactly the challenges that a PaaS is intended to address. So while microservices do not necessarily imply cloud (and vice versa), there is in fact a symbiotic relationship between the two, with each approach somehow compensating for the limitations of the other, much like the practices of eXtreme Programming.
The primary goals of this presentation are to:
- Show how to easily deploy Pivotal Cloud Foundry to CenturyLink Cloud with CenturyLink’s Blueprint technology
- Do a deep dive into the CF architecture via animated slides illustrating push, stage, deploy, scale and health management.
- Discuss in depth how Pivotal Cloud Foundry simplifies many traditional operator concerns such as managing application updates, availability, user/quota management and monitoring.
- Provide a brief introduction to BOSH, including why BOSH, what it is and animations of how it works.
- Discuss the value adds to CF BOSH OSS that Pivotal brings through the Pivotal Ops Manager product and our associated ecosystem of data and mobile services.
We are in the midst of a revolution. The ways in which software and value is delivered to users and the role that very frequent user feedback plays in the development lifecycle is radically different from legacy models that had software delivered on yearly cycles. The IT processes in place today cannot meet the new demands for weekly or daily releases, so we must change them. But these existing processes are serving a purpose, ensuring the quality, robustness, security and compliance of the software.
Today’s processes are centered on the client-server architectures that have reigned since the 1990s, and as a result the steps in the software development lifecycle (SDLC) predominantly involve performing operations on servers (and storage and networks). Further, IT job functions have been established to execute those processes.
In this talk we look at key existing requirements such as security and compliance, as well as some new ones such as rapid experimentation. We will rethink processes to satisfy these requirements and propose new organizational structures to execute them (spoiler alert, it is not a plan/build/run structure). Finally, we will detail some of the requirements on the IT system architectures that will allow these marked process changes. Session participants will leave with a concrete framework for transforming current IT practices, roles and responsibilities, and a clear understanding of the key technology enablers thereof.
Cloud Foundry Platform Operations - CF Summit 2015cornelia davis
In this session Cornelia will share lessons learned from a month spent on a team that operates a production instance of Cloud Foundry. From her first morning addressing a prod incident, through building ops dashboards, documenting how a crashed micro-bosh is recovered, and prod deploys, she will share lessons on the value of declarative, immutable infrastructure, cloud-native application design and proper abstractions. Tried and true practices such as checklists and jumpboxes remain, while new ones such as primetime deploys and even live experimentation in prod emerge. The punchline? Even as an ops novice, she was immediately productive. In this session Cornelia will present specific techniques for using BOSH, system metrics and logging, dashboards, alerting systems and more to manage your CF deployment.
Part 4: Custom Buildpacks and Data Services (Pivotal Cloud Platform Roadshow)VMware Tanzu
Custom Buildpacks & Data Services
The primary goals of this session are to:
Give an overview of the extension points available to Cloud Foundry users.
Provide a buildpack overview with a deep focus on the Java buildpack (my target audience has been Java conferences)
Provide an overview of service options, from user-provided to managed services, including an overview of the V2 Service Broker API.
Provide two hands-on lab experiences:
Java Buildpack Extension
via customization (add a new framework component)
via configuration (upgrade to Java 8)
Service Broker Development/Management
deploy a service broker for “HashMap as a Service (HaaSh).”
Register the broker, make the plan public.
create an instance of the HaaSh service
deploy a client app, bind to the service, and test it
Pivotal Cloud Platform Roadshow is coming to a city near you!
Join Pivotal technologists and learn how to build and deploy great software on a modern cloud platform. Find your city and register now http://bit.ly/1poA6PG
Evolving Devops: The Benefits of PaaS and Application Dial Tonecornelia davis
Differentiate between Infrastructure as a Service (IaaS), enhanced IaaS (Iaas+) and Platform as a Service (PaaS). We define IaaS+, which remains an infrastructure virtualization solution, and make clear the benefits of providing making the application (instead of the virtual machine) the first class abstraction with which developers and operations teams interact. When enough functionality is available around the *application* devops practices provide greater value.
These slides were presented as a part a Pivotal webinar - a replay can be accessed here: http://www.pivotal.io/platform-as-a-service/evolving-devops-the-benefits-of-paas-and-application-dial-tone
Driving Enterprise Architecture Redesign: Cloud-Native Platforms, APIs, and D...Chris Haddad
High performance architecture is rapidly changing due to three fundamental drivers:
Cloud-Native Platforms - change the way we think about operational infrastructure
DevOps - changes application lifecycle practices
APIs - change how we integrate and evolve infrastructure and applications, especially Mobile apps
In this session, Chris will illustrate:
Why you should consider Cloud-Native architecture components in your Enterprise Architecture
What is DevOps impact on App and API design guidelines
How API-centric focus revises Enterprise Architecture
At this joint NYC Cloud Foundry and NY PHP meetup, we'll discuss the shift to Platform-as-a-Service and what it means for PHP development on the cloud.
First, we'll take a look at the "traditional" cloud Infrastructure-as-a-Service (virtual servers and disks) model and describe how Platform-as-a-Service builds upon it to provide the runtimes and data services for hosting PHP applications.
We'll then demonstrate how a PHP developer can use buildpacks and services within a Cloud Foundry PaaS to deploy scalable and resilient apps to his or her cloud of choice.
Along the way we'll compare the variety of buildpacks available to PHP developers, show techniques for binding to services, and highlight best practices for creating born-on-the-cloud apps based on a microservices architecture.
Special thanks to Dan Mikusa for helping with the buildpack comparison.
PHP developers: Please give all three build packs a try. Provide your feedback and submit pull requests on GitHub.
12 Factor, or Cloud Native Apps - What EXACTLY Does that Mean for Spring Deve...VMware Tanzu
SpringOne Platform 2016
Speaker: Thomas Gamble; Director, Development, Home Depot
Your team is excited about getting started with Spring Boot and Cloud Native, but you're not entirely sure you're ready to have the team continuously delivering to prod using cf push from their local desktops. The freedom of cloud native development can be very empowering for developers, but it shouldn't be something that terrifies the operations and security teams. We'll discuss how you can setup a fast and reliable deployment process, as well as some interesting things to thing about in the future. One of the most well known descriptions of these new paradigms is the Twelve Factor App (12factor.net), which describes elements of cloud native applications. Many of these needs are squarely met through the Spring Framework, others require support from other systems. In this session we will examine each of the twelve factors and present how Spring, and platforms such as Cloud Foundry satisfy them, and in some cases we’ll even suggest that responsibility should shift from Spring to platforms. At the conclusion you will understand what is needed for cloud‐native applications, why and how to deliver on those requirements.
SpringOne Platform 2016
Speakers: Neville George; Principal Engineer, Comcast & Sergey Matochkin; Principal Architect, Comcast
Over the course of the last year, Comcast has matured its Cloud Foundry platform from proof-of-concept to production ready. The platform currently supports some of our most critical applications while also being an incubator for more innovation. Transitioning to a new platform is never easy and we have had to win over skeptics with operational excellence. Join us to hear about our experience with:
-Reducing Time to Market for new applications and services with PaaS
-Enabling DevOps with Cloud Foundry PaaS
-Extending Pivotal Cloud Foundry with new capabilities to meet DevOps needs
Cloud Native: Designing Change-tolerant Softwarecornelia davis
Delivered at Interop ITX 2017: http://info.interop.com/itx/2017/scheduler/session/cloud-native-designing-change-tolerant-software
Cloud-native applications are characterized by highly distributed topologies consisting of many relatively small components (yup, usually called microservices). But the thing that sets them apart from the previous generation of apps is that they are expected to function flawlessly even while the environment they are running in is constantly changing, or even failing. All of this requires applying a new set of design patterns and practices and this session will introduce the key ones. The Twelve Factor App (12factor.net) is a high-level articulation of some of these techniques that you may well have heard of, but its descriptions are relatively dense and the industry knowledge has evolved a fair bit since its publication.
Cornelia Davis will go through the best practices for cloud-native applications and clear some of the mystery that shrouds 12-factor today. At the conclusion, attendees will understand what is needed for cloud-native applications, as well as why and how to deliver on those requirements.
Creating Polyglot Communication Between Kubernetes Clusters and Legacy System...VMware Tanzu
SpringOne 2021
Session Title: Creating Polyglot Communication Between Kubernetes Clusters and Legacy Systems with an Event Mesh
Speakers: Michael Hilmen, Principal Architect at Solace; Robbie Jerrom, Principal SE - Office of the CTO at VMware
The 12 Factors for Building Cloud-Native SoftwareVMware Tanzu
Each slide covers one of the 12 factors, including what it is, why it's important and suggestions for how to implement it (with a focus on dot net applications). By Ed King, Pivotal.
https://drive.google.com/file/d/13_lD7Ve68_VbLeew7iqlkEpBVuPy7wXO/view
<November 2017 Updated from earlier presentations on Cloud-native Data>
Cloud-native applications form the foundation for modern, cloud-scale digital solutions, and the patterns and practices for cloud-native at the app tier are becoming widely understood – statelessness, service discovery, circuit breakers and more. But little has changed in the data tier. Our modern apps are often connected to monolithic shared databases that have monolithic practices wrapped around them. As a result, the autonomy promised by moving to a microservices application architecture is compromised.
What we need are patterns and practices for cloud-native data. The anti-patterns of shared databases and simple proxy-style web services to front them give way to approaches that include use of caches (Netflix calls caching their hidden microservice), database per service and polyglot persistence, modern versions of ETL and data integration and more. In this session, aimed at the application developer/architect, Cornelia will look at those patterns and see how they serve the needs of the cloud-native application.
Lattice: A Cloud-Native Platform for Your Spring ApplicationsMatt Stine
As presented at SpringOne2GX 2015 in Washington, DC.
Lattice is a cloud-native application platform that enables you to run your applications in containers like Docker, on your local machine via Vagrant. Lattice includes features like:
Cluster scheduling
HTTP load balancing
Log aggregation
Health management
Lattice does this by packaging a subset of the components found in the Cloud Foundry elastic runtime. The result is an open, single-tenant environment suitable for rapid application development, similar to Kubernetes and Mesos Applications developed using Lattice should migrate unchanged to full Cloud Foundry deployments.
Lattice can be used by Spring developers to spin up powerful micro-cloud environments on their desktops, and can be useful for developing and testing cloud-native application architectures. Lattice already has deep integration with Spring Cloud and Spring XD, and you’ll have the opportunity to see deep dives into both at this year’s SpringOne 2GX. This session will introduce the basics:
Installing Lattice
Lattice’s Architecture
How Lattice Differs from Cloud Foundry
How to Package and Run Your Spring Apps on Lattice
Building a Secure App with Google Polymer and Java / Springsdeeg
Polymer is the latest web framework out of Google. Designed completely around the emerging Web Components standards, it has the lofty goal of making it easy to build apps based on these low level primitives. Along with Polymer comes a new set of Elements (buttons, dialog boxes and such) based on the ideas of "Material Design". These technologies together make it easy to build responsive, componentized "Single Page" web applications that work for browsers on PCs or mobile devices. But what about the backend, and how do we make these apps secure? In this talk Scott Deeg will take you through an introduction to Polmyer and its related technologies, and then through the build out of a full blown cloud based app with a secure, ReSTful backend based on Spring ReST, Spring Cloud, and Spring Security and using Thymeleaf for backend rendering jobs. At the end he will show the principles applied in a tool he's currently building. The talk will be mainly code walk through and demo, and assumes familiarity with Java/Spring and JavaScript.
Cloud Native Java with Spring Cloud ServicesVMware Tanzu
SpringOne Platform 2016
Speakers: Craig Walls; Spring Social Lead, Pivotal. Roy Clarkson; Spring Mobile Lead, Pivotal.
Developing cloud native applications presents several challenges. How do microservices discover each other? How do you configure them? How can you make them resilient to failure? How can you monitor the health of each microservice?
Spring Cloud addresses all of these concerns. Even so, you still must explicitly develop your own discovery server, configuration server, and circuit breaker dashboard for monitoring the circuit breakers in each microservice.
Spring Cloud Services for Pivotal Cloud Foundry picks up where Spring Cloud leaves off, offering a discovery server, configuration server, and Hystrix dashboard as services that can be bound to applications deployed in Pivotal Cloud Foundry, leaving you to focus on developing the services that drive your application. In this talk, we will introduce the capabilities provided by Spring Cloud Services and demonstrate how it makes simple work of deploying cloud native applications to Cloud Foundry.
Migrating to Angular 4 for Spring Developers VMware Tanzu
SpringOne Platform 2017
Gunnar Hillert, Pivotal
You have the goal to migrate your project from AngularJS 1.x to Angular 4. This should be straightforward, except you are realizing that your 3 year old technology stack is totally outdated (Grunt, RequireJS, Bower et al). Furthermore, you are using an older AngularJS 1.x version and your architecture does not conform with the latest 1.x architectural recommendations. At this point things start to look daunting. In this talk we discuss the challenges, experiences and reasons for migrating the Spring Cloud Data Flow Dashboard from using AngularJS 1.x to Angular 4. We also show how we effectively integrate our Angular front-end with Spring Boot.
Migrating to Angular 5 for Spring DevelopersGunnar Hillert
You have the goal to migrate your project from AngularJS 1.x to Angular 4 and Angular 5. This should be straightforward, except you are realizing that your 3 year old technology stack is totally outdated (Grunt, RequireJS, Bower et al). Furthermore, you are using an older AngularJS 1.x version and your architecture does not conform with the latest 1.x architectural recommendations. At this point things start to look daunting. In this talk we discuss the challenges, experiences and reasons for migrating the Spring Cloud Data Flow Dashboard from using AngularJS 1.x to Angular 5. We also show how we effectively integrate our Angular front-end with Spring Boot.
Continuous Delivery for Microservice Architectures with Concourse & Cloud Fou...VMware Tanzu
SpringOne Platform 2016
Speaker: Alex Ley; Product Manager, Pivotal
Building a continuous delivery pipeline for your micro-service based architecture can be a real challenge when using more conventional CI systems like Jenkins and GoCD. How do you get a clear picture of the CI workflow and status? What artifact was deployed and when? How is this all configured?
Introducing Concourse (https://concourse.ci), an open source pipeline based CI system that focuses on simplicity, usability and reproducibility. It offers isolated builds, a range of integrations and is built upon a proven technology stack from Cloud Foundry.
This talk will demonstrate creating a continuous delivery pipeline for a Spring microservice-based application that uses Spring Cloud. You will see how the pipeline tests services, integrates and then blue / green deploys to Cloud Foundry.
Expect to rush to your laptop to try out Concourse after this session!
Developing Real-Time Data Pipelines with Apache KafkaJoe Stein
Developing Real-Time Data Pipelines with Apache Kafka http://kafka.apache.org/ is an introduction for developers about why and how to use Apache Kafka. Apache Kafka is a publish-subscribe messaging system rethought of as a distributed commit log. Kafka is designed to allow a single cluster to serve as the central data backbone. A single Kafka broker can handle hundreds of megabytes of reads and writes per second from thousands of clients. It can be elastically and transparently expanded without downtime. Data streams are partitioned and spread over a cluster of machines to allow data streams larger than the capability of any single machine and to allow clusters of coordinated consumers. Messages are persisted on disk and replicated within the cluster to prevent data loss. Each broker can handle terabytes of messages. For the Spring user, Spring Integration Kafka and Spring XD provide integration with Apache Kafka.
The many benefits of a RESTful architecture has made it the standard way in which to design web based APIs. For example, the principles of REST state that we should leverage standard HTTP verbs which helps to keep our APIs simple. Server components that are considered RESTFul should be stateless which help to ensure that they can easily scale. We can leverage caching to gain further performance and scalability benefits.
However, the best practices of REST and security often seem to clash. How should a user be authenticated in a stateless application? How can a secured resource also support caching? Securing RESTful endpoints is further complicated by the the fact that security best practices evolve so rapidly.
In this talk Rob will discuss how to properly secure your RESTful endpoints. Along the way we will explore some common pitfalls when applying security to RESTful APIs. Finally, we will see how the new features in Spring Security can greatly simplify securing your RESTful APIs.
SpringOne Platform 2017
Xiaokai He, Microsoft; Chris Anderson, Microsoft
Are you struggling with diagnosing your serverless functions? In this live coding session, we will quickly develop and deploy a serverless application to cloud, and then show you how we can go inside the black box and debugging functions locally and remotely.
Our previous talk "Intro to Reactive Programming" defined reactive programming and provided details around key initiatives such as Reactive Streams and ReactiveX. In this talk we'll focus on where we are today with building reactive web applications. We'll take a look at the choice of runtimes, how Reactive Streams may be applied to network I/O, and what the programming model may look like. While this is a forward looking talk, we'll spend plenty of time demoing code built with with back-pressure ready libraries available today.
SpringFramework 5에서 선보이는 Reactive와 같은 핵심기능이 2017 2017년 12월 샌프란시스코에서 열린 Spring One Platform행사에서 소개된 내용중 Spring Data, Spring Security, Spring WebFlux프로젝트에 녹아져 있는지 살펴봅니다. 또한 이러한 기능들이 어떻게 여러분의 시스템의 반응성을 높이고 효율적으로 동작하게 하는지 알아봅니다.
Cassandra and DataStax Enterprise on PCFVMware Tanzu
SpringOne Platform 2016
Speakers: Ben Lackey; Partner Architect, Datastax. Cornelia Davis; Sr. Director of Technology, Pivotal.
DataStax Enterprise (DSE) is a distributed database built on Apache Cassandra with support for Spark, Solr and graph database. Bringing DSE support to the Pivotal Cloud Foundry application platform allows developers and operators to self-service provision DSE clusters and easily connect them to Spring Boot apps running in and managed by PCF. In this session we’ll start with the use cases for on-demand, dedicated DSE clusters, cover the solution design, and demo the system. The creation of on-demand clusters takes full advantage of BOSH 2.0 and we’ll go just a little bit under the covers to show you how these new BOSH features rock this use case. Finally, we’ll complete the story by looking at the support that Spring has for Cassandra.
Fast 5 Things You Can Do Now to Get Ready for the CloudVMware Tanzu
SpringOne Platform 2019
Fast 5 Things You Can Do Now to Get Ready for the Cloud
Speaker: Robert Sirchia, Practice Lead, Magenic Technologies
YouTube: https://youtu.be/WLw82cV0Lwk
As the complexity of web and mobile apps increases, so does the importance of ensuring that your client-side resources load and execute in an optimal and efficient manner. Differences in resource loading, transforming, and fingerprinting techniques can have a dramatic impact on performance and caching. These techniques can dictate whether your users have a joyful or frustrating experience. Attend this talk to learn the SpringMVC performance techniques aimed at keeping your users happy.
A video of this presentation is available from InfoQ:
http://www.infoq.com/presentations/resource-spring-mvc-4-1
Similar to 12 Factor, or Cloud Native Apps – What EXACTLY Does that Mean for Spring Developers? (20)
You've Made Kubernetes Available to Your Developers, Now What?cornelia davis
Congratulations! You’ve built out your Kubernetes infrastructure and it’s ready for prime-time. But if you want to optimize for Developer Productivity, Operational Efficiency, Security Posture, you have more to do. Do your developers know how to build secure containers? Do they know about persistent volumes and claims? Setting pod security policies? Are they willing to take on operational responsibilities (and are you ok delegating that to them?). Who’s responsible for addressing OS vulnerabilities?
Kubernetes doesn’t address these concerns, but it’s likely you are responsible for finding the answers. In this session we’ll equip you with tools and techniques to solve these problems, based on our experience deploying hundreds of thousands of containers across Fortune 500 organizations.
You Might Just be a Functional Programmer Nowcornelia davis
The declarative programming model of Kubernetes is markedly different from what most developers are used to. That the API is a set of resources rather than a list of methods on objects is a bit mind bending. But this programming model is not entirely new – rather, it smacks quite heavily of functional programming.
Functional programming had mostly been relegated to academic endeavors until recently. What’s changed that is that our apps are now distributed systems and are simply too complex for us to reason about without help. Kubernetes helps.
In order to effectively use Kubernetes to deploy and manage your workloads you need to understand some of the principles of functional programming and how they surface in K8s. In this session I will cover these underlying principles of the K8s programming model so that you can up the robustness and manageability of your application deployments.
Presented at KubeCon Barcelona, May 2019
When we think about establishing a Kubernetes capability for our organization, our instinct, or perhaps just habit, might lead us to stand up a single cluster that will then be a shared resource across numerous tenants. Kubernetes offers namespaces that are intended to carve up the capacity across different users or groups of users. And while this may work well in some scenarios, it does impose certain constraints and limitations on its use. For example, it is well understood that the multitenancy in Kubernetes is soft, meaning it does not guard against deliberately malicious attacks from one tenant to another.
If instead, we align tenant boundaries to Kubernetes clusters, effectively creating many single tenant clusters we can not only avoid certain limitations but we gain some significant advantages. Add a control plane for managing these sets of clusters and we have a powerful solution built on decades of maturity in machine virtualization.
In this session we will present both models, multi-tenant clusters and multi-clusters and study the tradeoffs of each.
Pivotal Container Service (PKS) at SF Cloud Foundry Meetupcornelia davis
Overview of Pivotal Container Service (PKS), built on the open source Cloud Foundry Container Runtime (CFCR). Covers what Kubernetes is, how PKS presents a complete platform that includes Kubernetes and much more, and key cloud principles.
Presented at the San Francisco-Bay Area Cloud Foundry meetup.
It’s Not Just Request/Response: Understanding Event-driven Microservicescornelia davis
Why all of the recent buzz around event-driven architectures? Software solutions have implemented event-driven patterns for some time, using message brokers such as RabbitMQ or ActiveMQ. Use of these message brokers is so ubiquitous that every J2EE platform such as WebSphere or WebLogic embeds one.
What is new is that we are reexamining event-driven approaches in the context of microservices. On the one hand, microservices don’t change things too much—the scenarios that called for message queuing in the past remain. Where eventing starts to get interesting is when we start applying it to scenarios we once used a request/response model. We can turn the processing on its head by propagating events through a network of microservices. Doing so can yield more autonomous microservices and more resilient systems.
In this session Cornelia Davis, Senior Director of Technology at Pivotal will examine this approach, describing the architectural tenets and analyzing the benefits and tradeoffs. By the end of this webinar, you will have some very concrete techniques that you can immediately put into practice.
In June 2017 at the Devops Enterprise Summit in London, while announcing the 2017 State of Devops Report with his esteemed colleagues, Jez Humble reveled that their studies showed that there was a strong correlation between high-functioning teams and the architecture of the software they are building, deploying and managing. In short - architecture matters to Devops.
In this talk Cornelia goes over a host of software architectural patterns and their relationship to some of the key goals of Devops - "higher throughput and higher quality and stability." Cloud native applications and cloud native data are both covered.
Kubo (Cloud Foundry Container Platform): Your Gateway Drug to Cloud-nativecornelia davis
You’re at the Cloud Foundry Summit, which means you are by definition a cloud-native enthusiast. There’s no question that building apps in this architectural style will produce resilient, scalable software in an agile manner, and allow you to operate it far more efficiently than you’ve been able to in the past. But you’ve also got a whole lot of software in your company’s portfolio that isn’t there yet. Do you have to resign yourself to the pains of managing those applications the old way until you can finally refactor them to be cloud-native? Kubo to the rescue.
You can run legacy applications on Kubo without significant refactoring – pure and simple. As an added bonus, it allows you to satisfy the CIO mandate of running containers (check). But it’s far more than that – running those workloads on Kubo offers advantages over running them on traditional virtualized infrastructure. This session covers those advantages –resource consolidation, health management, multi-cloud and more. It will also present the abstractions in Kubernetes, things like pods and stateful sets, that support running legacy workloads in the cloud environments that are far more distributed and changing than they have been in the past. It’s a first step to cloud-native.
Cloud Native: Designing Change-tolerant Softwarecornelia davis
To see this presentation given live, go to http://bit.ly/DesignPatternsReplay
There is a special (discount) offer in there! :-)
Cloud-native applications are characterized by highly distributed topologies consisting of many relatively small components (yup, usually called microservices). But the thing that sets them apart even more from the previous generation of apps is that they are expected to function flawlessly even while the environment they are running in is constantly changing, or even failing.
All of this requires applying a new set of design patterns and practices and this webinar will introduce the most important ones. The Twelve Factor App (12factor.net) is a high-level articulation of some of these techniques that you may well have heard of, but its descriptions are relatively dense and the industry knowledge has evolved a fair bit since its publication.
Cornelia Davis, Senior Director of Technology at Pivotal, will share best practices for cloud-native applications and clear some of the mystery that shrouds 12-factor today. At the conclusion, attendees will understand what is needed for cloud-native applications, as well as why and how to deliver on those requirements.
Devops: Enabled Through a Recasting of Operational Rolescornelia davis
Delivered at CF Summit Berlin, 2 Nov 2015.
One thing that everyone agrees on is that “Devops” is about reducing the friction between dev and ops. While it might not be immediately apparent, CF enables a separation of “operations” into two roles: platform ops and application ops. Platform ops is responsible for maintaining a secure platform with sufficient functionality and capacity so that application developers and application operators can perform their work. And application operators are responsible for keeping business applications up and running, so that consumers receive superior service, 24x7x365. By moving further up the stack, app operators can be far closer to the line of business owners, getting them speaking the same language. In this session we demonstrate how Cloud Foundry enables this, we talk about customers who are taking advantage of it, and we cover the tools available for each of the roles.
Cloud Foundry Diego, Lattice, Docker and morecornelia davis
Colorado Cloud Foundry Meetup
May 19, 2015
Lattice and Docker with Cornelia Davis
Starting with a comparison of the current core runtime of the Cloud Foundry Elastic Runtime, to the new Diego rewrite, we take a tour through how linux containers can run a variety of image formats, including Docker. We talk about one way that you can get the Diego functionality in Lattice, a container scheduler that runs on a laptop or as a cluster in the cloud. We talk about ways of creating container images including Cloud Rocker and we draw it all together with a bunch of demos.
Abstract from the meetup:
What is Lattice (www.lattice.cf)?
Lattice is an open source project for running containerized workloads on a cluster. A Lattice cluster is comprised of a number of Lattice Cells (VMs that run containers) and a Lattice Coordinator that monitors the Cells.
Lattice includes built-in http load-balancing, a cluster scheduler, log aggregation with log streaming and health management.
Lattice containers are described as long-running processes or temporary tasks. Lattice includes support for Linux Containers expressed either as Docker Images or by composing applications as binary code on top of a root file system. Lattice's container pluggability will enable other backends such as Windows or Rocket in the future.
Competing with Software: It Takes a Platform -- Devops @ EMC Worldcornelia davis
Presentation at Devops @ EMC World event, 3 May 2015
In Mark Andreessen’s 2010 piece for the Wall Street Journal, in which he declared “Software is Eating the World,” he talked about well established, large enterprises loosing footing to small, nimble startup companies who are far better at bringing software to their consumers. In fact, it’s not as much that these upstarts are better at meeting customer demands, rather they are the cause of the increased expectations, providing consumers with things they didn’t even know they wanted. What are the factors behind their success? New development and operational approaches including extreme agile & test driven development, continuous delivery and devops practices all play a significant role, and while a part of the difference is cultural, tools matter. In this session we’ll look at why a software-driven enterprise needs platform. Google has one. Facebook has one. Netflix has one. Your enterprise needs one.
Keynote presentation for the Pivotal Cloud Platform Roadshow. Introduces the market drivers for the Cloud Foundry Platform as a Service, discusses open source softwared (Cloud Foundry is OSS) and introduces the fundamentals of the platform.
Software Quality in the Devops World: The Impact of Continuous Delivery on Te...cornelia davis
Covers techniques, both technical and cultural/process, for ensuring quality in software delivered in the continuous delivery world we live in today.
First presented at the IC3 Conference in October 2014.
Cloud Foundry Introduction (w Demo) at Silicon Valley Code Campcornelia davis
Silicon Valley Code Camp, The Self-healing Elastic Runtime that is Cloud Foundry.
While we did mostly demo in this session, these slides set a bit of context first. Also includes the four levels of HA in Cloud Foundry.
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.
How Does XfilesPro Ensure Security While Sharing Documents in Salesforce?XfilesPro
Worried about document security while sharing them in Salesforce? Fret no more! Here are the top-notch security standards XfilesPro upholds to ensure strong security for your Salesforce documents while sharing with internal or external people.
To learn more, read the blog: https://www.xfilespro.com/how-does-xfilespro-make-document-sharing-secure-and-seamless-in-salesforce/
Why React Native as a Strategic Advantage for Startup Innovation.pdfayushiqss
Do you know that React Native is being increasingly adopted by startups as well as big companies in the mobile app development industry? Big names like Facebook, Instagram, and Pinterest have already integrated this robust open-source framework.
In fact, according to a report by Statista, the number of React Native developers has been steadily increasing over the years, reaching an estimated 1.9 million by the end of 2024. This means that the demand for this framework in the job market has been growing making it a valuable skill.
But what makes React Native so popular for mobile application development? It offers excellent cross-platform capabilities among other benefits. This way, with React Native, developers can write code once and run it on both iOS and Android devices thus saving time and resources leading to shorter development cycles hence faster time-to-market for your app.
Let’s take the example of a startup, which wanted to release their app on both iOS and Android at once. Through the use of React Native they managed to create an app and bring it into the market within a very short period. This helped them gain an advantage over their competitors because they had access to a large user base who were able to generate revenue quickly for them.
Software Engineering, Software Consulting, Tech Lead.
Spring Boot, Spring Cloud, Spring Core, Spring JDBC, Spring Security,
Spring Transaction, Spring MVC,
Log4j, REST/SOAP WEB-SERVICES.
Cyaniclab : Software Development Agency Portfolio.pdfCyanic lab
CyanicLab, an offshore custom software development company based in Sweden,India, Finland, is your go-to partner for startup development and innovative web design solutions. Our expert team specializes in crafting cutting-edge software tailored to meet the unique needs of startups and established enterprises alike. From conceptualization to execution, we offer comprehensive services including web and mobile app development, UI/UX design, and ongoing software maintenance. Ready to elevate your business? Contact CyanicLab today and let us propel your vision to success with our top-notch IT solutions.
Check out the webinar slides to learn more about how XfilesPro transforms Salesforce document management by leveraging its world-class applications. For more details, please connect with sales@xfilespro.com
If you want to watch the on-demand webinar, please click here: https://www.xfilespro.com/webinars/salesforce-document-management-2-0-smarter-faster-better/
Quarkus Hidden and Forbidden ExtensionsMax Andersen
Quarkus has a vast extension ecosystem and is known for its subsonic and subatomic feature set. Some of these features are not as well known, and some extensions are less talked about, but that does not make them less interesting - quite the opposite.
Come join this talk to see some tips and tricks for using Quarkus and some of the lesser known features, extensions and development techniques.
Modern design is crucial in today's digital environment, and this is especially true for SharePoint intranets. The design of these digital hubs is critical to user engagement and productivity enhancement. They are the cornerstone of internal collaboration and interaction within enterprises.
Large Language Models and the End of ProgrammingMatt Welsh
Talk by Matt Welsh at Craft Conference 2024 on the impact that Large Language Models will have on the future of software development. In this talk, I discuss the ways in which LLMs will impact the software industry, from replacing human software developers with AI, to replacing conventional software with models that perform reasoning, computation, and problem-solving.
Multiple Your Crypto Portfolio with the Innovative Features of Advanced Crypt...Hivelance Technology
Cryptocurrency trading bots are computer programs designed to automate buying, selling, and managing cryptocurrency transactions. These bots utilize advanced algorithms and machine learning techniques to analyze market data, identify trading opportunities, and execute trades on behalf of their users. By automating the decision-making process, crypto trading bots can react to market changes faster than human traders
Hivelance, a leading provider of cryptocurrency trading bot development services, stands out as the premier choice for crypto traders and developers. Hivelance boasts a team of seasoned cryptocurrency experts and software engineers who deeply understand the crypto market and the latest trends in automated trading, Hivelance leverages the latest technologies and tools in the industry, including advanced AI and machine learning algorithms, to create highly efficient and adaptable crypto trading bots
Globus Compute wth IRI Workflows - GlobusWorld 2024Globus
As part of the DOE Integrated Research Infrastructure (IRI) program, NERSC at Lawrence Berkeley National Lab and ALCF at Argonne National Lab are working closely with General Atomics on accelerating the computing requirements of the DIII-D experiment. As part of the work the team is investigating ways to speedup the time to solution for many different parts of the DIII-D workflow including how they run jobs on HPC systems. One of these routes is looking at Globus Compute as a way to replace the current method for managing tasks and we describe a brief proof of concept showing how Globus Compute could help to schedule jobs and be a tool to connect compute at different facilities.
Climate Science Flows: Enabling Petabyte-Scale Climate Analysis with the Eart...Globus
The Earth System Grid Federation (ESGF) is a global network of data servers that archives and distributes the planet’s largest collection of Earth system model output for thousands of climate and environmental scientists worldwide. Many of these petabyte-scale data archives are located in proximity to large high-performance computing (HPC) or cloud computing resources, but the primary workflow for data users consists of transferring data, and applying computations on a different system. As a part of the ESGF 2.0 US project (funded by the United States Department of Energy Office of Science), we developed pre-defined data workflows, which can be run on-demand, capable of applying many data reduction and data analysis to the large ESGF data archives, transferring only the resultant analysis (ex. visualizations, smaller data files). In this talk, we will showcase a few of these workflows, highlighting how Globus Flows can be used for petabyte-scale climate analysis.
Listen to the keynote address and hear about the latest developments from Rachana Ananthakrishnan and Ian Foster who review the updates to the Globus Platform and Service, and the relevance of Globus to the scientific community as an automation platform to accelerate scientific discovery.
Designing for Privacy in Amazon Web ServicesKrzysztofKkol1
Data privacy is one of the most critical issues that businesses face. This presentation shares insights on the principles and best practices for ensuring the resilience and security of your workload.
Drawing on a real-life project from the HR industry, the various challenges will be demonstrated: data protection, self-healing, business continuity, security, and transparency of data processing. This systematized approach allowed to create a secure AWS cloud infrastructure that not only met strict compliance rules but also exceeded the client's expectations.
OpenFOAM solver for Helmholtz equation, helmholtzFoam / helmholtzBubbleFoamtakuyayamamoto1800
In this slide, we show the simulation example and the way to compile this solver.
In this solver, the Helmholtz equation can be solved by helmholtzFoam. Also, the Helmholtz equation with uniformly dispersed bubbles can be simulated by helmholtzBubbleFoam.
Exploring Innovations in Data Repository Solutions - Insights from the U.S. G...Globus
The U.S. Geological Survey (USGS) has made substantial investments in meeting evolving scientific, technical, and policy driven demands on storing, managing, and delivering data. As these demands continue to grow in complexity and scale, the USGS must continue to explore innovative solutions to improve its management, curation, sharing, delivering, and preservation approaches for large-scale research data. Supporting these needs, the USGS has partnered with the University of Chicago-Globus to research and develop advanced repository components and workflows leveraging its current investment in Globus. The primary outcome of this partnership includes the development of a prototype enterprise repository, driven by USGS Data Release requirements, through exploration and implementation of the entire suite of the Globus platform offerings, including Globus Flow, Globus Auth, Globus Transfer, and Globus Search. This presentation will provide insights into this research partnership, introduce the unique requirements and challenges being addressed and provide relevant project progress.
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I ...Juraj Vysvader
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I didn't get rich from it but it did have 63K downloads (powered possible tens of thousands of websites).
Globus Connect Server Deep Dive - GlobusWorld 2024Globus
We explore the Globus Connect Server (GCS) architecture and experiment with advanced configuration options and use cases. This content is targeted at system administrators who are familiar with GCS and currently operate—or are planning to operate—broader deployments at their institution.
Platforms have to make reasonable time assumptions when judging health, if you’re not started, what are you?
How:
Complete in flight requests, reject new ones.
Design for failure, mark jobs as complete, in progress, aborted etc.
Transactions, NACK
Service selection and consumption is a big part, can they handle sudden failure?
Be quick about it, you’re on a clock.
Cloud Native, resiliency is big. Healer processes.
Transition: So how do we do that?
Blue Green For this deploy.
This example is mysql
This example is mysql
Its better to declare our dependencies with our code
The upside, you’re deploys fail faster if the service can’t be found.
So to recap how that all works:
Demo
Head not to disposability, as we do blue green.
https://github.com/cdavisafc/twelvefactorapp/compare/f11_logs...f4_backing_services?expand=1
We made a change to our app, lets take a person name, and save who we greet
Controller change
https://github.com/cdavisafc/twelvefactorapp/blob/f4_backing_services/src/main/java/hello/HelloController.java#L29-L30
Added some config to our app for mysql, flyway and cloud foundry connectors.
https://github.com/cdavisafc/twelvefactorapp/blob/f4_backing_services/build.gradle#L40-L46
Cloud Native & 12 Factor apps are designed for continuous deployment
Why?
Important to emphasize
Dev has env just like
Acceptance and prod
(i.e. McKenty rant)
Cloud Native & 12 Factor apps are designed for continuous deployment
Why?
Dev, Acceptance, Prod
The services we use in dev are the services we use in prod – no tool gap
The data we use in dev is derived from prod
We don’t spend any time messing around with data conversions, it’s the same because it’s the same.
If every commit is a canidate, we desire to know that it works in our target environment.
We deploy, the same way to all environments (cf push)
We deploy the same thing, to all environments (war, from artifactory)
If every change is a candidate, there's no time gap, deployments are simple with low overhead, we design and build for continuous deployment. This is an architecture, design and mindset shift.
We minimize the personnel gap.
Developers have the tools (and the responsibility) to deploy and monitoring in production
Ops have the tools and the knowledge to deploy
Of the factors to pay attention too… pragmatism counts. The purist implementation w/ java is harder than the pragmatic one. Don’t take on that complexity until you need it.
https://github.com/cdavisafc/twelvefactorapp/compare/f4_backing_services...f12_admin_processes