Continuous Delivery with Content Management and UGC

•Transferir como PPTX, PDF•

3 gostaram•1,800 visualizações

Like salmon swimming upstream, user-generated content (UGC) and changes from content management systems (CMS) need to flow in the opposite direction to most software product changes. What strategies exist for reconciling the bidirectional flow (applications & features vs. content)? How can we bring upstream-moving content into our deployment pipeline, in which everything flows down towards Production?

Tecnologia Notícias e política

Continuous Delivery
with Content
Management
Systems (CMS) and
User-Generated
Content (UGC)

Matthew Skelton
23rd October 2013
#londoncd meetup group
@matthewpskelton

CMS and UGC
• Content Management System
– WordPress, Drupal, CQ5, Magnolia,
Sitecore, SharePoint (?!)

• User-Generated Content
– Reviews, photos, ratings

What‟s the Problem?
Much
contemporary
CMS-managed
content and UGC
is not simply static
but changes
application
functionality
Photo: Ingy the Wingy http://www.flickr.com/photos/ingythewingy/5740856803/

Made in Production ®
• Non-technical content authors
– New pages, widgets, workflow

• End users
– Graph connections, tagging

New Functionality
• Ideal: flow down new functionality
and behaviour from Dev
• Reality: CMS and UGC introduce
new behaviour and functionality
directly in Production

What do Humble & Farley
say?
“In most cases,
don‟t use dumps of
the production
dataset for testing
purposes. Create
custom datasets by
carefully selecting
a smaller subset of
production data”p.344
... but not much more than this

Example Strategies
1. Remove the Problem
– Avoid CMS
– Decouple UGC

2. Embrace the Problem
– Testing
– More testing

Remove the Problem
• Ditch the CMS
– Use plain HTML fragments + tooling
– Flow down the pipeline
– Package Management for
dependency graph

• Decouple UGC
– JavaScript client-side integration

Embrace the Problem
• Front-end tests in Production
– Use Staging?

• Identify new pages/features, extract,
bring back
– Track content with UUIDs

• Pre-live environment with data
regularly synched from Prod

Content Flow: „Upstream‟

Photo: Karen Miller, http://www.flickr.com/photos/tmtht/4029281127/

Other Approaches?
• Performance Testing?
– Data dumps

• „Content Platform‟?
– ETL approaches

• (No correct answers)

Matthew Skelton
@matthewpskelton

Discussion Time!

London Continuous Delivery
meetup group:
@londoncd
http://londoncd.org.uk/

Mais conteúdo relacionado

Semelhante a Continuous Delivery with Content Management and UGC

Bridging Current Reality & Future Vision with Reality Maps

Malini Rao

intelligraf by Ascalonic

Varghese Mathai

26 story slicing techniques for any scrum team

agilebin

[Public] between two worlds native&no-native experiences

Nicolas Bortolotti

Recommender Problems Introduction

Minh Nguyen

LvivCSS: Web Components as a foundation for Design System

Vlad Fedosov

Download this webinar for free: http://mstnr.me/2hPUamd Technology is one of five essential components of the digital story. Analytics provide us with vital information to track and measure audience behavior, so we can extend the reach and impact of our storytelling efforts across all of our communications channels. What do you measure, and how do you use that data to refine your story? Join us for this webinar to get your analytics game on! What You Will Learn • Learn about the most important metrics for digital stories, and how analytics relate to the four other essential components of a digital story. • Discover techniques for measuring those metrics on your sites and social media accounts, including testing different versions of content. • Gain a framework for analyzing information and making smart, data-driven decisions about content and design.

Analytics and Digital Storytelling

mStoner, Inc.

When Web Performance Optimization was emerging as a new field of engineering we had a handful of rules to follow. Gzip here, minify there, do some caching. This was 15 years ago. This year’s Smashing Magazine performance checklist has 62 items with hundreds of links for further research. Have we learned so much or has the Web become so complicated? In this talk I will try to make sense of today’s most pressing Web Performance issues with easily digestible lessons about metrics, budgets, JavaScript frameworks, functional programming, browsers and plain old HTML.

10 Web Performance Lessons For the 21st Century

Mateusz Kwasniewski

Web app with j query & javascript (5:4)

Thinkful

ACI Design and Creativity Day05 2015

R. Sosa

UserTesting 2016 webinar: Research to inform product design in Agile environm...

Steve Fadden

