October 2017 Summaries

Before making a private API public, it is crucial to undergo thorough planning and assessment of several key factors to ensure security and functionality. The process begins with a comprehensive security review, as private APIs often lack the rigorous design scrutiny required for public exposure, exemplified by Tinder's past privacy issues. Enhancing API documentation is essential to replace the informal communication methods used internally, ensuring that new users can understand the API's features, authentication, and endpoints. Providing usage examples through code snippets and demo applications can facilitate developer integration. It is also vital to implement rate limiting and endpoint protection to safeguard against unauthorized access and excessive use, protecting performance and infrastructure costs. Finally, defining key performance indicators (KPIs) and utilizing analytics for tracking usage are necessary for aligning the API with business and technical goals, ensuring the new public API's success. Tyk offers a platform with the necessary features for API management, including security, analytics, and developer support, to help organizations transition their APIs from private to public effectively.

Tyk announced a new integration that simplifies the deployment of Tyk Multi-Cloud using Heroku, a platform as a service that facilitates building, running, and managing applications in the cloud. This integration allows users to deploy the Tyk API Gateway on Heroku with a single click, enabling quick management of APIs with up to 1,000 calls per day during a free trial period. The setup is designed to be user-friendly, eliminating the need for users to manage their own hosting and configurations. Initially available as an invite-only beta trial, the integration aims to gather user feedback for continuous improvement, offering participants Tyk swag in exchange for their insights. The integration is particularly appealing for developers and teams who wish to experiment with Tyk or conduct proof-of-concept projects without significant infrastructure investment.

This article discusses the integration of Tyk and Git to streamline the process of source-controlling APIs, particularly in the context of continuous deployment and integration. It introduces a tool called Tyk-Git, designed to facilitate the migration of API configurations across different environments, such as development, testing, and production, while minimizing human error and ensuring consistency. Tyk-Git allows users to dump API definitions and policies from a Tyk dashboard into a directory, making them portable and version-controlled via Git. By employing ID masking, Tyk-Git ensures that policy IDs remain immutable, thus maintaining configuration integrity across environments. The tool supports synchronization with dashboards, updating existing APIs and policies without creating redundant entries, and enables API configurations to be deployed selectively to various environments. Although Tyk-Git is in its early stages of development, the article encourages users to experiment with it and provide feedback, with the potential for its functionalities to be integrated into core applications in the future.