February 2022 Summaries

GraphQL back-ends are increasingly essential in the API industry due to their ability to provide front-end developers with more control over the data sent by back-ends, potentially reducing traffic and improving efficiency for slow mobile connections. Unlike REST, GraphQL's well-defined specification allows for more consistent implementations, making it more accessible for developers. This article demonstrates how to build a GraphQL back-end using Apollo Server on Node.js, including setting up a simple server to query tasks and creating a custom analytics extension to monitor request lifecycle stages. This extension can log data and timings at each stage, which can be viewed using debugging tools like those in Visual Studio Code (VSCode). By integrating with VSCode's debugger, developers can gain deeper insights into the server's operation, aiding in performance monitoring and debugging. The Apollo Server's extension system facilitates integration with monitoring services, offering detailed access to request lifecycle stages, ultimately helping developers understand and improve their GraphQL servers.

Deciding between building an in-house API analytics platform and purchasing a third-party solution like Moesif involves complex considerations, including cost, resources, and potential long-term benefits. Building an API analytics system requires substantial investment in infrastructure, visualization, security, and compliance features, with costs significantly increasing as the system scales to handle higher data volumes. Additionally, ongoing maintenance, compute, storage costs, and license fees for visualization tools add to the total expenses over time. A ready-made solution like Moesif can offer considerable cost savings by providing advanced features such as conversion funnels and retention analysis, allowing engineering teams to focus on core product development rather than maintaining legacy systems. Moesif's expertise in API analytics further supports enterprises by offering guidance and support, thus enhancing decision-making capabilities without overwhelming teams with complex metrics.

Usage-based pricing models like Pay As You Go (PAYG) are gaining traction in the SaaS industry for their potential to boost revenue and customer retention compared to traditional subscription models. These models require customers to pay based on their actual consumption, such as hours used or transactions made, and are supported by major cloud providers like AWS, Google, and Azure. A critical decision for businesses is whether to implement prepaid or postpaid billing, each with its own advantages and challenges, including cash flow management and customer budgeting. Billing frequency and measurement are vital, requiring systems that can accurately track and report usage, potentially leveraging tools like Moesif for analytics and quota notifications to prevent customer surprises. The implementation of self-serve dashboards providing visibility into usage metrics can enhance the customer experience by allowing them to manage their consumption and costs effectively. Despite the benefits, these pricing models are more complex to implement and require careful management to ensure transparency and customer satisfaction.

In Episode 9 of Moesif's podcast, Larry Ebringer hosts Claire Barrett, Director at APIsFirst, to discuss key strategies for successful digital transformation and API product management in large enterprises. Barrett emphasizes the importance of digital savviness, shared business goals, and balanced teams, highlighting the distinction between project and product management. She explains that while project management focuses on achieving specific goals and deliverables, product management centers on the long-term vision of the product's lifecycle, customer-centricity, and data-driven decisions. The discussion also touches on the need for organizations to balance internal capability building with external consultancy to drive digital change effectively. Barrett advocates for inclusive and balanced teams, which foster creativity and resilience, and shares insights from her leadership of the Global Women in APIs initiative, which aims to enhance skills and confidence through public speaking and writing programs.

Serverless computing is a cloud-based model where the management of servers and infrastructure is handled by the cloud provider, allowing developers to focus solely on application functionality and business logic. This approach, which is being adopted rapidly, offers advantages such as reduced compute costs through a consumption-based pricing model and the elimination of infrastructure management. It builds on the concept of microservices by further abstracting the infrastructure layer, leading to easier scalability and development. Major providers like AWS, Azure, and Google Cloud offer serverless solutions with varying levels of language support and deployment ease. AWS Lambda, Azure Functions, and Google Cloud Functions each have unique features and limitations, with AWS leading in integration options, Azure offering extensive language support, and Google focusing on its Firebase integration. Despite these benefits, serverless computing poses challenges in monitoring and debugging due to its dispersed logging context and vendor-specific implementations. Independent frameworks and vendor-neutral shims can help mitigate provider lock-in and standardize deployments across different platforms.

Setting up a local debugging environment for serverless applications using the AWS SAM CLI involves installing and configuring essential tools such as the AWS CLI, Docker, and VSCode. The SAM CLI, a Python-based command-line tool, facilitates the creation and management of serverless backends by emulating the AWS Lambda cloud environment on local machines using Docker. Developers can initiate a SAM project, write and test Lambda functions, and utilize VSCode's debug UI to set breakpoints and inspect variables. By configuring a launch file in VSCode, users can connect to the SAM CLI's debug process for a seamless debugging experience. Additionally, developers can streamline testing workflows with NPM scripts, allowing for efficient invocation of functions in debug mode. This setup aids in effectively testing and debugging serverless applications, ensuring they closely mimic the cloud environment where they will ultimately be deployed.

In the context of software engineering leadership, Moesif emphasizes the importance of adopting a mindset focused on leveraging capital efficiently to achieve significant business returns, rather than solely relying on traditional metrics or soft skills. Outstanding leaders are recognized for their ability to maximize the utility of resources like human, technical, and financial capital, thereby creating a positive return on investment (ROI) which, in turn, grants them more responsibility and greater influence within a company. The text argues that efficiency in resource utilization is crucial, as inefficient practices can lead to unnecessary costs and opportunity losses. Experienced managers often prefer purchasing third-party software solutions over building them in-house, as external vendors typically offer superior products that benefit from extensive research and development investments. This strategic approach not only reduces short-term and long-term costs but also mitigates risks associated with in-house development, thereby aligning with the broader business goal of maximizing ROI and making upper management look successful.