Speaker: Ori Bendet, Inbound Product Manager, HPE Software Today’s testers must test multiple aspects across a plethora of device permutations, in every network condition, while balancing quality with speed of delivery. But there’s no time to test everything. And so, we base our tests on hunches. But hunches can result in not testing key functionalities and/or environments that end up having a devastating effect on quality of the product. So what’s the answer? We need to switch from “gut feel” to evidence-based-testing, or simply put, adopt the practice of analytics to drive testing. Join the webinar to learn why and, how to start using analytics for testing your apps. Who is this for - Testers - DevTesters - Test managers - Developers - Project management - Product Owners - CIOs Key takeaways - What is one of the main problems in today’s testing teams - What are the risks? - Examples from our own experiences - How can you empower your testing by using Analytics You can view all our past webinars at: www.srijan.net/webinar/past-webinars

[Srijan Wednesday Webinars] Why Adopt Analytics Driven Testing

Srijan Technologies

Agile Testing and Test Automation

Naveen Kumar Singh

This session is about migration from a huge monolith to microservices. I will tell you about our experience, not theory. The session depicts prerequisites to start a monolith separation, problems I bumped and obstacles that were overcome. In my presentation I will shortly depict problems with the monolith, show appearance of business and framework modules separation, describe necessity of internal and external API, depict certification of libraries and microservices and touch other questions like branching/release strategies.

Migrate to microservices

Andrey Trubitsyn

Не один десяток раз каждый из нас видео этот пункт Agile манифеста. Кто на официальном сайте Agile Manifesto, кто в книгах или статьях, кто на тренингах или конференциях. Звучит правильно очевидно и просто, но на практике возникают некие сложности с его реализацией. Как определить какие документы писать нужно, а какие не стоит? Как поддерживать документы с наименьшими усилиями? От каких документов нужно отказаться или заменить на более простые решения? Что стоит документировать тестировщику, разработчику, бизнес-аналитику в Agile проектах, для того чтобы презентовать результаты своей работы. На все эти вопросы я постараюсь ответить в своем докладе, закрепляя примерами которые вы сможете попытаться применить на своих проектах.

Working Software Over Comprehensive Documentation

Andrii Dzynia

How Much Content Would Your Content Management System Manage If Your Content ...

John Eckman

Technical debt strategy

Masas Dani

DevOps - Keepers of the Keys to the Kingdom

DevOpsDays Tel Aviv

why agile?

Tathagat Varma

Lean startup

AgileOnTheBeach

Semelhante a Continuous Delivery with Content Management and UGC (20)

Bridging Current Reality & Future Vision with Reality Maps

intelligraf by Ascalonic

26 story slicing techniques for any scrum team

[Public] between two worlds native&no-native experiences

Recommender Problems Introduction

LvivCSS: Web Components as a foundation for Design System

Analytics and Digital Storytelling

10 Web Performance Lessons For the 21st Century

Web app with j query & javascript (5:4)

ACI Design and Creativity Day05 2015

UserTesting 2016 webinar: Research to inform product design in Agile environm...

[Srijan Wednesday Webinars] Why Adopt Analytics Driven Testing

Agile Testing and Test Automation

Migrate to microservices

Working Software Over Comprehensive Documentation

How Much Content Would Your Content Management System Manage If Your Content ...

Technical debt strategy

DevOps - Keepers of the Keys to the Kingdom

why agile?

Lean startup

Mais de Matthew Skelton

Find me on SpeakerDeck! - Matthew Skelton.pdf

Matthew Skelton

Organizations that do not adapt rapidly to the modern, highly-changeable business and technical environment are failing, and failing in large numbers. Increased regulation, pressures from climate change, shifting of energy sources, digitalization, cloud-native, and (recently) the COVID-19 pandemic are all driving a need for business and technical agility in organizations of all sizes. In this talk, we’ll explore how the patterns and principles from Team Topologies promote true business and technical agility through a rapid flow of software change, fast feedback from running systems, a strong drive for loose coupling, and an awareness of sociotechnical mirroring. Combined with a product mindset and techniques from Domain-driven Design, the Team Topologies approach is helping organizations around the world to adapt to the “new normal” and achieve true business and technical agility. From a talk at QCon Plus on 2021-05-26

Business and technical agility with Team Topologies - QCon Plus - 2021-05-26

Matthew Skelton

