In this post of the WHOOP Developer Platform series, readers learn about design decisions for developing a resilient, multitenant webhook solution. Check out the other posts in the series “Designing the WHOOP API” and “Your body doesn’t know what day it is”
In this post of the WHOOP Developer Platform series, readers that are interested in developing applications with WHOOP learn how to use physiological cycles, rather than calendar days, to provide the best experience for their users.
Welcome to the first WHOOP Developer Platform blog series, where the engineers behind the platform give readers an inside look across three posts!
In early 2020, WHOOP formed partnerships with companies and research institutions interested in our technology. Several of these partnerships required access to WHOOP APIs.
How We Automated Our Technical Documentation to Increase Developer Velocity.
Microservice architecture has become ubiquitous for many software engineering teams. This approach to building software promotes maintainability and interoperability of the many components required to produce a product. At WHOOP, we apply the same microservice principles when building the user interfaces for our internal developer tools, opting for small-footprint, individual UIs built on top of our microservices. This allows us to streamline developer workflows while limiting downtime and hiccups for any individual tool.
Often, infrastructure is viewed as the technology or the servers hosting and supporting applications. At WHOOP, infrastructure aims to support, unify, and accelerate product development. Here is how we view the impact of infrastructure development.