Neat!
Readit Newsjeanyang commented on Summary: The daily number game that thinks it's a word game auftup.com/summary... · Posted by u/jsvine
jeanyang commented on Postman acquires Akita for automated API observability blog.postman.com/postman-... · Posted by u/captn3m0
Congrats to the Akita team! Repository is 2 years old. That's a pretty quick exit.
Thank you! I've been at it since 2018 and we've been working on the repo since 2020, after pivoting from API security. -Jean from Akita
jeanyang commented on Drop-in endpoint observability for Docker and K8s akitasoftware.com/blog-po... · Posted by u/eob
How does this compare to Cilium's Hubble?
Can you host the dashboard and data storage yourself or is it only accessible as a hosted SaaS product (free or otherwise)?
Hello, Jean here from Akita.
Akita is lighter weight in terms of install and setup than Cilium's Hubble and will get you to insights more quickly. With Akita, it's easier to have a single dev use Akita and get visibility across many services. Cilium's Hubble is more of a power tool: it will give you more different kinds of data, which can be quite useful for people who are looking for that.
Akita is currently only accessible as a hosted SaaS product (with a free tier).
jeanyang commented on Drop-in endpoint observability for Docker and K8s akitasoftware.com/blog-po... · Posted by u/eob
I was confused by the first chart where they cropped off the Y-Axis label.
I thought the X-Axis was "# of people at the company" and the Y-Axis was "# of developers". That wouldn't make sense because the "less than 10" person company would have "16.40" developers!
I found the survey they mentioned. The Y-Axis is "Number of Internal APIs" which makes much more sense. https://rapidapi.com/blog/rapidapi-developer-survey-insights...
Ah good catch! I have updated the graphic to not cut off the left axis label. Thanks.
"Almost immediately after installation, Akita provided all the endpoints’ requirements, as well as some examples of expected values, which allowed us to better understand the service that the contractors had built. Once we could understand the data flow (including not only the request body, but also headers and authorization), improving the system became a lot easier. After we had the mapping,"
Interesting... could be cool to see a value-add service on top of Akita or another Obs vendor that just inspects req/res payloads and generates OpenAPI specs based off what was observed. I can't count how many times I've dropped into teams and tried to piece together their API contracts just to realize... they don't have specs! Having to then turn around and reconstruct them backwards based off code spelunking and maybe some design docs is... frustrating.
Hi, Jean here from Akita. Yes, it's possible to generate an OpenAPI spec, either by running Akita in production or from a HAR file. Here's a blog post someone wrote about using Akita to generate an OpenAPI spec: https://apisyouwonthate.com/blog/creating-openapi-from-http-...