From a webinar on 29 April 2021 https://info.container-solutions.com/wtf-is-platform-as-product-2nd-edition Savvy organisations are discovering the value of treating their internal platforms as products. But what does it mean to treat a “platform as a product”? What benefits does this give, and why would an organisation adopt this approach? In this talk, [Matthew Skelton] [Manuel Pais], co-author of the book Team Topologies, explains why the platform-as-product approach can be a game-changer for organisations building and running software-enabled products and services. Using ideas & patterns from Team Topologies - including Thinnest Viable Platform, team cognitive load, and the evolutionary team interaction modes - [Matthew] [Manuel] explains how organisations like adidas and Uswitch have successfully used the platform-as-product model to accelerate and simplify the delivery of software at scale.

What is platform as a product? Clues from Team Topologies - WTFinar with Cont...

Matthew Skelton

Organizations that do not adapt rapidly to the modern, highly-changeable business environment are failing, and failing in large numbers. Increased regulation, pressures from climate change, shifting of energy sources, digitalization, and (recently) the COVID-19 pandemic are all driving a need for business agility in organizations of all sizes. In this talk, we’ll explore how the patterns and principles from Team Topologies promote true business agility through a rapid flow of software change, fast feedback from running systems, a strong drive for loose coupling, and an awareness of sociotechnical mirroring. Combined with a product mindset and techniques from Domain-driven Design, the Team Topologies approach is helping organizations around the world to adapt to the “new normal” and achieve true business agility. Matthew Skelton, co-author of Team Topologies, shares insights from organizations in several different industry sectors including banking, financial services, insurance, retail, and leisure.

Business agility with Team Topologies - NatWest Group - 2021-01-19

Matthew Skelton

From a WTFinar with Container Solutions on 2020-11-19 Savvy organisations are discovering the value of treating their internal platforms as products. But what does it mean to treat a “platform as a product”? What benefits does this give, and why would an organisation adopt this approach? In this talk, [Matthew Skelton] [Manuel Pais], co-author of the book Team Topologies, explains why the platform-as-product approach can be a game-changer for organisations building and running software-enabled products and services. Using ideas & patterns from Team Topologies - including Thinnest Viable Platform, team cognitive load, and the evolutionary team interaction modes - [Matthew] [Manuel] explains how organisations like adidas and Uswitch have successfully used the platform-as-product model to accelerate and simplify the delivery of software at scale.

WFT is platform as a product? Clues from Team Topologies - WTFinar with Conta...

Matthew Skelton

From a talk at Tech.Rocks 2020 For effective, modern, cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway’s Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes. This talk will cover the basics of organization design using Team Topologies, exploring a selection of key team types, and how and when to use them in order to make the development and operation of your software systems as effective as possible. The talk is based on the book Team Topologies by Matthew Skelton and Manuel Pais including first-hand experience helping companies around the world with the design of their technology teams. Key takeaways: 1. Why using the “Spotify Model” of team design is not enough 2. The four fundamental team topologies needed for modern software delivery 3. The three team interaction modes that enable fast flow and rapid learning 4. How to address Conway’s Law, cognitive load, and team evolution with Team Topologies

Beyond the Spotify Model - Team Topologies - Tech.rocks - 2020-12-10 - Matthe...

Matthew Skelton

Who designs the architecture of your software systems? Conway's Law suggests that HR may be strongly shaping software architecture by deciding how teams are composed and interrelate. Do you want HR designing your software architecture? Organization architecture and software system architecture need to be co-designed to avoid friction from Conway's Law. Based on ideas in the book Team Topologies, this talk by co-author Matthew Skelton explains how and why to bring together HR and Engineering to shape team boundaries and interactions for effective software delivery. From a talk at FlowCon 2020

Accidental Architects - how HR designs software systems - Team Topologies - f...

Matthew Skelton

Since the book Team Topologies was published in 2019, organizations around the world have started to adopt Team Topologies principles and practices like Stream-aligned teams, modern platforms, well-defined team interactions, and team cognitive load as a key driver for fast software delivery and operations. We will look at examples from these organizations: - Footasylum gives fashion-focused youth a multi-branded retail experience mixing global sportswear household names with emerging brands and its own stable of in-house labels. Founded in 2005, Footasylum now has 70 stores across the UK and a thriving ecommerce platform, with revenue of £260m per annum and over 2500 employees. Footasylum used Team Topologies patterns to revolutionize their ecommerce platform. - PureGym is Britain’s largest gym chain - the first to gain over 1 million members. As PureGym expanded, so did the need for software to enable their members to book and manage gym sessions. Since 2019, PureGym has re-aligned its teams and team interactions based on Team Topologies patterns, helping to scale the engineering teams and improve flow. - uSwitch / RVU, one of the UK’s leading consumer price comparison websites, has grown a modern platform from scratch, allowing stream-aligned teams to focus on consumers needs, offloading infrastructure provisioning concerns to the platform which also provides cross-cutting services around scalability, security and data management - Wealth Wizards is a UK company making financial advice affordable and accessible to everyone through online tools and apps. The engineering division at Wealth Wizards has used the Team Topologies ideas around team cognitive load to help right-size their teams and align teams to the most important flows of business change. For each of these examples, we explore how the ideas and patterns in Team Topologies were useful to the organization and the results of the changes.

