A software developer has argued that protocols should replace services in modern application architecture. The author contends that protocols offer superior flexibility and maintainability compared to traditional service-oriented approaches. This perspective challenges conventional wisdom in software engineering.

Protocols, as defined in this context, provide clear interfaces for communication between components without dictating implementation details. This contrasts with services, which often bundle functionality with specific implementations. The distinction matters because it affects how systems evolve over time.

By adopting protocols, developers can create more modular and testable code. This approach allows components to interact through well-defined contracts while remaining independent of each other's internal workings. The result is software that's easier to modify, extend, and debug. The argument for protocols over services represents a shift toward more composable and adaptable software design patterns.