The Minds Behind Webhooks – 7 People Redefining Software
Seven builders helped turn user-defined HTTP callbacks into webhooks, making event-driven integration a normal part of APIs, developer tools, SaaS automation, and continuous delivery.
Seven builders helped turn user-defined HTTP callbacks into webhooks, making event-driven integration a normal part of APIs, developer tools, SaaS automation, and continuous delivery.
Seven contributors helped bring links, affordances, media types, and machine-discoverable state transitions into API design instead of treating APIs as fixed endpoint catalogs.
Seven thinkers helped turn events, logs, asynchronous messaging, and stream processing into a major architectural model for loosely coupled distributed systems.
Seven practitioners helped separate commands from queries and turn domain events into durable system history through CQRS, event sourcing, messaging, and domain-driven design.
Seven practitioners helped converge on a family of architectures that protect domain logic by forcing framework, database, UI, and infrastructure dependencies to point inward.
Seven practitioners helped turn business-domain understanding into an architectural discipline built around ubiquitous language, bounded contexts, aggregates, events, and explicit model boundaries.
Seven practitioners and toolmakers helped compress software delivery from infrequent integration events into automated build, test, and deployment pipelines.
Seven community builders, researchers, and practitioners helped turn the development–operations divide into the DevOps movement around flow, automation, feedback, and shared ownership.
Seven practitioners helped turn large-scale operations into an engineering discipline centered on reliability targets, automation, service-level objectives, and learning from failure.
Seven researchers and engineers helped grow Spark from Berkeley research into a general engine for batch, SQL, streaming, and machine-learning workloads.