Team Topologies in action - early results from industry - DOES Las Vegas 2020...

Matthew Skelton

Savvy organisations are discovering the value of treating their internal platforms as products. But what does it mean to treat a “platform as a product”? What benefits does this give, and why would an organisation adopt this approach? In this talk, [Matthew Skelton] [Manuel Pais], co-author of the book Team Topologies, explains why the platform-as-product approach can be a game-changer for organisations building and running software-enabled products and services. Using ideas & patterns from Team Topologies - including Thinnest Viable Platform, team cognitive load, and the evolutionary team interaction modes - [Matthew] [Manuel] explains how organisations like adidas and Uswitch have successfully used the platform-as-product model to accelerate and simplify the delivery of software at scale.

What is platform as a product? Clues from Team Topologies - Puppetize 2020 - ...

Matthew Skelton

From a talk at Iris Software Group in September 2020 We know that team-based software delivery can be very effective but how can we promote and enable team-based approaches for organisations that are fully remote? What should teams think about and what patterns can teams adopt to be effective when no-one is in the office? Based on the ideas from the book Team Topologies, authors Manuel Pais and Matthew Skelton will present some useful approaches to clarify and evolve inter-team interactions and communication in this remote-first world.

Remote first team interactions with Team Topologies - Iris Software Group - 2...

Matthew Skelton

A talk given at DevOps Enterprise Summit Virtual 2020 --- Since the book Team Topologies was published in 2019, organizations around the world have started to adopt Team Topologies principles and practices like Stream-aligned teams, modern platforms, well-defined team interactions, and team cognitive load as a key driver for fast software delivery and operations. We will look at examples from these organizations: * Gjensidige Insurance, a leading Nordic insurance company with 4000 employees and business in the Nordic and Baltic countries, uses the four fundamental team types to clarify team responsibilities and interactions and is moving towards several “thinnest viable platforms” with Stream-aligned teams as internal customers * PureGym is Britain’s largest gym chain - the first to gain over 1 million members. As PureGym expanded, so did the need for software to enable their members to book and manage gym sessions. Since 2019, PureGym has re-aligned its teams and team interactions based on Team Topologies patterns, helping to scale the engineering teams and improve flow. * uSwitch / RVU, one of the UK’s leading consumer price comparison websites, has grown a modern platform from scratch, allowing stream-aligned teams to focus on consumers needs, offloading infrastructure provisioning concerns to the platform which also provides cross-cutting services around scalability, security and data management * Visma is one of the leading software development companies in Europe with nearly 1 million customers in 21 countries. Team Topologies has helped to define and accelerate a transformation begun in 2015 to improve service ownership and speed of changes. * Wealth Wizards is a UK company making financial advice affordable and accessible to everyone through online tools and apps. The engineering division at Wealth Wizards has used the Team Topologies ideas around team cognitive load to help right-size their teams and align teams to the most important flows of business change. For each of these examples, we explore how the ideas and patterns in Team Topologies were useful to the organization and the results of the changes.

Team Topologies in action - early results from industry - DOES London Virtual...

Matthew Skelton

Accidental Architects - how HR designs software systems - Team Topologies - e...

Matthew Skelton

From an online meetup at SEAM with Matthew Skelton and Manuel Pais Remote-first work is the "new normal" for companies around the world. There is no shortage of advice on how individual teams can bond and work effectively remotely. However, there is not much on how to address remote interactions between different teams that need to collaborate remotely, as part of the same value stream. Moving from the physical to the online world can further expose pre-existing interaction problems, increase wait times and slow down delivery and possibly response to incidents. Based on the ideas from Team Topologies, Manuel Pais will present some useful approaches to clarify and evolve inter-team interactions and communication in this remote-first world. Designing Team APIs and virtual communication channels that promote relevant team interactions while minimizing communication overhead will help modern organizations keep a fast flow of delivery once they're past the initial adaptation to teleworking. Following well-defined interaction patterns and architecting for team-first software boundaries will also help reduce communication overhead, clarify expectations on teams, and increase visibility of on-going work and support.

