What is Firecamp and what are its top alternatives?
Top Alternatives to Firecamp
It is the only complete API development environment, used by nearly five million developers and more than 100,000 companies worldwide. ...
Easiest way to run a GraphQL server: Sensible defaults & includes everything you need with minimal setup.;Includes Subscriptions: Built-in support for GraphQL subscriptions using WebSockets.;Compatible: Works with all GraphQL clients (Apollo, Relay...) and fits seamless in your GraphQL workflow. ...
A beautiful feature-rich GraphQL Client IDE for all platforms. Enables you interact with any GraphQL server you are authorized to access from any platform you are on. Much like Postman for GraphQL, you can easily test and optimize your Grap ...
Represent any GraphQL API as an interactive graph. It's time to finally see the graph behind GraphQL. ...
It allows you to easily and quickly deploy GraphQL APIs on AWS, and integrate them with AWS Lambda, DynamoDB & others. It supports all AWS AppSync features, while offering sane defaults that makes working with AppSync a lot easier without compromising on flexibility. ...
Visual GraphQL Editor is a visual backend editor that speed's up software development and improve's communication with non-tech people. It's a is a bridge between tech and non-tech users. Professionals can import their previously written code and visualize it on diagram while newbies can link visual blocks and editor will transform them into code. Our tool makes understanding GraphQL schema a lot easier. ...
Made by the team at hasura.io, graphqurl is a curl like CLI for GraphQL.
Firecamp 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.
- Easy to setup. No boilerplate code2
related graphql-yoga posts
I just finished a web app meant for a business that offers training programs for certain professional courses. I chose this stack to test out my skills in graphql and react. I used Node.js , GraphQL , MySQL for the #Backend utilizing Prisma as a database interface for MySQL to provide CRUD APIs and graphql-yoga as a server. For the #frontend I chose React, styled-components for styling, Next.js for routing and SSR and Apollo for data management. I really liked the outcome and I will definitely use this stack in future projects.
In my last side project, I built a web posting application that has similar features as Facebook and hosted on Heroku. The user can register an account, create posts, upload images and share with others. I took an advantage of graphql-subscriptions to handle realtime notifications in the comments section. Currently, I'm at the last stage of styling and building layouts.
For the #Backend I used graphql-yoga, Prisma, GraphQL with PostgreSQL database. For the #FrontEnd: React, styled-components with Apollo. The app is hosted on Heroku.
- Easy setup1
- Available in all platforms1
- Multiple windows1
- Well designed UI1
- Open source1
- Easy to use1
related Altair GraphQL posts
related GraphQL Voyager posts
related Serverless AppSync posts
- Visual GraphQL Editor3
- Web based GraphiQL3
- Visualize your code on diagram3
- Generate queries for front end3
- Fake / mocked backend3
- Generate code from diagram2
related GraphQL Editor posts
- Use with Apollo1
- Code first1