Runscope Blog
blog.runscope.com · Company blog · on HN since 2013
Runscope's company blog covering API testing and monitoring, API design advice, engineering notes, and its acquisition by CA Technologies.
What HN saysHN users link it for API error and GraphQL-alternative posts. One commenter is fairly happy with Runscope for basic API monitoring but wants longer response data retention.
21HN people shared it
5linked it in comments
47stories submitted
395story points
4 years agolast shared
2013people per year2026
Most-shared posts
- 1Runscope acquired by CA Technologies3 people · 15 points · first shared 2017 · 4 comments on HN
- 26 Common API Errors3 people · 9 points · first shared 2017 · discussion on HN
- 3You Might Not Need GraphQL2 people · 107 points · first shared 2017 · 27 comments on HN
- 4OpenAPI / Swagger Resource List for API Developers2 people · 11 points · first shared 2017 · 1 comments on HN
- 5Build a Twilio-like Request Inspector in One Day with Runscope Embeds2 people · 7 points · first shared 2013 · discussion on HN
- 6Monolith to Microservices: Transforming a real-world e-commerce platform2 people · 6 points · first shared 2017 · discussion on HN
- 7Golang at Runscope2 people · 6 points · first shared 2014 · 1 comments on HN
- 8Tutorial: Continuous Integration with Runscope API Tests and Codeship2 people · 5 points · first shared 2017 · discussion on HN
- 9Runscope phasing our their Traffic Inspector2 people · 4 points · first shared 2018 · 2 comments on HN
- 10Introducing Runscope Radar: Automated API Testing and Monitoring2 people · 2 points · first shared 2013 · discussion on HN
- 11Meet Runscope1 people · 85 points · first shared 2013 · 29 comments on HN
- 12Understanding OAuth 2.0 and OpenID Connect1 people · 72 points · first shared 2018 · 24 comments on HN
- 13What's in a Modern Software Monitoring Toolkit?1 people · 10 points · first shared 2018 · discussion on HN
- 14Migrating to DynamoDB: Lessons in Schema Design1 people · 6 points · first shared 2016 · 1 comments on HN
- 15Microsoft Build, from an API Perspective1 people · 5 points · first shared 2015 · discussion on HN
What HN people wrote when they linked it
philstu · 2017-05-22
Hey! I cover that a bit ni a followup blog post :)
https://blog.runscope.com/posts/you-might-not-need-graphql
tl;dr: maybe you want OData, JSON-API, or one of the many other standards or practices that solve this simple problem as their super-set of functionality on top of the networking principles of REST.
Using GraphQL for this alone is rather nuclear, as you gain a lot with GraphQL but lose other stuff.
CodeAlong · 2018-10-24
We have been fairly happy with Runscope [0] for fairly simplistic monitoring of api response codes and body payloads. My biggest complaint is probably the lack of individualized response data after >= 24 hours.
Still waiting to see if the CA Technologies acquisition [1] makes things worse or not.
[0] https://www.runscope.com/
[1] https://blog.runscope.com/posts/301
johns · 2016-11-15
smarx · 2015-10-21
Seems like a useful tool; thanks for sharing it!
Two questions:
1) What's the diff logic? At first glance, it looks like JSON is reformatted (maybe canonicalized in some way) and then a line-by-line diff is applied. Is there more to it? Since the tool seems JSON-aware, I was surprised to see an added trailing comma up as a difference.
2) Do you have plans to expand the kind of HTTP requests users can make? It would be nice to use different verbs, headers, and request bodies. Runscope has a similar tool[0] built in that I believe (haven't tried it yet) allows a bit more flexibility, but it would be nice to have a standalone tool available.
[0] http://blog.runscope.com/posts/comparing-http-requests-using-runscope
epanastasi · 2014-08-01
Runscope - San Francisco, CA
Runscope is building tools for developers working on API-driven mobile and web applications. Working at Runscope means joining a small team of fun, smart, collaborative people who care about quality, APIs, and building developer tools. Even if you don't see a position here that fits you perfectly, we're always interested in talking with people who love APIs. We have proven work/life balance (checkout https://www.runscope.com/work_at_runscope for the data), are well funded, and we're looking to grow the team!
We write code in Python and Go, deploy 15-20 times a day, and use our own product to help us write better code!
Positions open:
* Lead Web Engineer
* Mobile Networking Engineer
* Senior Software Engineer
* Software Engineer
* Enterprise Inside Sales
If you're interested or want more information email us at: [email protected]
Check out the jobs page: https://www.runscope.com/work_at_runscope
Read some of our blog posts:
http://blog.runscope.com/posts/go-at-runscope
http://blog.runscope.com/posts/100-continue
http://blog.runscope.com/posts/introducing-runscope-radar-automated-ap…
"Everything is going to be 200 OK"