Remote-first team interactions with Team Topologies - SEAM - 2020-05-13

Matthew Skelton

From a meetup run by Agile Yorkshire on 30 April 2020. Remote-first work is the "new normal" for companies around the world. There is no shortage of advice on how individual teams can bond and work effectively remotely. However, there is not much on how to address remote interactions between different teams that need to collaborate remotely, as part of the same value stream. Moving from the physical to the online world can further expose pre-existing interaction problems, increase wait times and slow down delivery and possibly response to incidents. Based on the ideas from Team Topologies, Manuel Pais and Matthew Skelton will present some useful approaches to clarify and evolve inter-team interactions and communication in this remote-first world. Designing Team APIs and virtual communication channels that promote relevant team interactions while minimizing communication overhead will help modern organizations keep a fast flow of delivery once they're past the initial adaptation to teleworking. Following well-defined interaction patterns and architecting for team-first software boundaries will also help reduce communication overhead, clarify expectations on teams, and increase visibility of on-going work and support.

Remote-first team interactions with Team Topologies - Agile Yorkshire - 2020-...

Matthew Skelton

From a webinar run by IT Revolution Press on 29 April 2020. Remote-first work is the "new normal" for companies around the world. There is no shortage of advice on how individual teams can bond and work effectively remotely. However, there is not much on how to address remote interactions between different teams that need to collaborate remotely, as part of the same value stream. Moving from the physical to the online world can further expose pre-existing interaction problems, increase wait times and slow down delivery and possibly response to incidents. Based on the ideas from Team Topologies, Manuel Pais and Matthew Skelton will present some useful approaches to clarify and evolve inter-team interactions and communication in this remote-first world. Designing Team APIs and virtual communication channels that promote relevant team interactions while minimizing communication overhead will help modern organizations keep a fast flow of delivery once they're past the initial adaptation to teleworking. Following well-defined interaction patterns and architecting for team-first software boundaries will also help reduce communication overhead, clarify expectations on teams, and increase visibility of on-going work and support.

Remote first team interactions with Team Topologies - IT Revolution webinar -...

Matthew Skelton

Remote-first work is the "new normal" for companies around the world. There is no shortage of advice on how individual teams can bond and work effectively remotely. However, there is not much on how to address remote interactions between different teams that need to collaborate remotely, as part of the same value stream. Moving from the physical to the online world can further expose pre-existing interaction problems, increase wait times and slow down delivery and possibly response to incidents. Based on the ideas from Team Topologies, Manuel Pais and Matthew Skelton will present some useful approaches to clarify and evolve inter-team interactions and communication in this remote-first world. Designing Team APIs and virtual communication channels that promote relevant team interactions while minimizing communication overhead will help modern organizations keep a fast flow of delivery once they're past the initial adaptation to teleworking. Following well-defined interaction patterns and architecting for team-first software boundaries will also help reduce communication overhead, clarify expectations on teams, and increase visibility of on-going work and support.

Remote-first team interactions with Team Topologies

Matthew Skelton

The “monoliths vs microservices” debate often focuses on technological aspects, ignoring strategy and team dynamics. Instead of technology, smart-thinking organizations are beginning with team cognitive load as the guiding principle for modern software. In this talk we explain how and why, based on material from the book Team Topologies by Matthew Skelton and Manuel Pais. From a talk at Dept Manchester sponsored by Commercetools https://www.deptagency.com/en-gb/event/architecting-the-modern-digital-experience/

Forget monoliths vs microservices - focus on Team Cognitive Load - Team Topol...

Matthew Skelton

How to break apart a monolithic system safely without destroying your team - ...

Matthew Skelton

From a talk at OIO15 The way in which many (most?) software teams use logging needs a re-think as we move into a world of microservices and remote sensors. Instead of using logging merely to dump out stack traces, our logs become a continuous trace of application state, with unique-enough identifiers for every interesting point of execution. We also use transaction identifiers to trace calls across components, services, and queues, so that we can reconstruct distributed calls after the fact. Logging becomes a rich source of insight for developers and operations people alike, as we 'listen to the logs' and tighten feedback cycles to improve our software systems.

Un-broken logging - the foundation of software operability - Operability.io -...

Matthew Skelton

Forget monoliths vs microservices - focus on team cognitive load - Team Topol...

Matthew Skelton

Mais de Matthew Skelton (20)