What is Runscope and what are its top alternatives?
Top Alternatives to Runscope
It is the only complete API development environment, used by nearly five million developers and more than 100,000 companies worldwide. ...
Simulate any user scenario for webapps, websites, mobile apps or web services. 100% Apache JMeter compatible. Scalable from 1 to 1,000,000+ concurrent users.<br> ...
New Relic is the all-in-one web application performance tool that lets you see performance from the end user experience, through servers, and down to the line of application code. ...
Pingdom is an uptime monitoring service. When problems happen with a site that Pingdom monitors, it immediately alerts the owner so the problem can be taken care of. ...
API management, design, analytics, and security are at the heart of modern digital architecture. The Apigee intelligent API platform is a complete solution for moving business to the digital world. ...
Reduce bugs in web applications by using Assertible to create an automated QA pipeline that helps you catch failures & ship code faster. ...
Kong is a scalable, open source API Layer (also known as an API Gateway, or API Middleware). Kong controls layer 4 and 7 traffic and is extended through Plugins, which provide extra functionality and services beyond the core platform. ...
Amazon API Gateway
Amazon API Gateway handles all the tasks involved in accepting and processing up to hundreds of thousands of concurrent API calls, including traffic management, authorization and access control, monitoring, and API version management. ...
Runscope alternatives & related posts
- Easy to use481
- Great tool366
- Makes developing rest api's easy peasy274
- Easy setup, looks good154
- The best api workflow out there142
- History feature53
- It's the best53
- Adds real value to my workflow43
- Great interface that magically predicts your needs41
- The best in class app34
- Can save and share script10
- Fully featured without looking cluttered9
- Global/Environment Variables6
- Shareable Collections6
- Dead simple and useful. Excellent6
- Dark theme easy on the eyes6
- Option to run scrips6
- Awesome customer support5
- Great integration with newman5
- The test script is useful4
- This has simplified my testing significantly3
- Easy as pie3
- Makes testing API's as easy as 1,2,33
- Saves responses3
- Mocking API calls with predefined response2
- I'd recommend it to everyone who works with apis2
- Pre-request Script and Test attributes are invaluable1
- Postman Runner CI Integration1
- Now supports GraphQL1
- Continuous integration using newman1
- Easy to setup, test and provides test storage1
- <a href="http://fixbit.com/">useful tool</a>0
- Stores credentials in HTTP8
- Poor GraphQL support7
- Bloated features and UI6
- Cumbersome to switch authentication tokens5
- Can't prompt for per-request variables1
related Postman posts
We just launched the Segment Config API (try it out for yourself here) — a set of public REST APIs that enable you to manage your Segment configuration. A public API is only as good as its #documentation. For the API reference doc we are using Postman.
Postman is an “API development environment”. You download the desktop app, and build API requests by URL and payload. Over time you can build up a set of requests and organize them into a “Postman Collection”. You can generalize a collection with “collection variables”. This allows you to parameterize things like
workspace_name so a user can fill their own values in before making an API call. This makes it possible to use Postman for one-off API tasks instead of writing code.
Then you can add Markdown content to the entire collection, a folder of related methods, and/or every API method to explain how the APIs work. You can publish a collection and easily share it with a URL.
This turns Postman from a personal #API utility to full-blown public interactive API documentation. The result is a great looking web page with all the API calls, docs and sample requests and responses in one place. Check out the results here.
Postman’s powers don’t end here. You can automate Postman with “test scripts” and have it periodically run a collection scripts as “monitors”. We now have #QA around all the APIs in public docs to make sure they are always correct
Along the way we tried other techniques for documenting APIs like ReadMe.io or Swagger UI. These required a lot of effort to customize.
Writing and maintaining a Postman collection takes some work, but the resulting documentation site, interactivity and API testing tools are well worth it.
Our whole Node.js backend stack consists of the following tools:
- Lerna as a tool for multi package and multi repository management
- npm as package manager
- NestJS as Node.js framework
- TypeScript as programming language
- ExpressJS as web server
- Swagger UI for visualizing and interacting with the API’s resources
- Postman as a tool for API development
- TypeORM as object relational mapping layer
- JSON Web Token for access token management
The main reason we have chosen Node.js over PHP is related to the following artifacts:
- Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
- I can run load tests without needing JMeter scripts.9
- Easy to prepare JMeter workers3
- UI centric1
related BlazeMeter posts
- Easy setup414
- Really powerful345
- Awesome visualization244
- Ease of use194
- Great ui151
- Free tier107
- Great tool for insights81
- Heroku Integration66
- Market leader55
- Peace of mind49
- Push notifications21
- Email notifications20
- Heroku Add-on17
- Error Detection and Alerting16
- Multiple language support12
- SQL Analysis11
- Server Resources Monitoring11
- Transaction Tracing9
- Apdex Scores8
- Azure Add-on8
- Analysis of CPU, Disk, Memory, and Network7
- Detailed reports6
- Performance of External Services6
- Error Analysis6
- Application Availability Monitoring and Alerting6
- Application Response Times6
- JVM Performance Analyzer (Java)5
- Most Time Consuming Transactions5
- Easy to use4
- Top Database Operations4
- Browser Transaction Tracing4
- Application Map3
- Pagoda Box integration3
- Custom Dashboards3
- Weekly Performance Email3
- Easy visibility2
- App Speed Index2
- Easy to setup2
- Real User Monitoring Analysis and Breakdown1
- Incident Detection and Alerting1
- Real User Monitoring Overview1
- Worst Transactions by User Dissatisfaction1
- Metric Data Resolution1
- Metric Data Retention1
- Team Collaboration Tools1
- Super Expensive1
- Time Comparisons1
- Access to Performance Data API1
- Background Jobs Transaction Analysis1
- Best of the best, what more can you ask for1
- Best monitoring on the market1
- Rails integration1
- Pricing model doesn't suit microservices19
- UI isn't great10
- Visualizations aren't very helpful7
- Hard to understand why things in your app are breaking5
related New Relic posts
Hey there! We are looking at Datadog, Dynatrace, AppDynamics, and New Relic as options for our web application monitoring.
Current Environment: .NET Core Web app hosted on Microsoft IIS
Future Environment: Web app will be hosted on Microsoft Azure
Tech Stacks: IIS, RabbitMQ, Redis, Microsoft SQL Server
Requirement: Infra Monitoring, APM, Real - User Monitoring (User activity monitoring i.e., time spent on a page, most active page, etc.), Service Tracing, Root Cause Analysis, and Centralized Log Management.
Please advise on the above. Thanks!
Regarding Continuous Integration - we've started with something very easy to set up - CircleCI , but with time we're adding more & more complex pipelines - we use Jenkins to configure & run those. It's much more effort, but at some point we had to pay for the flexibility we expected. Our source code version control is Git (which probably doesn't require a rationale these days) and we keep repos in GitHub - since the very beginning & we never considered moving out. Our primary monitoring these days is in New Relic (Ruby & SPA apps) and AppSignal (Elixir apps) - we're considering unifying it in New Relic , but this will require some improvements in Elixir app observability. For error reporting we use Sentry (a very popular choice in this class) & we collect our distributed logs using Logentries (to avoid semi-manual handling here).
- Simple and reliable225
- Monitoring your websites103
- Easy to use dashboard75
- Email, text & twitter alerts65
- Free tier43
- Performance data23
- Detailed Reports14
- Email Reports11
- Mobile App9
- Root Cause Analysis9
- 30-day risk free trial1
- Easy setup1
- IOS app1
- UI is incredibly complicated3
- Hard to set up alerts properly2
related Pingdom posts
We currently monitor performance with the following tools:
- Heroku Metrics: our main app is Hosted on Heroku, so it is the best place to get quick server metrics like memory usage, load averages, or response times.
- Good old New Relic for detailed general metrics, including transaction times.
- Skylight for more specific Rails
Controller#actiontransaction times. Navigating those timings is much better than with New Relic, as you get a clear full breakdown of everything that happens for a given request.
Skylight offers better Rails performance insights, so why use New Relic? Because it does frontend monitoring, while Skylight doesn't. Now that we have a separate frontend app though, our frontend engineers are looking into more specialized frontend monitoring solutions.
Finally, if one of our apps go down, Pingdom alerts us on Slack and texts some of us.
#Datadog #Relay42 #Monitoring
With Datadog unveiling their Synthetics product (https://www.datadoghq.com/blog/introducing-synthetic-monitoring/), we at Relay42 are considering moving out of Pingdom.
The rationale is simple:
90% of our monitoring is on Datadog, apart from the external requests. It'd be nice to identify regional issues in one place, so this is great in our monitoring consolidation efforts.
The lack of a non-community Terraform provider for Pingdom
We have yet to get in the beta and test it out but we feel very excited about this announcement.
- Highly scalable and secure API Management Platform10
- Quick jumpstart5
- Good documentation5
- Fast and adjustable caching3
- Easy to use3
related Apigee posts
related Assertible posts
- Easy to maintain36
- Easy to install30
- Great performance20
- Api blueprint5
- Custom Plugins4
- Documentation is clear1
related Kong posts
We needed a lightweight and completely customizable #microservices #gateway to be able to generate #JWT and introspect #OAuth2 tokens as well. The #gateway was going to front all #APIs for our single page web app as well as externalized #APIs for our partners.Contenders
We looked at Tyk Cloud and Kong. Kong's plugins are all Lua based and its core is NGINX and OpenResty. Although it's open source, it's not the greatest platform to be able to customize. On top of that enterprise features are paid and expensive. Tyk is Go and the nomenclature used within Tyk like "sessions" was bizarre, and again enterprise features were paid.Decision
We ultimately decided to roll our own using ExpressJS into Express Gateway because the use case for using ExpressJS as an #API #gateway was tried and true, in fact - all the enterprise features that the other two charge for #OAuth2 introspection etc were freely available within ExpressJS middleware.Outcome
We opened source Express Gateway with a core set of plugins and the community started writing their own and could quickly do so by rolling lots of ExpressJS middleware into Express Gateway
- AWS Integration35
- Less expensive1
- No websocket broadcast1