New York

October 15–17, 2025

Berlin

November 3–4, 2025

Search results

Module Archive
Session 1: Developing your team | LeadDev Together
Article
Mapping the immovable objects in engineering projects
Accepting what you can't change and changing what you can
Article
What linguistics can teach us about building software with distributed teams
Identifying structures in our software systems that are open to (mis)interpretation
Contributor
Andrew Hao
Article
Learnings from ‘Weighing up the pros and cons of build vs. buy’
A snapshot of the series
Video
Universal Apps: Architecture for the Modern Web
"In today's web environment, performance and Search Engine Optimization (SEO) are important to successful apps. Universal architecture provides a hybrid approach to building web apps that combines server-side rendered applications and Single-Page Applications (SPA). This architectural approach improves the user experience and makes it easier for your site to serve content to search and social bots. This talk will explain the methodology and benefits of the universal approach. It will explore some of the tradeoffs and challenges that come with universal architecture. Finally, we will cover the various implementation options available today. At the end of this talk, you'll be able to evaluate if universal architecture is a good choice for your projects."
Video
Traps on the Path to Microservices
After Netflix helped popularize microservices, you probably heard the architectural pattern labelled a boon. However, if your team is tasked with implementing the pattern it is too easy to find yourself in a place where you've significantly increased your architectural complexity without deriving any of the benefits that microservices purport to bring, especially if implemented without proper organizational maturity or careful foresight and follow-through. ThoughtWorks has led many teams and organizations along the path from monoliths to microservices and this presentation covers three of the major traps that we’ve experienced (as well as how to avoid them). The traps covered are, underestimating the cost of a microservice, overcentralization, and neglecting the monolith
Video
Traps on the Path to Microservices
After Netflix helped popularize microservices, you probably heard the architectural pattern labelled a boon. However, if your team is tasked with implementing the pattern it is too easy to find yourself in a place where you've significantly increased your architectural complexity without deriving any of the benefits that microservices purport to bring, especially if implemented without proper organizational maturity or careful foresight and follow-through. ThoughtWorks has led many teams and organizations along the path from monoliths to microservices and this presentation covers three of the major traps that we’ve experienced (as well as how to avoid them). The traps covered are, underestimating the cost of a microservice, overcentralization, and neglecting the monolith
Contributor
Elyse Kolker Gordon
Contributor
George Woskob