March 2017 Summaries

In her article, Jennifer Craig outlines five common mistakes that teams make in their API product strategy and offers advice on how to avoid them. She emphasizes the importance of solving the right problem by mapping out how the API fits into usage scenarios to ensure it addresses a specific pain point for the target audience. Clarity is crucial, as APIs should focus on solving a clear problem rather than offering a multitude of disconnected features. Craig differentiates between delivering capabilities, which empower users to achieve new outcomes, and features, which are merely the tools to achieve those outcomes. She also highlights the significance of ongoing product ownership beyond the initial release, urging API product owners to continuously seek stakeholder feedback and plan for future iterations. Finally, she advises against long design and delivery cycles, recommending a design-first approach to balance speed and consumer safety, and encourages the use of cross-functional teams and tools like the OpenAPI Specification to streamline the delivery process while keeping stakeholders engaged.

API eventing represents a significant opportunity for API providers to enhance their platforms and deliver greater value to users by moving beyond the traditional request-response model over HTTP. This shift toward event-driven architectures is driven by the rise of technologies like webhooks, Kafka, and the integration of IoT devices, which allow APIs to engage in dynamic, two-way interactions. API events enable innovation by automating tasks such as continuous integration, foster collaboration through integrations with messaging platforms like Slack, and facilitate codeless integration with iPaaS tools like Zapier and IFTTT. Additionally, they provide architectural flexibility for microservices by allowing services to communicate changes and business events efficiently, and they are crucial for IoT devices and edge computing, where event streaming supports seamless communication between devices and cloud services. By supporting event subscriptions, APIs can deliver a richer user experience and reduce consumer churn, making them more adaptable and valuable in solving everyday problems.

An open-source WordPress plugin now enables the integration of Tyk API developer portal functionalities into any WordPress site, thanks to contributions from Liip, a prominent Swiss web application developer. This collaboration allows users to create advanced API Developer portals by combining Tyk's API capabilities with WordPress's content management system. The plugin, which is already being used by the Swiss Federal Railways, offers features such as automatic developer registration, API policy configuration, and token management, including request and revocation processes. While it does not manage the Tyk API Gateway, it provides a streamlined way to handle developer access and monitor API usage statistics. The plugin is available on GitHub and WordPress.org, with users encouraged to share their insights and suggestions for future enhancements.