team organization

Architect's Guide

Feb 26, 2025 · Backend Development

Why Microservices Are More About Organizational Structure Than Pure Technology

The article critically examines the hype around microservices, arguing that their true value lies in promoting modularity, clear ownership, and organizational clarity rather than solving inherent technical problems, and it traces these ideas back to classic software engineering principles and modern operational challenges.

Microservicesdistributed systemsmodularity

0 likes · 22 min read

Why Microservices Are More About Organizational Structure Than Pure Technology

DevOps

Jun 16, 2024 · Operations

Performance Engineering Challenges and Practices for Software‑Defined Vehicles

The article examines how the shift to Software‑Defined Vehicles introduces complex performance engineering challenges across software, hardware, and organizational domains, and proposes an engineering‑driven, continuous‑observability approach—including modeling, monitoring, iterative optimization, and specialized team structures—to sustainably improve automotive software performance.

SDVautomotive softwareobservability

0 likes · 17 min read

Performance Engineering Challenges and Practices for Software‑Defined Vehicles

DeWu Technology

Apr 1, 2024 · R&D Management

Scaling Agile at DeWu: The Type‑P Framework and PMO Evolution

The article details how DeWu’s technology organization scaled from a few hundred to over a thousand engineers by adopting the custom Type‑P framework—emphasizing value‑orientation, small‑step rapid iteration, bi‑weekly sprints, unified domain‑level agile processes, metric‑driven governance, and an evolving PMO that shifted from throughput‑first to value‑first objectives.

Agile ScalingPMOmetrics

0 likes · 16 min read

Scaling Agile at DeWu: The Type‑P Framework and PMO Evolution

DevOps

Apr 24, 2023 · Backend Development

Hybrid “Big Waterfall + Small Agile” Delivery Model and Application Boundary Design in Large‑Scale Microservice Architecture

The article shares a chief architect’s experience designing a hybrid “big waterfall + small agile” delivery approach, microservice architecture, BFF layer, and team organization principles such as Conway’s law to address application boundary challenges in a massive state‑owned enterprise project.

ArchitectureBFFConway's law

0 likes · 11 min read

Hybrid “Big Waterfall + Small Agile” Delivery Model and Application Boundary Design in Large‑Scale Microservice Architecture

DevOps

Feb 13, 2023 · Backend Development

Hybrid “Big Waterfall + Small Agile” Delivery Model and Microservice Architecture Design Principles

The article shares a chief architect's experience on combining a large‑scale waterfall approach with agile iterations, detailing microservice and BFF design, team organization aligned with Conway's law, and practical application‑boundary principles for a distributed enterprise system.

BFFConway's lawMicroservices

0 likes · 11 min read

Hybrid “Big Waterfall + Small Agile” Delivery Model and Microservice Architecture Design Principles

Code Ape Tech Column

Jan 29, 2023 · Backend Development

Microservice Splitting Strategies: Expert Perspectives and Practical Guidelines

The article discusses various expert approaches to microservice decomposition, highlighting vertical and horizontal splits, business logic, stability, reliability, performance considerations, and team size implications, offering practical guidance for backend architects in design.

Microservicesbackend architectureservice decomposition

0 likes · 10 min read

Microservice Splitting Strategies: Expert Perspectives and Practical Guidelines

Architect

Jan 8, 2023 · Backend Development

Rethinking Microservices: From Hype to Core Architectural Principles

This article critically examines the microservices movement, tracing its historical roots, debunking common hype, and arguing that the true value lies in modular design, clear team ownership, and disciplined architectural practices rather than merely scaling distributed systems.

Microservicesdistributed systemsmodularity

0 likes · 23 min read

Rethinking Microservices: From Hype to Core Architectural Principles

IT Architects Alliance

Jul 15, 2021 · R&D Management

Feature Teams: Building Cross‑Functional, Long‑Lived Teams for Agile Development

The article explains how feature teams—cross‑functional, long‑lived groups that own end‑to‑end customer features—can improve user experience, technical excellence, and operational efficiency, while outlining the cultural and organizational changes required for successful adoption.

Agile Developmentcross-functionalfeature teams

0 likes · 7 min read

Feature Teams: Building Cross‑Functional, Long‑Lived Teams for Agile Development

DevOps

Mar 9, 2021 · R&D Management

Designing R&D Teams as Special Forces: Organizational Architecture for Agile Development