Moesif's integration with Zendesk enhances the resolution of technical issues by automatically importing user profile data, such as browser, device information, and HTTP error traces, directly into Zendesk tickets, streamlining the debugging process for RESTful APIs and integrated applications. This integration avoids lengthy email exchanges with customers for debug information and provides immediate access to detailed error analysis and application API history within Zendesk, eliminating the need to manually search application logs. The setup involves logging into a Moesif account to retrieve an APPLICATION_ID, installing the Moesif integration from Zendesk’s Marketplace, and entering the integration token. This tool aims to improve customer experience by resolving issues swiftly, thus preventing customer attrition to competitors, with a 14-day free trial available for new users.

Moesif has introduced a new Metered Billing feature that allows users to monetize their APIs by billing customers based on usage tracked within Moesif. This feature simplifies the complex process of setting up a metered billing solution by integrating directly with billing providers to accurately calculate and send usage data for billing. Users can implement various billing strategies, such as pay-as-you-go or tiered approaches, and customize metrics to track specific usage criteria. Moesif aggregates API usage data, applies user-defined filters, and sends it to the billing provider, enabling a seamless post-paid monetization system. The feature is accessible via Moesif's interface, requiring minimal setup, and supports a highly customizable approach to billing.

AWS Lambda is a serverless compute service that runs code in response to events, while Amazon API Gateway manages HTTP endpoints of REST APIs, connecting them to backend business logic. The guide details setting up Moesif API analytics to track APIs hosted on AWS Lambda using API Gateway as a trigger. It explains implementing a Lambda function handler in Go, logging API requests, and using Moesif Middleware to send logs for analytics and debugging. The middleware allows secure logging by masking sensitive information and offers configuration options for data protection. Moesif provides insights into API usage, helping optimize performance and understand traffic patterns.

The healthcare sector, which constitutes 17% of the US GDP, is undergoing transformative changes, with remote medicine and digital health services becoming more prevalent due to the COVID-19 pandemic. This shift has increased the digitalization and electronic handling of patient records, highlighting the critical role of APIs in facilitating new healthcare services. However, this evolution necessitates stringent compliance with HIPAA and HITECH laws to protect electronic Protected Health Information (ePHI). API developers handling ePHI must ensure compliance by signing Business Associates Agreements (BAAs) with relevant parties and adopting safeguards aligned with HIPAA's Privacy, Security, and Breach Notification Rules. These measures include encrypting data, maintaining detailed logs, and conducting risk assessments to prevent unauthorized access and disclosures. Non-compliance can lead to significant civil and criminal penalties, with breaches being made public. The landscape is ripe for disruption, with APIs playing a central role in modernizing healthcare processes.

API product management is a burgeoning role in both startups and enterprises, focusing on building and managing API platforms. Successful candidates should not only be adept product managers but also passionate about APIs and developer support. Key competencies for API PMs include understanding effective developer onboarding, selecting meaningful metrics for product success, and creating a well-balanced feature roadmap that considers market trends and customer feedback. API PMs must handle API versioning and deprecation carefully to avoid disrupting users, employing strategies like maintaining backward compatibility and effective communication. They should also be adept at segmenting developer communities based on relevant attributes and crafting comprehensive, up-to-date documentation using tools like OpenAPI. Additionally, API PMs should leverage analytics to measure API usage and value, and possess skills in data modeling to design efficient APIs for various use cases, such as eCommerce.

Enterprises and SaaS companies often rely on a multitude of external API integrations to enhance customer experience by outsourcing business functionalities to third-party services like Stripe and Algolia. However, integrating numerous vendors can lead to performance and reliability issues that may not be immediately visible, impacting customer satisfaction. Monitoring these integrations is crucial, focusing on metrics such as latency, reliability, availability, and usage to ensure seamless performance. Traditional Application Performance Monitoring (APM) tools fall short in tracking third-party APIs, prompting the need for solutions like Moesif, which employs techniques such as monkey patching and real user API monitoring to capture and analyze API calls effectively. By leveraging such monitoring, companies can detect anomalies, hold partners accountable for service-level agreements, and maintain operational resilience, ultimately improving the overall customer experience.

In a podcast episode from Moesif’s Podcast Network, Tyler Jewell, Managing Director at Dell Technologies Capital, discusses his journey from being the CEO of WS02 to focusing on investing in developer-first companies. With a keen interest in developer tools, devops, and infrastructure, Jewell emphasizes the importance of open-source project experience for founders and the significant influence of the developer ecosystem, which is valued at over a trillion dollars. He explores the evolving landscape of developer tools, highlighting the cyclical nature of bundling and unbundling that occurs every 15 years, driven by shifts like the introduction of Git in 2005. Jewell also notes the transformative potential of APIs in disrupting traditional businesses, using GameStop's shift toward a software company as an example, and discusses strategies for measuring developer experience, focusing on authentic engagement and emotional responses from developers. Additionally, he touches on the financial implications of API-first businesses, advocating for transitioning from pay-as-you-go models to contractual agreements at scale to ensure revenue predictability and manage consumption.

Providing APIs to customers requires ensuring they derive value from the service while maintaining automation to minimize human intervention. A developer portal can serve as a valuable platform for displaying key metrics such as API usage, performance, and billing information, tailored to the interests of developers, product leaders, and finance departments. API logs enhance this experience by offering structured data, context, and advanced filters for efficient debugging and integration. Usage reports should offer insights into business transactions by intervals, user demographics, and SLA compliance to demonstrate reliability and performance. Billing dashboards help customers optimize API use and manage expenses, while notifications alert them to quota limits, potentially driving upsells. Moesif facilitates embedding these metrics and logs into applications through simple steps involving creating an embed template, generating a workspace URL, and adding an iFrame to the frontend, thereby enhancing customer success by transparently showcasing the API's value.