TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Monitor Every API Call in Your Codebase, Today

3 点作者 gmontard超过 5 年前

1 comment

PragmaticPulp超过 5 年前
Some unsolicited feedback from a potential customer:<p>1) The animated .gif in the product announcement does not inspire confidence. When you&#x27;re asking customers to trust you with all of their external API calls, the website needs to be 100% professional and polished from top to bottom. A quirky animated .gif sends the wrong message.<p>2) The product page is surprisingly vague. I wanted to understand how this compares to a known solution like New Relic, but the product description looks like unfinished placeholder copy:<p>&gt; Get a complete picture of third-party API usage at a glance. Instantly view all API used, latency, error rate, etc. &gt; Filter per API and compare usage between time.<p>3) Finally, locking myself into your product as an intermediary for external APIs feels massively risky versus just adding a known monitoring solution like New Relic. What&#x27;s the advantage, other than simplicity? As a customer, this feels like an enormous risk for possibly negative gain, because now my developers need to learn and support two APIs (Bearer&#x27;s API as well as the 3rd-party API) and jump between two sets of possibly conflicting documentation. I&#x27;d want to see much more explanation for the upside of this tool before we considered using it for anything.