The article explains how adopting a "special forces" style organizational structure—small, cross‑functional squads with clear goals and boundaries—can improve R&D efficiency, adaptability to changing business needs, performance assessment, and career development within modern software companies.

DevOpsR&D managementSpecial Forces

0 likes · 7 min read

Designing R&D Teams as Special Forces: Organizational Architecture for Agile Development

Selected Java Interview Questions

Jan 14, 2021 · Backend Development

When to Merge Microservices Back into a Monolith: Balancing Technical and Organizational Concerns

The article argues that merging microservices back into a monolith can be justified when service boundaries no longer align with team structures, emphasizing that microservices address both technical load and people‑organization problems, and that the right size of a service depends on context rather than the misleading notion of "micro".

Conway's lawMicroservicesmonolith

0 likes · 11 min read

When to Merge Microservices Back into a Monolith: Balancing Technical and Organizational Concerns

Architect

Aug 17, 2020 · Backend Development

Various Approaches to Microservice Decomposition

The article examines microservice architecture as an abstract concept and presents three practical decomposition strategies—vertical/horizontal business split, business‑driven and team‑oriented considerations, and criteria based on logic, stability, reliability and performance—while also discussing cost, release frequency, and team size implications.

Microservicesbackend architectureservice decomposition

0 likes · 8 min read

Various Approaches to Microservice Decomposition

Efficient Ops

Apr 8, 2020 · R&D Management

Designing Autonomous Teams: Reduce Collaboration Overhead for End‑to‑End Ownership

The article explains how designing autonomous, end‑to‑end responsible teams—by minimizing inter‑team collaboration, adopting full‑process or cross‑functional squads, and leveraging automation tools—leads to better software architecture, aligns with Conway’s law, and improves efficiency in modern DevOps environments.

AutomationConway's lawDevOps

0 likes · 6 min read

Designing Autonomous Teams: Reduce Collaboration Overhead for End‑to‑End Ownership

Cloud Native Technology Community

Mar 18, 2020 · Backend Development

Microservice Splitting Strategies: Perspectives and Practices

The article explores various microservice decomposition approaches—vertical vs. horizontal, business‑driven, stability‑based, reliability‑focused, and performance‑oriented—highlighting trade‑offs, team size considerations, and practical guidelines for achieving scalable, maintainable service architectures.

Microservicesscalabilityservice decomposition

0 likes · 9 min read

Microservice Splitting Strategies: Perspectives and Practices

Architecture Digest

Mar 4, 2020 · Backend Development

Microservice Splitting Strategies: Three Approaches and Practical Considerations

This article examines microservice decomposition by presenting three expert‑derived splitting approaches—vertical/horizontal, business‑driven cost‑aware, and responsibility‑based—and discusses how factors such as team size, maintenance cost, scalability, stability, reliability and performance influence the optimal service boundaries.

Microservicesbackend architecturescalability

0 likes · 8 min read

Microservice Splitting Strategies: Three Approaches and Practical Considerations

Efficient Ops

Jun 27, 2017 · Big Data

How a Leading Bank Evolved Its Big Data Platform Architecture

This talk outlines how China’s Guangfa Bank built, refined, and scaled its big‑data platform since 2014, covering data positioning, system architecture optimization, delivery model improvements, team restructuring, and real‑world use cases that demonstrate the platform’s impact on risk control, marketing and operational efficiency.

Big DataContinuous DeliveryMicroservices

0 likes · 14 min read

How a Leading Bank Evolved Its Big Data Platform Architecture

Qunar Tech Salon

Jul 11, 2015 · Big Data

How Airbnb Scaled Its Data Science Team and Built a User‑Centric Data Culture

The article recounts Riley Newman's five‑year journey at Airbnb, describing how the data science team evolved from a small, centralized group to an embedded, cross‑functional partner that treats user behavior as data, democratizes insights, and drives product and business decisions at scale.

AirbnbBig DataUser‑Centric Data

0 likes · 10 min read

How Airbnb Scaled Its Data Science Team and Built a User‑Centric Data Culture

Qunar Tech Salon

May 13, 2015 · R&D Management

Facebook's Engineering Culture and R&D Management Practices

The talk explains Facebook's early engineering culture—emphasizing rapid "Hack" iterations, a decentralized organization that avoids dependencies, open code‑base ownership, data‑driven debate, and the strategic hiring of strong engineers—to illustrate how these practices drive high‑speed product development.

Engineering CultureFacebookHack

0 likes · 17 min read