This document discusses building cloud-aware applications. It defines key characteristics of cloud architecture like rapid elasticity, on-demand self-service, and resource pooling. It also discusses how to make applications cloud-aware by delivering them as stateless services, improving resiliency, and creating ecosystem platforms. Open source projects that can help deliver cloud awareness are also reviewed, like frameworks for parallel processing, distributed storage, and actor models.
Leveraging the unique benefits of the cloud requires a specialized approach to application architecture. The right design enables business agility, massive scaling, ability to burst, and high resiliency. Plus, it promotes resource efficiency and can minimize costs. If you are involved in providing applications or services in the cloud, attend this session to learn the principles of cloud-aware application design and to explore emerging architectural patterns which maximize cloud advantages.
The ability to deliver software is no longer a differentiator. In fact, it is a basic requirement for survival. Companies that embrace cloud native patterns of software delivery will survive; companies that don’t - will not.
In this webinar, we will:
- Look at the common patterns that distinguish cloud native companies and the architectures that they employ.
- Discover that an opinionated platform, one that stretches from the infrastructure all the way to the application framework, rather than ad-hoc automation, is an essential component to an enterprise's cloud native journey.
- Show that the combination of Pivotal Cloud Foundry and Spring is the complete cloud native platform.
Speaker:
Faiz Parkar
DIRECTOR OF PRODUCT MARKETING
As Director of Product Marketing for Pivotal in the Europe, Middle East and Africa region, Faiz Parkar loves working at the intersection of cloud native platforms, big data/analytics and agile application development to help organisations deliver compelling data-driven software experiences for their customers. With more than 25 years experience in the IT industry, Faiz has helped organisations large and small to take advantage of technology transitions from proprietary systems to client/server, from physical infrastructure to virtual, and from virtual infrastructure to cloud. His mission now is to help organisations accelerate their digital transformation journey and reinvent themselves as the digital leaders of the future.
The Application Server Platform of the Future - Container & Cloud Native and ...Lucas Jellema
New architecture patterns are rapidly influencing many organizations. The march to the cloud is taking place. DevOps and microservices for true agility and containers as vehicle for delivery, testing and management. During
Oracle OpenWorld 2017 - Oracle presented its vision and roadmap in the area of cloud native computing (which is based on container native) and announced its application server platform (container management runtime) of the future. This presentation summarizes that picture painted by Oracle.
This session introduces the key patterns in Cloud Native application development. It highlights the need of a unique architecture style, further, the fitment of DevOps, usage of Microservices and the runtime of Cloud Native application (* as a Service). The precautions of distributed computing gives insights of how to plan the application design and architecture.
What does being "cloud native" mean? In this session, presented at the Austin Microservices Meetup, I explore the four levels of the ODCA Cloud Application Maturity Model and discuss how microservices and containers can help transform applications.
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.
Pivotal Cloud Foundry: Cloud Native Architecture. A presentation by Adam Zwickey (Cloud Foundry) at Apigee's Adapt or Die, San Francisco 2016. See events.apigee.com
Cloud Native, Cloud First and Hybrid: How Different Organizations are Approac...Amazon Web Services
The implementation of highly scalable, easy-to-deploy technology is transforming the public sector, but it’s not a one-size-fits-all approach. Organizations begin their cloud adoption journeys in many ways. Some start with pilot projects and others jump into mission critical programs, but they are all starting with an existing infrastructure. Adopting cloud doesn’t mean scrapping it all and starting over. This session explores how organizations are using cloud while building on their existing technology and lessons they’ve learned along the way. Learn More: https://aws.amazon.com/government-education/
Leveraging the unique benefits of the cloud requires a specialized approach to application architecture. The right design enables business agility, massive scaling, ability to burst, and high resiliency. Plus, it promotes resource efficiency and can minimize costs. If you are involved in providing applications or services in the cloud, attend this session to learn the principles of cloud-aware application design and to explore emerging architectural patterns which maximize cloud advantages.
The ability to deliver software is no longer a differentiator. In fact, it is a basic requirement for survival. Companies that embrace cloud native patterns of software delivery will survive; companies that don’t - will not.
In this webinar, we will:
- Look at the common patterns that distinguish cloud native companies and the architectures that they employ.
- Discover that an opinionated platform, one that stretches from the infrastructure all the way to the application framework, rather than ad-hoc automation, is an essential component to an enterprise's cloud native journey.
- Show that the combination of Pivotal Cloud Foundry and Spring is the complete cloud native platform.
Speaker:
Faiz Parkar
DIRECTOR OF PRODUCT MARKETING
As Director of Product Marketing for Pivotal in the Europe, Middle East and Africa region, Faiz Parkar loves working at the intersection of cloud native platforms, big data/analytics and agile application development to help organisations deliver compelling data-driven software experiences for their customers. With more than 25 years experience in the IT industry, Faiz has helped organisations large and small to take advantage of technology transitions from proprietary systems to client/server, from physical infrastructure to virtual, and from virtual infrastructure to cloud. His mission now is to help organisations accelerate their digital transformation journey and reinvent themselves as the digital leaders of the future.
The Application Server Platform of the Future - Container & Cloud Native and ...Lucas Jellema
New architecture patterns are rapidly influencing many organizations. The march to the cloud is taking place. DevOps and microservices for true agility and containers as vehicle for delivery, testing and management. During
Oracle OpenWorld 2017 - Oracle presented its vision and roadmap in the area of cloud native computing (which is based on container native) and announced its application server platform (container management runtime) of the future. This presentation summarizes that picture painted by Oracle.
This session introduces the key patterns in Cloud Native application development. It highlights the need of a unique architecture style, further, the fitment of DevOps, usage of Microservices and the runtime of Cloud Native application (* as a Service). The precautions of distributed computing gives insights of how to plan the application design and architecture.
What does being "cloud native" mean? In this session, presented at the Austin Microservices Meetup, I explore the four levels of the ODCA Cloud Application Maturity Model and discuss how microservices and containers can help transform applications.
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.
Pivotal Cloud Foundry: Cloud Native Architecture. A presentation by Adam Zwickey (Cloud Foundry) at Apigee's Adapt or Die, San Francisco 2016. See events.apigee.com
Cloud Native, Cloud First and Hybrid: How Different Organizations are Approac...Amazon Web Services
The implementation of highly scalable, easy-to-deploy technology is transforming the public sector, but it’s not a one-size-fits-all approach. Organizations begin their cloud adoption journeys in many ways. Some start with pilot projects and others jump into mission critical programs, but they are all starting with an existing infrastructure. Adopting cloud doesn’t mean scrapping it all and starting over. This session explores how organizations are using cloud while building on their existing technology and lessons they’ve learned along the way. Learn More: https://aws.amazon.com/government-education/
Where SOA and Monolitch EAR have failed. It's not simple to have your Apps scaling automagically without a very complex architecture. We're going to show pros and cons of so called Cloud-Native Applications based on Microservices, Caas, DevOps, Continuous Delivery....
Review this AWS and Nimbo webinar where we discuss moving your data center to the AWS Cloud. We feature a real world example to illustrate how this can be achieved both quickly and smoothly.
Hess Corporation recently moved part of its infrastructure to the cloud, to prepare for a business divestiture. Relying on consultation from enterprise cloud solution provider Nimbo, the migration was completed securely, in about half the time it would have taken in an on-premises environment.
This topic introduces the need of a unique architecture style for Cloud Native application deployments. Further, the fitment of DevOps, usage of Microservices and the runtime of Cloud Native application (* as a Service) are covered in detail. The need of distributed computing in Cloud for Cloud Native applications is trivial to understand. Insights on the same are covered.
Using cloud native development to achieve digital transformationUni Systems S.M.S.A.
Avishay Sebban, Partner Senior Solution Architect at Red Hat IGC, gives the comprehensive idea behind Red Hat Ansible platform, the full automation capabilities and the smooth deployment to cloud. From Cloud Migration Through Automation: Next Level Flexibility virtual event, hosted on September 30, 2020
Monitoring the Cloud – Understanding the Dynamic Nature of Cloud Computing - ...Amazon Web Services
Applications running in a typical data center are static entities. The same is not true in the cloud. Dynamic scaling and resource allocation is the norm in AWS. Technologies such as EC2, Lambda, and AutoScaling make tracking resources and resource utilization a challenge. The days of static server monitoring are over.
In this session, we examine trends we've discovered in dynamic resource allocation and how AWS helps deliver those trends. We will discuss some of the best practices we've learned working with New Relic customers on how you can manage applications running in this environment and take advantage of the dynamic nature of the cloud to give you additional insights into your application performance.
Speaker: Lee Atchison, Principal Cloud Architect and Advocate, New Relic
http://stiller.co.il/blog/2014/01/upcoming-event-from-alm-to-devops/
How do companies like Microsoft, Twitter, Facebook and LinkedIn achieve high levels of execution which allow implementing hundreds and even thousands of lines of code every day, while maintaining a high & consistent level of performance, security and availability? How can the development and operation environments work together to create a meaningful competitive edge for the organization?
In an era where time-to-market and product quality have a critical meaning, the DevOps methodology offers simple and effective ways to shorten schedules, improve the product quality and maintain a competitive edge.
In this presentation, which is part of the "From ALM to DevOps" day, I explain and demonstrate the principles of DevOps in Windows Azure. Also demonstrated is the possible synchronization between Team Foundation Server (TFS) and Microsoft System Center (SCOM),
Innovating with AWS: How Microservices on AWS Can Transform Your BusinessAmazon Web Services
Rehan Qureshi
Canada Practice Manager, AWS Professional Services, explains the concept of Microservices built on the AWS cloud, and how they can completely transform a customer's IT business. Microservices goes beyond DevOps, and into serverless solutions such as AWS Lambda. This is a high level overview of microservices architectures.
Ensuring Cloud Native Success: Organization TransformationChloe Jackson
Are you being asked to put more cloud in your strategy? If you’re like most people, the answer is a definite yes. The word “cloud” can mean so many things, however, that making an actionable strategy is impossible. At Pivotal, we divide cloud into two distinct parts: migrating as many legacy applications into SaaS as possible and focusing on perfecting the software you build in-house that runs your business. Gartner is predicting that by 2020, 75% of applications used to support digital businesses will be built in-house. If you’re one of these companies, you’ll need to quickly evaluate how you develop and run your custom written software.
We believe that soon, every company will either be a software company or losing to a competitor who is. It’s time to focus on the craft of managing the software development life-cycle, and this brief, but dense webinar will help launch your efforts to become a software defined business.
Join us in the last installment in our series: Organization Transformation - to get the full benefit of a cloud native approach, you'll likely need to change how your organization functions and behaves: you'll have to change its culture. When software is thought of more as ongoing products instead of discrete projects, the way the IT department is managed and run changes accordingly. This last part covers the motivations for those changes and outlines how to start transforming everyday management, strategy, staffing, and operations to become a cloud native enterprise.
Presenter: Michael Coté
Large-Scale Enterprise Platform Transformation with Microservices, DevOps, an...VMware Tanzu
SpringOne Platform 2016
Speakers: Christopher Tretina; Director, Comcast & Vipul Savjani; Director of PaaS, Accenture
Comcast is embarking on a multi-year application modernization and transformation journey to achieve application resiliency, velocity and cost optimization at enterprise scale. We will discuss how we are addressing significant technical architecture, engineering, and delivery challenges faced in transformation of Comcast’s Enterprise Services Platform (ESP) from SOA architecture to Cloud-Native architecture using Microservices, DevOps, and PaaS.
Building A Diverse Geo-Architecture For Cloud Native Applications In One DayVMware Tanzu
Presenter: Ben Laplanche, Product Manager, Pivotal Cloud Foundry
Companies turn to PaaS and Cloud Native Applications to gain agility and speed. To provide customer value, a fault tolerant infrastructure is essential. But what happens if an entire data center, region, or even country should go offline? Cassandra holds the key to keeping application state in sync through replication, whilst Pivotal Cloud Foundry provides easy deployment to multiple IaaS providers. It also comes complete with a managed service offering for DataStax Enterprise. This talk will discuss how this setup can be deployed in one day, including demonstrations and a walkthrough of the key concepts, approaches, and considerations.
Chris Munns, DevOps @ Amazon: Microservices, 2 Pizza Teams, & 50 Million Depl...TriNimbus
Keynote presentation from Vancouver's 2016 Canadian Executive DevOps & Cloud Summit on Thursday, May 5th.
Speaker: Chris Munns, Business Development Manager, DevOps at Amazon Web Services
Title: DevOps @ Amazon: Microservices, 2 Pizza Teams, & 50 Million Deploys a Year
Cloud Migration, Application Modernization, and Security Tom Laszewski
As AWS continues to expand, enterprise customers are looking to our partner ecosystem to assist in migrating their workloads to the cloud. This session describes the challenges, lessons learned and best practices for large scale application migrations. We will use real examples from our consulting partners and AWS Professional Services to illustrate how to move workloads to the cloud while modernizing the associated applications to take advantage of AWS’ unique benefits. We will also dive into how to use an array of AWS services and features to improve a customer’s security posture as they are migrating and once they are up and running in the cloud
How Discovery Migrated 80% of Their IT to AWS with CloudreachAmazon Web Services
While the advantages of operating your workloads on AWS are attractive to many organizations, the prospect of migrating a vast legacy IT environment to the cloud may have your IT department wondering where to start. When Discovery Communications, a mass media and entertainment company, decided to migrate 20 data centers to AWS they selected Cloudreach as their trusted advisor on their journey to the cloud. Cloudreach uses a mature methodology with its roots in industry best practices and the AWS Cloud Adoption Framework to efficiently migrate large on-premises environments to the cloud. Join us for the upcoming webinar where cloud experts from Cloudreach, AWS, and Discovery discuss how Cloudreach helped Discovery Communications transform and modernize their IT infrastructure and adopt the AWS Cloud.
Join us to learn:
How Discovery Communications migrated 80% of their corporate IT environment to AWS.
Cloudreach’s repeatable structure and methodology behind migrating large-scale workloads to AWS.
How Cloudreach ensures the business goals of the migration (e.g., TCO/ROI, speed of deployment, team focus, etc.) are achieved, if not surpassed.
Who Should Attend:
CIO, CTO, VP or SVP Infrastructure, IT Director, Chief Architect
Where SOA and Monolitch EAR have failed. It's not simple to have your Apps scaling automagically without a very complex architecture. We're going to show pros and cons of so called Cloud-Native Applications based on Microservices, Caas, DevOps, Continuous Delivery....
Review this AWS and Nimbo webinar where we discuss moving your data center to the AWS Cloud. We feature a real world example to illustrate how this can be achieved both quickly and smoothly.
Hess Corporation recently moved part of its infrastructure to the cloud, to prepare for a business divestiture. Relying on consultation from enterprise cloud solution provider Nimbo, the migration was completed securely, in about half the time it would have taken in an on-premises environment.
This topic introduces the need of a unique architecture style for Cloud Native application deployments. Further, the fitment of DevOps, usage of Microservices and the runtime of Cloud Native application (* as a Service) are covered in detail. The need of distributed computing in Cloud for Cloud Native applications is trivial to understand. Insights on the same are covered.
Using cloud native development to achieve digital transformationUni Systems S.M.S.A.
Avishay Sebban, Partner Senior Solution Architect at Red Hat IGC, gives the comprehensive idea behind Red Hat Ansible platform, the full automation capabilities and the smooth deployment to cloud. From Cloud Migration Through Automation: Next Level Flexibility virtual event, hosted on September 30, 2020
Monitoring the Cloud – Understanding the Dynamic Nature of Cloud Computing - ...Amazon Web Services
Applications running in a typical data center are static entities. The same is not true in the cloud. Dynamic scaling and resource allocation is the norm in AWS. Technologies such as EC2, Lambda, and AutoScaling make tracking resources and resource utilization a challenge. The days of static server monitoring are over.
In this session, we examine trends we've discovered in dynamic resource allocation and how AWS helps deliver those trends. We will discuss some of the best practices we've learned working with New Relic customers on how you can manage applications running in this environment and take advantage of the dynamic nature of the cloud to give you additional insights into your application performance.
Speaker: Lee Atchison, Principal Cloud Architect and Advocate, New Relic
http://stiller.co.il/blog/2014/01/upcoming-event-from-alm-to-devops/
How do companies like Microsoft, Twitter, Facebook and LinkedIn achieve high levels of execution which allow implementing hundreds and even thousands of lines of code every day, while maintaining a high & consistent level of performance, security and availability? How can the development and operation environments work together to create a meaningful competitive edge for the organization?
In an era where time-to-market and product quality have a critical meaning, the DevOps methodology offers simple and effective ways to shorten schedules, improve the product quality and maintain a competitive edge.
In this presentation, which is part of the "From ALM to DevOps" day, I explain and demonstrate the principles of DevOps in Windows Azure. Also demonstrated is the possible synchronization between Team Foundation Server (TFS) and Microsoft System Center (SCOM),
Innovating with AWS: How Microservices on AWS Can Transform Your BusinessAmazon Web Services
Rehan Qureshi
Canada Practice Manager, AWS Professional Services, explains the concept of Microservices built on the AWS cloud, and how they can completely transform a customer's IT business. Microservices goes beyond DevOps, and into serverless solutions such as AWS Lambda. This is a high level overview of microservices architectures.
Ensuring Cloud Native Success: Organization TransformationChloe Jackson
Are you being asked to put more cloud in your strategy? If you’re like most people, the answer is a definite yes. The word “cloud” can mean so many things, however, that making an actionable strategy is impossible. At Pivotal, we divide cloud into two distinct parts: migrating as many legacy applications into SaaS as possible and focusing on perfecting the software you build in-house that runs your business. Gartner is predicting that by 2020, 75% of applications used to support digital businesses will be built in-house. If you’re one of these companies, you’ll need to quickly evaluate how you develop and run your custom written software.
We believe that soon, every company will either be a software company or losing to a competitor who is. It’s time to focus on the craft of managing the software development life-cycle, and this brief, but dense webinar will help launch your efforts to become a software defined business.
Join us in the last installment in our series: Organization Transformation - to get the full benefit of a cloud native approach, you'll likely need to change how your organization functions and behaves: you'll have to change its culture. When software is thought of more as ongoing products instead of discrete projects, the way the IT department is managed and run changes accordingly. This last part covers the motivations for those changes and outlines how to start transforming everyday management, strategy, staffing, and operations to become a cloud native enterprise.
Presenter: Michael Coté
Large-Scale Enterprise Platform Transformation with Microservices, DevOps, an...VMware Tanzu
SpringOne Platform 2016
Speakers: Christopher Tretina; Director, Comcast & Vipul Savjani; Director of PaaS, Accenture
Comcast is embarking on a multi-year application modernization and transformation journey to achieve application resiliency, velocity and cost optimization at enterprise scale. We will discuss how we are addressing significant technical architecture, engineering, and delivery challenges faced in transformation of Comcast’s Enterprise Services Platform (ESP) from SOA architecture to Cloud-Native architecture using Microservices, DevOps, and PaaS.
Building A Diverse Geo-Architecture For Cloud Native Applications In One DayVMware Tanzu
Presenter: Ben Laplanche, Product Manager, Pivotal Cloud Foundry
Companies turn to PaaS and Cloud Native Applications to gain agility and speed. To provide customer value, a fault tolerant infrastructure is essential. But what happens if an entire data center, region, or even country should go offline? Cassandra holds the key to keeping application state in sync through replication, whilst Pivotal Cloud Foundry provides easy deployment to multiple IaaS providers. It also comes complete with a managed service offering for DataStax Enterprise. This talk will discuss how this setup can be deployed in one day, including demonstrations and a walkthrough of the key concepts, approaches, and considerations.
Chris Munns, DevOps @ Amazon: Microservices, 2 Pizza Teams, & 50 Million Depl...TriNimbus
Keynote presentation from Vancouver's 2016 Canadian Executive DevOps & Cloud Summit on Thursday, May 5th.
Speaker: Chris Munns, Business Development Manager, DevOps at Amazon Web Services
Title: DevOps @ Amazon: Microservices, 2 Pizza Teams, & 50 Million Deploys a Year
Cloud Migration, Application Modernization, and Security Tom Laszewski
As AWS continues to expand, enterprise customers are looking to our partner ecosystem to assist in migrating their workloads to the cloud. This session describes the challenges, lessons learned and best practices for large scale application migrations. We will use real examples from our consulting partners and AWS Professional Services to illustrate how to move workloads to the cloud while modernizing the associated applications to take advantage of AWS’ unique benefits. We will also dive into how to use an array of AWS services and features to improve a customer’s security posture as they are migrating and once they are up and running in the cloud
How Discovery Migrated 80% of Their IT to AWS with CloudreachAmazon Web Services
While the advantages of operating your workloads on AWS are attractive to many organizations, the prospect of migrating a vast legacy IT environment to the cloud may have your IT department wondering where to start. When Discovery Communications, a mass media and entertainment company, decided to migrate 20 data centers to AWS they selected Cloudreach as their trusted advisor on their journey to the cloud. Cloudreach uses a mature methodology with its roots in industry best practices and the AWS Cloud Adoption Framework to efficiently migrate large on-premises environments to the cloud. Join us for the upcoming webinar where cloud experts from Cloudreach, AWS, and Discovery discuss how Cloudreach helped Discovery Communications transform and modernize their IT infrastructure and adopt the AWS Cloud.
Join us to learn:
How Discovery Communications migrated 80% of their corporate IT environment to AWS.
Cloudreach’s repeatable structure and methodology behind migrating large-scale workloads to AWS.
How Cloudreach ensures the business goals of the migration (e.g., TCO/ROI, speed of deployment, team focus, etc.) are achieved, if not surpassed.
Who Should Attend:
CIO, CTO, VP or SVP Infrastructure, IT Director, Chief Architect
ServiceMesh's Dave Roberts presented, originally at Cloud Connect 2012, Santa Clara CA
Applications are the heart of enterprise IT. Everything that IT does is focused on delivering new functionality through applications. Unfortunately, for most enterprises, the application delivery process is tremendously inefficient, leading outcomes where more application development projects are canceled than are completed.
Making of a Successful Cloud Business:
Current Status & Future Requirements
Rajarshi Bhose and Sumit Kumar Bose
Infosys Technologies Limited
Delivered as part of Cloud symposium, at ACM Bangalore COmpute 2009.
What integration, service, or API infrastructure components are appropriate for my platform?
Should teams Decouple at Edge or Center?
Why incorporate API Gateways, Enterprise Service Bus (ESB), or integration frameworks into your platform and architecture?
Eight Miles High: Build Cloud-native and Cloud-aware SystemsChris Haddad
Achieve development agility, improve run-time application resiliency, and deliver highly-responsive applications by adopting cloud-native design patterns and building cloud-aware applications. Forklifting applications into the cloud is relatively fast, but the simple path into the cloud does not create better software. End-users may still complain about your development velocity, operations may still struggle to maintain uptime guarantees, and development iterations may continue at a glacial pace. By iteratively applying cloud-native design patterns and re-architecting applications, teams reduce technical debt, deploy with confidence, and build highly scalable solutions. Cloud-aware applications embrace microservices, actor model interactions, map-reduce processing, shared-nothing architecture, and the thirteen dwarf patterns. Learn about cloud-native design practices and frameworks that help you optimize scalability, foster anti-fragility, and decompose application monoliths into cloud-native microservices. Chris describes how Kubernetes, Akka, Hadoop, Eureka, Hysterix, and other open source projects make cloud-native design and implementation an approachable proposition.
Cloaking Devices, CyberPersonas, and Neutral ZonesChris Haddad
When every endpoint is under constant attack, and all traffic is being parsed and analyzed, how can we safeguard confidential information, freely interact, and express our digital persona without concern? Chris will describe why privacy must not be breached; why anonymity can engender hostility, and what mindset is leading us into cyberwar zones instead of cybertrade neutral zones.
Traditional static middleware servers do not fit a cloud-native, micro service model. Rapid container provisioning, software defined networking, and scaling policies now demand spinning up discrete infrastructure services on demand. Chris will present a next generation integration and application hosting environment that will free DevOps from expensive static deployments and glacial refresh cycles. He will describe:
* Why traditional middleware servers must evolve into dynamic infrastructure services
* What Cloud-native, microservices friendly architectural design patterns force teams to rethink integration and application hosting platforms
* What reference architecture ensures successful microservices projects
* How teams can establish DevOps workflows that support on-demand infrastructure services
Bring N-Tier Apps to containers 2015 ContainerConChris Haddad
Containerization is moving from lab work to production application projects. Teams desire to achieve deployment agility, application resilience, and resource optimization. While container cookbooks show simple scenarios, containerizing production N-tier applications requires complex considerations. Chris describes how teams select complementary open source projects (i.e. Docker Compose, Apache Mesos, Mesos Marathon, Google Kubernetes, Apache Stratos) and craft an open source platform that shifts legacy applications away from virtual machines and into containers. He demonstrates how teams effectively manage container dependencies, independently scale container tiers, and deliver quality of service. From a developer’s perspective, Chris will show micro-service architecture patterns guiding teams towards application packaging strategies and container lifecycle decisions
Overcome DevOps Adoption Barriers to Accelerate Software DeliveryChris Haddad
Overcome DevOps Adoption Barriers to Accelerate Software Delivery
Many organizations want to create systems delivered in a DevOps framework with diverse services implemented via API building blocks.
Chris Haddad says that people, processes, and tools often hinder a team's ability to comply with security policies, streamline collaboration, and rapidly deliver business value.
Chris recommends moving design, development, and continuous delivery into a cloud Platform as a Service (PaaS) environment.
PaaS helps organizations and teams more readily adopt DevOps practices, integrate governance compliance frameworks, and follow agile methodologies with distributed teams.
Find out how to change your software culture by employing an environment and tooling that promote collaboration, rapid iterations, and painless compliance.
Chris describes the tools you need and a step-by-step approach for developing robust and secure software within a DevOps framework.
Discover how merging DevOps activities, polyglot PaaS capabilities, and governance practices overcome organizational barriers, create better software, and accelerate software delivery.
Recommended Reading
DevOps Meets ALM in the Cloud
WSO2 App Factory Product Page
Teams can extend business reach, enhance customer intimacy, and increase revenue opportunities by tracking who is accessing their API. Chris will describe how linking Identity as a Service (IDaaS), identity bridges, API gateways, and API analytics can help teams realize API economy goals. In this session, you will learn:
Why analytics linking identity with API access will drive business value?
What best practices efficiently bridge front-end identity with back-end legacy authorization?
Deploy at scale with CoreOS Kubernetes and Apache StratosChris Haddad
Platform-as-a-Service (PaaS) streamlines DevOps and allows developers to focus on application development. The PaaS handles provisioning, scaling, high availability, and tenancy.
Integration with the Docker platform, CoreOS Linux distribution, and Kubernetes container management system bring more scalability and flexibility to a PaaS. This session will include installing and deploying sample applications using Docker,CoreOS and Kubernetes, and a walkthrough on how it can be extended to support new application containers.
Merging microservices architecture with SOA practicesChris Haddad
Microservice architecture promises to pragmatically overcome service development hurdles by using a single responsibility pattern (SRP) and full-stack development teams. Do we now throw out SOA and integration practices? In this session, Chris Haddad will describe how you can rapidly build systems by adapting SOA practices, extending your DevOps toolchest, and defining microservices. You will learn:
How to properly define, decouple, and size a microservice.
What DevOps practices overcome microservice deployment roadblocks
When microservices create fragile instead of antifragile building blocks
Connected Architecture Fabric Creating a Connected WorldChris Haddad
In-memory contextual processing, API Clouds, and Industrial Things are driving digital transformation and connecting the world.
In this session, Chris will describe how leading IT teams incorporate new reference architecture components and practices that enhance connections across people, devices, and partners.
In this session, you will learn:
Why new business and customer expectations demand a connected business
What new connected architecture fabric components create strategic business opportunity
How leading IT teams incorporate new components and practices
Establishing SOA Focused Enterprise ArchitectureChris Haddad
Enterprise architecture frameworks (i.e. TOGAF) define data, application, technology, and business domains. Where do services, APIs , and streams fit into the blueprint? Teams can enhance architectural integrity and coherence by establishing a SOA-focused and API-centric foundation for their architecture efforts. In this presentation, Chris will describe key Enterprise Architecture patterns and practices that accelerate project delivery and create a SOA-focused architecture. During this session, you will learn:
Why SOA-focused Enterprise Architecture and API-centric approaches accelerate project delivery and increase
What patterns and practices help overcome common SOA and Enterprise Architecture challenges
How to fit project-oriented service development into an Enterprise Architecture picture
Apache Stratos is a highly-extensible Platform-as-a-Service (PaaS) framework that helps run Apache Tomcat, PHP, and MySQL applications. The PaaS environment can be extended to support any additional language, framework, or server. For developers, Stratos provides a cloud-based environment for developing, testing, and running scalable applications. IT providers benefit from high utilization rates, automated resource management, and platform-wide insights, including monitoring and billing.
In this session, we will discuss key features in Apache Stratos and choosing the right solution for your business needs.
Topics to be covered:
True community ecosystem
Open extensible architecture
True flexibility for custom services and infrastructure
Multi-factored auto scaling
Multi-tenancy
Scalable dynamic load balancing
Capability of controlling PaaS resources
Logging, metering and monitoring
Cloud bursting
Teams building successful APIs focus on six tactical best practices areas to gain widespread developer community adoption, increase operational resiliency, accelerate API delivery, and seamlessly evolve API design as business requirements change. In this session, learn how to make tactical design decisions that expand your internal and external API community, reliably connect back-end Cloud services, rapidly publish data as APIs, secure API interactions, and synchronize lifecycle activities. Chris and Sumedha will build a few live APIs in the Cloud. The APIs will demonstrate design patterns, implementation decisions, and API environments (cloud and on-premise) that allow you to tailor your API based on target ecosystem and business model.
Gaining Startup Speed with DevOps PaaSChris Haddad
In today’s hyper-competitive environment, successful teams cloud source business capabilities and nimbly connect ecosystem participants across cloud environments. Infrastructure, processes, and team collaboration models must adapt. Chris Haddad will describe how innovative WSO2 clients are gaining startup speed, reducing project risk, and enabling new business models by adopting DevOps PaaS.
Enabling cloud-native, complex enterprise development and deployment in the C...Chris Haddad
Forklifting terrestrial middleware into the cloud provides incremental benefits. Revolutionize project delivery, build a responsive IT, and operate at the speed of business.
SOA and API Convergence Strategy and TacticsChris Haddad
APIs encourage connected business interactions that lead to increased revenue growth, faster time to market, and increased customer engagement. When attempting to reconcile agile API tactics with enterprise SOA guidelines, teams tune governance practices and integrate API development with back-end service life-cycles.
In this session, Chris Haddad VP - Platform Evangelism at WSO2 will describe:
Why SOA services and RESTful APIs are complementary
What architecture patterns and governance techniques align API and service development lifecycles
How to converge SOA and API strategies and implement tactics that accelerate connected business projects
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...SOFTTECHHUB
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
Dr. Sean Tan, Head of Data Science, Changi Airport Group
Discover how Changi Airport Group (CAG) leverages graph technologies and generative AI to revolutionize their search capabilities. This session delves into the unique search needs of CAG’s diverse passengers and customers, showcasing how graph data structures enhance the accuracy and relevance of AI-generated search results, mitigating the risk of “hallucinations” and improving the overall customer journey.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
Communications Mining Series - Zero to Hero - Session 1DianaGray10
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024Neo4j
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
1. Building Applications On
Cloud Architecture
Chris Haddad
@cobiacomm chris@wso2.com
Read more about Cloud Architecture and Cloud-aware Apps at
http://blog.cobia.net/cobiacomm
12. Building Apps on Cloud Architecture
•Why cloud aware applications rise above Web
applications
•Where to make applications cloud aware
•What open source projects deliver cloud
awareness
13. Rise Above:
Cloud Scale and Distributed Providers
Business
Functional Proces
Presentation and Business
Mashups Role Process
Presentation Functional Business
Role Role Process
Business
Presentation and Functional
Role Process and
Mashups Functional Business Rules
Presentation and
Mashups code
Client Tier
Resource
Integration Services Tier
Resource
Services
Resource
Services
Integration Services
Public Cloud Services
Private
Applications
14. Rise Above:
Application Resiliency and Composition
Composite Mobile
Infrastructure as a
Application Application Service (IaaS)
SaaS Application
Cloud
API Web
Endpoint application
Endpoint
Integration Services
Business Service Portfolio Application Portfolio
Hybrid
Presentation Services
Platform
Business
Process and
Functional Services
Services
Rules Services
Resources Services
Integration Services
15. Rise Above:
Deliver Cross-Partner Digital Business Platform
Vertical Application 1 Vertical Application 2 Vertical Application 3
App Data App Data App Data
Summit
Vertical
App Source Code App Source Code App Source Code
App App App
Configuration Configuration Configuration
Vertical
API
Domain Services Domain Services
Domain Artifacts Domain Artifacts
Managed
Programming Languages
by PaaS
Frameworks
Containers
OS/Hypervisor
Hardware
16. Where to make applications Cloud Aware
• Deliver application to massive consumer base
• Infrastructure cost optimization strategy
• Application resiliency improvement strategy
• Create an ecosystem platform supporting cross-partner
digital business
17. Cloud Aware Architecture
• Maximize utilization and optimize cost
– Requires deterministic performance
– Load balance based on tenant, service, and workload, context
– Increase tenant density
• Increase reliability, availability, scalability
– Shared nothing architecture
– Stateless server-side elements
– Consensus protocols
– Services distributed across multiple providers and zones
• Ecosystem platform
– Monetize assets based on business value
– Tenant/Consumer personalization and isolation
– Sharing domain specific business capabilities
18. Architectural Difference Between Web
Application and Cloud Application
Web Application Cloud Application
• Synchronous request-reply • Asynchronous interaction
interaction • Queues and workers
• Centralized state (i.e. single • Scale out across datacenters
database) and session and providers
management • Distributed state and session
• Clustered server instances management
• Silo architecture • Autonomous service instances
• Tenant context personalization
• Shared JVM / Shared Schema
• Shared nothing architecture
19. Cloud Application Patterns
and Anti-Patterns 18
Separation of concerns
Failure Resilient Leaky interfaces
Tightly coupled
Single threaded, modules
serial execution
Embarrassingly Parallel /
Minimal Shared Nothing Architecture Deterministic
Consumption performance
Resource locks Monolithic footprint Single tenancy model
Deploy and execute on optimum topology
20. Cloud Architecture Best Practices
Transitioning to a New normal – Traditional practices may
not apply
• Distributed and federated interactions
– Event based, heterogeneous systems, network latency
• Configurable containers and engines
– Declarative data, rules, and process definitions
• De-normalized and simplified data models
– Hadoop/BigTable, Hypertext media, simple NoSQL entities
• Expect failure
– Systems span transactional control
• Applications decomposed into distinct services
– Federated environment drives autonomy, statelessness, and
composition
24. Cloud aware architecture model shift
New interaction model
• Actor Model
– Dispatching and scheduling instead of direct invocation
– Queues and asynchronous interactions
• RESTful interactions
– Message passing instead of function calls or shared
memory
• Eventual consistency instead of ACID
– Distributed cache instead of application cluster
– Cache access instead of direct resource access
• Traditional O/R mapping (e.g. Hibernate) doesn’t work
24
25. Cloud-aware Design Patterns
Cloud-aware Application
Parallelizable,
Shared nothing
Multi-tenant Application Platform Services
Asynchronous,
stateless services
Fine grained, ESB
modular design
Tenant
Application Server
PaaS Framework
personalization Business Process
Registry Asset
Efficient resource Load Metering and
Controller Deployer and Repositories
consumption Identity Management balancer Billing
Synchronizer
Deterministic Storage
performance
26. Simplification Through Patterns
Relevant pattern categories
• Computational fit analysis
• Parallelism and workload decomposition
• Concurrency
• State
• Structural
• Scale
26
27. Apply Computational Patterns
Evaluate 13 Dwarfs
1. Dense linear algebra – matrix calculations
2. Sparse linear algebra – sparse matrix calculations and storage
3. Spectral methods – operational engineering
4. N-body methods – particle force calculations
5. Structured grids – mechanical and fluid engineering, meteorology
6. Unstructured grids – mechanical and fluid engineering
7. Mapreduce – Monte Carlo simulations, data processing
8. Combinational logic – data transformation
9. Graph traversal – social networking
10. Dynamic programming – DNA pattern matching, web search, shipping
11. back-track / branch & bound - travel route mapping
12. graphical model reference – speech and image recognition
13. finite state machines – workflow optimization
27
28. Cloud-awareness
Programming Model
• Actor model (i.e. message passing instead of function
invocation
• RESTful interactions
• Dynamic recoverability
• Consensus protocols
• Asynchronous rather than synchronous interactions
• Shared nothing architecture
• Data partitioning and sharding
• Federated data queries
• Service orchestration
• Functional programming
• MapReduce
29. Open Source Projects
• Cloud aware Infrastructure
– WSO2 Stratos
– Cloud Foundry
– Red Hat OpenShift
• Frameworks
– Parallel Process Execution and Coordination
– Distributed Map-Reduce
– Distributed Storage for Large Scale Structured Data (aka Big
Table / Big Data)
– Grid Frameworks
– Distributed Object and Tuple Spaced Data Cache
– REST Frameworks
– Actor model
• Languages
– Functional, Parallel, Actor Model
30. Cloud-optimized Frameworks
Scaffolding to structure Cloud aware app development
• Parallel Process Execution and Coordination
• Distributed Map-Reduce
• Apache Hadoop, Apache MapReduce, StarFish MapReduce
• Distributed Storage for Large Scale Structured Data
(aka Big Table / Big Data)
• Apache Cassandra, Apache Hbase, Neptune, Hypertable
• Grid Frameworks
• Distributed Object and Tuple Spaced Data Cache
– memcache
• REST Frameworks
• Actor model
30
31. Cloud-optimized Frameworks
Scaffolding to structure Cloud application development
• Parallel Process Execution and Coordination
– .NET 4 Task Parallel Library, Apache Zookeeper
• Distributed Map-Reduce
– Apache Hadoop, Apache MapReduce, StarFish MapReduce
• Distributed Storage for Large Scale Structured Data (aka Big Table / Big
Data)
– Apache Cassandra, Apache Hbase, Neptune, Hypertable
• Grid Frameworks
– Globus, Condor, DataSynapse
• Distributed Object and Tuple Spaced Data Cache
– Oracle Coherence, Terracotta Ehcache, Spring GemStone, memcache,
GigaSpaces XAP
• REST Frameworks
– Restlet, .NET WCF, DJango
• Actor model
– Akka, Jetlang, Actors Guild, Actor Foundry,
31
32. Programming Languages
Cloud-ready languages are emerging and maturing
• Functional Languages
– Haskell
– Occam
– F#
– Clojure
• Actor Model Alignment
– Erlang
– Scala
• Parallel Computation and Data Processing
– Skywrite
– Pig
– BOOM
32
33. Building Cloud-awareness
Focus on adopting Cloud-friendly Architecture
• Tenancy, dynamic discovery, and distributed cache
• Fine-grained metering, billing, and reporting of
business entities, activities, and interactions
• Scale discrete application service instances instead of
scaling monolithic application instances
• Shared nothing architecture, Thirteen Dwarf
Patterns, parallel processing, resource coordination
• Cloud service provisioning and load balancer
34. Resources
• Try StratosLive right now:
– https://stratoslive.wso2.com/
• Read about Stratos:
– http://wso2.com/cloud/stratos/
– Source Download available
• White Paper
– Selecting Platform as a Service
– Platform as a Service TCO: multi-tenant shared container
• Blog Articles
– What is Platform as a Service?
– PaaS Evaluation Framework for CIOs and Architects
– How to simplify Platform as a Service Complexity
– Searching for Cloud Reference Architecture
• Contact us:
– bizdev@wso2.com
Is the 15-year-old web application architecture still relevant, or is new Cloud-aware application architecture emerging? While many teams forklift web applications into the Cloud, scale-out leaders are building for failure, high availability, elasticity, and operational efficiency. In this presentation, Chris Haddad describes how new components, patterns, and frameworks are redefining application architecture.
Skating towards puckhttp://www.webstockpro.com/UpperCut-RF/tre02014.Ice-hockey-player-skating-Photo/
To maximize business benefit, PaaS offerings should significantly exhibit essential Cloud characteristics. The NIST Draft – Cloud Computing Synopsis and Recommendations defines Cloud characteristics as:• On-demand self-service• Broad network access• Resource pooling• Rapid elasticity• Measured serviceMeasured service or pay per useThe first Cloud characteristic, measured service, enables pay-as-you-go consumption models and user subscription to metered services. Usage is monitored, and the system generates bills based on charging model. To close the perception gap between business end-users and IT teams, the Cloud solution should bill for business value or business metrics instead of billing for IT resources. Business end-users do not easily correlate business value with an invoice for CPU time, network I/O, or data storage bytes. In contrast, business focused IT teams communicate value and charges based on number of users, processed forms, received marketing pieces, or sales transactions. A cloud native PaaS supports monitoring, metering, and billing based on business oriented entities. Rapid ElasticityA stateful monolithic application server cluster connected to a relational database does not efficiently scale with rapid elastically. Dynamic discoverability and rapid provisioning can instantiate processing and message nodes across a flexible and distributed topology. Applications exposing stateless services (or where state is transparently cached and available to instances) will seamlessly expand and contract to execute on available resources. A cloud native PaaS will interoperate with cloud management components to coordinate spinning up and tearing down instances based on user, message, and business transaction load in addition to raw infrastructure load (i.e. CPU and memory utilization).Resource PoolingDevelopment and operation teams are familiar with resource pooling. Platform environments commonly pool memory, code libraries, database connections, and resource bundles for use across multiple requests or application instances. But because hardware isolation has traditionally been required to enforce quality of service and security, hardware resource utilization has traditionally been extremely low (~5-15%). While virtualization is often used to increase application-machine density and raise machine utilization, virtualization efforts often result in only (~50-60%) utilization. With PaaS level multi-tenancy, deterministic performance, and application container level isolation, an organization could possible shrink it’s hardware footprint by half. Sophisticated PaaS environments allocate resources and limit usage based on policy and context. The environment may limit usage by throttling messages, time slicing resource execution, or queuing demand. Integration and SOA run-time infrastructure supports the resource sharing and interoperability required to deliver effective resource pools. As teams start to pool resources beyond a single Cloud environment, integration is required to merge disparate identities, entitlements, policies, and resource models. As teams start to deliver application capabilities as Cloud services, a policy aware SOA run-time infrastructure pools service instances, manages service instance lifecycle, and mediates access.On-demand self-serviceOn-demand self-service requires infrastructure automation to flexibly assign workloads and decrease provisioning periods. If teams excessively customize an environment, they will increase time to market, lower resource pooling, and create a complex environment, which is difficult to manage and maintain. Users should predominantly subscribe to standard platform service offerings, and your team should minimize exceptions.
This evaluation criteria measures how widely the solution can be shared (i.e. private, public, community), who is responsible for PaaS environment management (i.e. internal, external), and where the PaaS is located (i.e. on-premise, outsourced) options. Before selecting PaaS infrastructure, understand how sharing, location, and responsibility impact your decision. Public, private, or community attributes specify how widely the cloud service is shared; a sharing dimension. Internal or external denote the consumer's view of the Cloud's service interface. The view is associated with a consumer's responsibility for service development, operations, and management; a responsibility dimension. A third dimension, on-premise or outsourced, describes where the service assets are located; a location dimension. A hybrid cloud strategy delivers, spans, and connects clouds across all dimension attributes. Your organization and team will often be confronted with delivering, connecting, and spanning solutions across diverse private and public Cloud environments. Your Platform as a Service architecture and platform service offering should provide a holistic hybrid environment consistently applying governance and policies across internal and external Clouds. Hybrid cloud use cases require interoperability, federation, SOA principles, and infrastructure services to bridge Cloud environments into a unified platform. PaaS offerings score high (10) when they can run within all dimension coordinates, and score low (1) when they only run within a subset of the dimensions. For more information on Cloud dimensions, view Chris’ blog post.
Platform as a Service resides within the space between Software as a Service (SaaS) and Infrastructure as a Service (IaaS). IaaS delivers basic network, storage, and compute- processing capabilities as standardized, scalable service offerings. Example IaaS offerings include Amazon EC2/S3, Windows Azure VM Role, and RackSpace Cloud Servers). Software as a Service delivers business software capabilities (e.g. expense reporting, logistics, benefits enrollment) and information feeds as online web applications and web services. Pioneered in the early 2000’s, SaaS was used to by independent software vendors to efficiently deliver an application without requiring on-premise installation, remote updates, and cost prohibitive instance management. Platform as a Service is application middleware offered as a service to developers, integrators, and architects.Infrastructure as a Service offers development team a bare-bones infrastructure environment, which requires adding middleware, application frameworks, and infrastructure services (i.e. identity, entitlement, application logging). IaaS encapsulates hardware complexity and applies operational best practices. Operation teams create IaaS Clouds by applying virtualization, automation, and standardization to hardware provisioning and allocation tasks. As teams look to apply provisioning and automation to the application platform, interest in DevOps has grown.The DevOps movement creates a collaborative environment bridging development and operation team members. DevOps enables team members to jointly design, build, and deploy business application and service solutions. The environment closes the gap between business requirements, policies, available run- time resources, and solution development.Development and operation teams use Platform as a Service to design, build, and deliver customized applications or information services. Instead of relying on standardized SaaS, teams using PaaS have more control over solution architecture, quality of service, user experience, data models, identity, integration, and business logic. PaaS offerings often support DevOp practices, which include self-service, automated provisioning, continuous integration, and continuous delivery.Figure 1 illustrates the Platform as a Service space, which incorporates IaaS DevOps practices and increases solution customization options. IaaS could be considered an unfinished house requiring appliances, cabinetry, and fixtures. At the other spectrum extreme, SaaS offers a fully furnished dwelling with little customization. Even if purple dotted lime décor is not your personal style, a SaaS may require you to sit on the purple dotted lime green couch. Alternatively, a PaaS offers a finished house with an array of personalized furniture choices. Because the industry broadly defines PaaS as the level above hardware infrastructure and below business applications, development teams do not commonly have clear comparison criteria to intelligently evaluate frameworks or determine adoption benefits. At a minimum, PaaS offerings differ from traditional application platforms by shielding teams from direct infrastructure ownership, management, and complexity. Figure 1. Relationship between Platform as a Service and other Cloud service layers
Taken from Gartner
Architects are interested in delivering measurable business value, shielding IT personnel from complex dependencies, and deliver a productive development and operations (i.e. DevOps) environment. The following PaaS capabilities are used to achieve these objectives:DevOps ToolingAutomated GovernanceService Level ManagementConsumption based pricing “Cloud consumers of PaaS can employ the tools and execution resources provided by cloud providers to develop, test, deploy and manage the applications hosted in a cloud environment. PaaS consumers can be application developers who design and implement application software, application testers who run and test applications in cloud-based environments, application deployers who publish applications into the cloud, and application administrators who configure and monitor application performance on a platform. PaaS consumers can be billed according to, processing, database storage and network resources consumed by the PaaS application, and the duration of the platform usage.”Source: http://collaborate.nist.gov/twiki-cloud-computing/pub/CloudComputing/ReferenceArchitectureTaxonomy/NIST_SP_500-292_-_090611.pdf“For PaaS, the Cloud Provider manages the computing infrastructure for the platform and runs the cloud software that provides the components of the platform, such as runtime software execution stack, databases, and other middleware components. The PaaS Cloud Provider typically also supports the development, deployment and management process of the PaaS Cloud Consumer by providing tools such as integrated development environments (IDEs), development version of cloud software, software development kits (SDKs), deployment and management tools. The PaaS Cloud Consumer has control over the applications and possibly some the hosting environment settings, but has no or limited access to the infrastructure underlying the platform such as network, servers, operating systems (OS), or storage.”Source: http://collaborate.nist.gov/twiki-cloud-computing/pub/CloudComputing/ReferenceArchitectureTaxonomy/NIST_SP_500-292_-_090611.pdf
Some solution architects find Cloud characteristics and supporting PaaS attributes too abstract and infrastructure focused. Architects may be more interested in delivering measurable business value, shielding IT personnel from complex dependencies, and deliver a productive development and operations (i.e. DevOps) environment. The following PaaS capabilities (See Figure 4) are used to achieve these objectives:DevOps ToolingAutomated GovernanceService Level ManagementConsumption based pricing Figure 4: Platform as a Service (PaaS) Capabilities and supporting practices DevOps ToolingDevOps tooling creates an environment fostering collaboration between development and operations team members. Practice and tooling enable teams to implement self-service configuration, automated provisioning, policy configuration, and process automation practices which bridge the design, build, deploy, and manage phases within the software development life-cycle. By integrating DevOps tooling with on-demand resource instances, teams can reduce time to market and increase agility. Automated GovernanceGovernance is a practice, which defines policies, people, and processes. Effective governance mitigates risks, improves performance, and facilitates correct actions. Automated governance enables application and infrastructure services to efficiently scale across numerous consumers and providers while effectively monetizing, maintaining, and securing assets and consumer-provider interactions. By publishing a service catalogue offering tiered levels of service, teams can promote standard offerings that meet customer requirements. By streamlining access and approval, automated governance encourages customers to choose standard offerings and reduce cost. Scaling a Cloud environment while right-sizing available capacity is non-trivial, and the infrastructure must support demand management and capacity management activities. When organizations move beyond their first Cloud service release, automated lifecycle management becomes a predominant concern. To effectively manage the service lifecycle, the infrastructure must report on service versions, subscribed consumers, and usage trends. In the run-time environment, an infrastructure authority component makes resource allocation decisions, which are enforced by service level management components. Service Level ManagementService level management enforces governance policies. PaaS infrastructure should integrate service level management activities throughout the solution stack (i.e. network, processing, storage, managed code container, application platform engines, and application logic). Resource monitoring, resource management, performance management, and traffic orchestration must monitor, manage, and optimize machine node instances, message routing, application service location, tenant security, and session state. Intelligent service level management on Cloud native PaaS infrastructure has the ability to raise infrastructure utilization while maintaining quality of service. Consumption Based PricingToday, cloud consumption based pricing reflects IT asset monetization (e.g. machine instance per hour, network I/O, storage bytes). However, business users don’t really care how many instances are running in the Cloud. Business users care about business entities, business activity performance, and associated cost. Table 1 below illustrates various pricing units. For example, the number of market leads generated by a marketing piece, or cost to process an insurance policy. Decoupling metering and billing from IT assets and shifting the reporting model to focus on business activity and holistic IT cost will positively change the IT investment conversation. Coupling multi-tenant metering and billing with business activity monitoring and reporting will facilitate the shift. “Cloud consumers of PaaS can employ the tools and execution resources provided by cloud providers to develop, test, deploy and manage the applications hosted in a cloud environment. PaaS consumers can be application developers who design and implement application software, application testers who run and test applications in cloud-based environments, application deployers who publish applications into the cloud, and application administrators who configure and monitor application performance on a platform. PaaS consumers can be billed according to, processing, database storage and network resources consumed by the PaaS application, and the duration of the platform usage.”Source: http://collaborate.nist.gov/twiki-cloud-computing/pub/CloudComputing/ReferenceArchitectureTaxonomy/NIST_SP_500-292_-_090611.pdf“For PaaS, the Cloud Provider manages the computing infrastructure for the platform and runs the cloud software that provides the components of the platform, such as runtime software execution stack, databases, and other middleware components. The PaaS Cloud Provider typically also supports the development, deployment and management process of the PaaS Cloud Consumer by providing tools such as integrated development environments (IDEs), development version of cloud software, software development kits (SDKs), deployment and management tools. The PaaS Cloud Consumer has control over the applications and possibly some the hosting environment settings, but has no or limited access to the infrastructure underlying the platform such as network, servers, operating systems (OS), or storage.”Source: http://collaborate.nist.gov/twiki-cloud-computing/pub/CloudComputing/ReferenceArchitectureTaxonomy/NIST_SP_500-292_-_090611.pdf
Cloud computing, PaaS, and DevOps tooling is an opportunity to raise infrastructure abstraction. Figure 5 demonstrates the continuum from hardware infrastructure to business entities. DevOps tooling integrated with PaaS should shield developers from hardware infrastructure concerns and expose business entities. While Cloud washed PaaS does often facilitates hardware infrastructure configuration, enables rapid infrastructure installation, and delivers machine level access to Cloud machines, the Cloud washed PaaS environment does not shield development team members from hardware infrastructure complexity. Development team members must still be experts in machine sizing, Java Virtual Machine (JVM) configuration, and network topologies. Some PaaS environments do hide hardware infrastructure concerns and instead expose application platform entities. Application developers can work with familiar application platform entities (i.e. .war files, application frameworks, application sessions), easily install applications on the Cloud, and configure application instances. Cloud environment exposing application platform entities will deliver a familiar application development model and provide the team with a high level of control. With both the hardware infrastructure and application platform abstraction levels, teams can often forklift existing applications into the Cloud with few modifications. The migrated applications will run in the Cloud, but will not be purpose-built for the Cloud. If Cloud benefits are derived by delivering capabilities ‘as a service’, business entities should be exposed, composed, connected, consumed, and orchestrated as services. A business entity perspective is required to decompose applications and flexibly distribute the entities across Cloud nodes. PaaS environments exposing APIs, services, and communication channels deliver application building blocks at an appropriate abstraction level. Multi-tenancy is extended inside the application, and tenancy can be applied to users, workspaces, and transactions.
A Platform as a Service offering should promote deploying applications onto a flexible, distributed topology. To maximize Cloud characteristics, a PaaS should facilitate scaling way out (e.g. across cloud zones, data centers) and automatically distribute fine-grained service component resources. Figure 6 presents a logical view of a cloud application executing across a distributed topology. The Integration Services PaaS service component is used to connect application service components and external cloud services by message passing, not function invocation. Integration services commonly include a Enterprise Service Bus (ESB), service governance registry, service gateways, and message brokers. Figure 6: Cloudy Topology
As an application platform in the Cloud, PaaS should facilitate Cloud characteristics (i.e. elastic scale, on-demand self service, resource pooling, and consumption based pricing). While all middleware vendors purport to deliver a platform product or service powering the Cloud, all PaaS offerings do not deliver appropriate granularity, abstraction, capabilities, simplicity, and solution breadth. When attempting to achieve Cloud characteristics, development teams often specify the following goals Ensure an application satisfies consumer demand while maximizing resource utilizationScale workload processing and increase performance while minimizing infrastructure spendAllocate, provision, monitor, manage, and administer resources and policies across multiple tenants, nodes, and locationsRapidly deploy application and service components on a preferred topology that meets deterministic performance requirements (e.g., replication, utilization, latency, bandwidth, and coherency)To achieve these goals, PaaS offerings can be evaluated and compared across the following criteria categories:Cloud CharacteristicsMeasures characteristics (i.e. on-demand self-service, resource pooling, rapid elasticity, and measured service) used to distinguish Cloud solutions from traditional application solutions. Cloud DimensionsMeasures how widely the solution can be shared (i.e. private, public, community), who is responsible for PaaS environment management (i.e. internal, external), and where the PaaS is located (i.e. on-premise, outsourced) optionsProduction ReadyMeasures PaaS maturity and suitability for enterprise, mission critical level useDevOps Activities and Lifecycle PhasesMeasures how to design, construct, deploy, and manage applications and services using DevOps practices (i.e. continuous integration, continuous delivery, automated release management, and incremental testing)Cloud ArchitectureMeasures architecture principles, concepts, and patterns enabling applications to dynamically execute parallel workloads across a highly distributed environmentPlatform ServicesMeasures how completely the PaaS satisfies development of complex applications by providing comprehensive application middleware components and servicesProgramming ModelMeasures programming languages and frameworks, which facilitates building applications and services exhibiting Cloud characteristics
Building Cloud optimized applications is difficult, but frameworks, languages, and patterns help guide our work.Cloud Application Patterns can be divided into six main categories:Computational fit analysis: How toanalyze problem domain and apply appropriate pattern to distribute workloadDecomposition: how do we divide the work?Concurrency: How do we ensure coordination and synchronization?State: how do we ensure safe process and data state manipulation in a distributed or parallel environment?Structural: How do we decouple business logic and applications from topology?Scale: How do we scale run-time application execution?
Most parallel programs can be reduced to a small set of concurrent patterns: For example, the 13 dwarf from David Patterson“A dwarf is a class of algorithms that tend to have a common pattern of communication and computation”Two dwarf patterns are currently popular, MapReduce, and Graph traversal.MapReduce is being used to process distributed dataGraph traversal is en vogue due to high interest in building social networking applications.If you develop applications for complex business domains, for example stock trade analysis, DNA pattern matching, meteorological predictions, or travel route mapping, a few more of these patterns may be familiar to you. http://view.eecs.berkeley.edu/wiki/Dwarfs Most parallel programs can be reduced to a small set of concurrent patterns: 13 dwarf from David Patterson“A dwarf is a class of algorithms that tend to have a common pattern of communication and computation”“Roles of Dwarfs1. Give us a vocabulary/organization to talk across disciplinary boundaries2. Define minimum set of necessary functionality for new hardware/software systems3. Define building blocks for creating libraries that cut across application domains4. “Anti-benchmarks” not tied to code or language artifacts ⇒ encourage innovation in algorithms, languages, data structures, and/or hardware5. They decouple research, allowing analysis of HW & SW programming support without waiting years for full app development“
The programming model category measures programming languages and frameworks, which facilitates building applications and services exhibiting Cloud characteristics. The Cloud programming model is fundamentally different from the web programming model which fueled Java EE’s popularity. To maximize cloud benefits, development teams must adopt new programming models, architecture patterns, and frameworks. The actor model, service composition, RESTful interactions, policy injection, and tenant aware frameworks extend Java into the Cloud. A Cloud programming model facilitates building applications and services, which exhibit Cloud characteristics. The programming model should be congruent with Cloud architecture principles and patterns. Example detailed criteria include:Actor model (i.e. message passing instead of function invocationRESTful interactionsDynamic recoverabilityConsensus protocolsAsynchronous rather than synchronous interactionsShared nothing architectureData partitioning and shardingFederated data queriesService orchestrationFunctional programmingMapReduce PaaS offerings score high (10) when the programming model explicitly supports parallel processing, distributed interactions, shared nothing architecture, workload decomposition, and hide infrastructure complexity. PaaS offerings score low (1) when they expose data center infrastructure concepts (i.e. machines, storage parameters, network addresses) and do not elastically scale beyond traditional application server clusters.
This category measures architecture principles, concepts, and patterns enabling applications to dynamically execute parallel workloads across a highly distributed environment. The PaaS architecture model should shield application developers, integrators, and architects from infrastructure, natively support cloud characteristics, and exhibit Cloudy architectural attributes (i.e. tenancy, dynamic discovery). Cloud architectural attributes should span the entire solution stack, and not be constrained to components below the application server. The Cloud Architecture criteria category measures conformance with architecture principles enabling:Measured service or pay per useEvaluate the PaaS solution for fine-grained metering, billing, and reporting of business entities, activities, and interactions. For example, can the PaaS meter the number of workspaces created, users added, or business transactions executed? Rapid elasticityMature PaaS offerings scale discrete application service instances rather than scaling monolithic application instances. An ability to rapidly provision small footprint services based on user demand will increase application density and infrastructure utilization. PaaS offerings should exhibit rapid service provisioning, flexible resource allocation, and distributed topologies. Implicit support for shared nothing architecture and the Thirteen Dwarf patterns (e.g. MapReduce) enables application decomposition, parallel processing, and resource coordination. On-demand self-serviceMature PaaS offerings do more than push application bits to a Cloud node. Mature PaaS offerings perform flexible, run-time workload assignment and automated startup of standard service offerings. Cloud architecture components include a Cloud controller, Cloud service provisioning, and Cloud load balancer. Resource PoolingMature PaaS offerings supply shared everything containers to hosted applications. Multi-tenancy is incorporated throughout the solution stack (i.e. network, processing, storage, managed code container, application platform engines, frameworks, and application logic). Resource utilization is tracked by business transaction or business entity access, and resource allocation conforms to well-defined policies. Distributed caches are used to share resources across entitled tenants while enforcing security. PaaS offerings score high (10) when they deliver enhanced capabilities at high abstraction and fine granularity. PaaS offerings score low (1) when they do not extend capabilities beyond levels offered by traditional application platform infrastructure.