March 2020 Summaries

Tyk, a remote-first organization, has successfully leveraged its global approach to create a dynamic and innovative team spread across 25 countries. Originally necessitated by the geographical distance between its founders, the remote-first model has become a competitive advantage, emphasizing trust, flexibility, and output over traditional office presence. The company encourages its employees, known as Tyklings, to adapt remote working to their personal styles and utilize technology like Zoom and Slack for communication and collaboration. Emphasizing the importance of a supportive company culture, Tyk fosters connections through social initiatives like twice-weekly virtual cafés and encourages employees to engage with colleagues across the organization. The company operates in a paperless environment, utilizing tools like GitHub, Google Docs, and Trello to maintain accessibility and efficiency in its remote operations.

In exploring the deployment of API gateways, organizations face decisions about using single or multiple gateway clusters to effectively manage their APIs, considering factors such as compliance, security, and flexibility. Employing multiple API gateways can provide significant advantages, such as segmenting APIs based on risk or compliance needs, which is crucial for regulatory adherence and data protection, particularly in sectors requiring stringent audits like financial services. Different types of API gateways, including internal, partner, and public gateways, serve distinct functions: internal gateways limit access to sensitive data within an organization, partner gateways manage specific endpoints for partner integrations, and public gateways support broader use cases like third-party developer interactions. Organizations must also weigh the benefits and challenges of environment-based gateways which separate development, staging, and production environments, although this can increase the number of gateway instances needed. Ultimately, some organizations might find a single API gateway sufficient initially, with the option to expand to multiple gateways later as needs evolve, balancing simplicity and cost-effectiveness against the complexity and advantages of a multi-gateway approach.

Managing an API program effectively involves a series of strategic actions that cater to the unique needs of an organization, whether it's undergoing digital transformation or managing existing APIs. Key steps include understanding the broader API landscape while acknowledging that not all strategies from leading companies like Netflix or Amazon will be suitable for every organization. It's crucial to grasp the intricacies of HTTP, document the API ecosystem, and understand current usage patterns to enhance security and functionality. Establishing a consistent API style guide and implementing a developer experience (DX) review process can significantly improve integration and reduce support costs. Additionally, unifying security measures, focusing on end-to-end delivery rather than a layer-by-layer approach, and automating operations are essential for efficiency. Planning for legacy system support and seeking external input when necessary can aid in smoother modernization efforts. By carefully navigating these steps, organizations can create a robust API program that aligns with their technological and business transformation goals.

Building your own API gateway can seem appealing due to the promise of a tailored solution, but it often proves to be a complex and time-consuming endeavor fraught with unforeseen challenges. Many organizations initially consider this approach because existing solutions may not meet their specific needs or because they operate in unique environments. However, the journey from concept to a production-ready gateway involves significant effort in terms of development, security, and ongoing maintenance. The initial vision often misaligns with reality, leading to a feature set that mirrors existing commercial offerings. Furthermore, issues such as security vulnerabilities and scalability can arise, making it difficult to match the performance and reliability of vendor solutions. Consequently, for most organizations, leveraging existing API gateway solutions can be a more efficient and effective choice, allowing developers to focus on delivering business value rather than reinventing the wheel.

Tyk, originally a community project, remains deeply committed to its community, which has grown to over one million downloads with global events and users. The organization plans to enhance its community forum by investing more time and resources, updating the site's visuals and structure, and generating more useful content. They are encouraging community feedback through a survey to better serve users and have launched the Side Project Fund, a micro-grant program for innovative ideas. Tyk also celebrates user contributions through Community Awards, highlighting impactful projects like Logz.io's integration and recognizing active contributors. Additionally, Tyk has been acknowledged as a fast-growing UK scale-up by Tech Nation's Upscale programme, underscoring the importance of community involvement in open-source initiatives.