Alternatives to Falcor logo

Alternatives to Falcor

GraphQL, Atlas, REST, Postman, and Amazon API Gateway are the most popular alternatives and competitors to Falcor.
26
67
+ 1
13

What is Falcor and what are its top alternatives?

Falcor lets you represent all your remote data sources as a single domain model via a virtual JSON graph. You code the same way no matter where the data is, whether in memory on the client or over the network on the server.
Falcor is a tool in the API Tools category of a tech stack.
Falcor is an open source tool with 9.7K GitHub stars and 458 GitHub forks. Here’s a link to Falcor's open source repository on GitHub

Top Alternatives to Falcor

Falcor alternatives & related posts

related GraphQL posts

Shared insights
on
Node.jsNode.jsGraphQLGraphQLMongoDBMongoDB

I just finished the very first version of my new hobby project: #MovieGeeks. It is a minimalist online movie catalog for you to save the movies you want to see and for rating the movies you already saw. This is just the beginning as I am planning to add more features on the lines of sharing and discovery

For the #BackEnd I decided to use Node.js , GraphQL and MongoDB:

  1. Node.js has a huge community so it will always be a safe choice in terms of libraries and finding solutions to problems you may have

  2. GraphQL because I needed to improve my skills with it and because I was never comfortable with the usual REST approach. I believe GraphQL is a better option as it feels more natural to write apis, it improves the development velocity, by definition it fixes the over-fetching and under-fetching problem that is so common on REST apis, and on top of that, the community is getting bigger and bigger.

  3. MongoDB was my choice for the database as I already have a lot of experience working on it and because, despite of some bad reputation it has acquired in the last months, I still believe it is a powerful database for at least a very long list of use cases such as the one I needed for my website

See more
Nick Rockwell
Nick Rockwell
SVP, Engineering at Fastly ¡ | 39 upvotes ¡ 1.2M views

When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

See more
Atlas logo

Atlas

21
46
0
Develop, deploy, and maintain your application anywhere. Use one console and one workflow from development to production
21
46
+ 1
0
PROS OF ATLAS
    No pros available
    CONS OF ATLAS
      No cons available

      related Atlas posts

      REST logo

      REST

      20
      94
      0
      A software architectural style
      20
      94
      + 1
      0
      PROS OF REST
      CONS OF REST
        No cons available

        related REST posts

        related Postman posts

        Noah Zoschke
        Noah Zoschke
        Engineering Manager at Segment ¡ | 30 upvotes ¡ 1.3M views

        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 username, password and 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.

        See more
        Simon Reymann
        Simon Reymann
        Senior Fullstack Developer at QUANTUSflow Software GmbH ¡ | 23 upvotes ¡ 750.7K views

        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:

        • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
        • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
        • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
        • 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.
        See more
        Amazon API Gateway logo

        Amazon API Gateway

        855
        620
        34
        Create, publish, maintain, monitor, and secure APIs at any scale
        855
        620
        + 1
        34
        PROS OF AMAZON API GATEWAY
        CONS OF AMAZON API GATEWAY

        related Amazon API Gateway posts

        related Insomnia REST Client posts

        Jason Barry
        Jason Barry
        Cofounder at FeaturePeek ¡ | 4 upvotes ¡ 838.1K views

        We've tried a couple REST clients over the years, and Insomnia REST Client has won us over the most. Here's what we like about it compared to other contenders in this category:

        • Uncluttered UI. Things are only in your face when you need them, and the app is visually organized in an intuitive manner.
        • Native Mac app. We wanted the look and feel to be on par with other apps in our OS rather than a web app / Electron app (cough Postman).
        • Easy team sync. Other apps have this too, but Insomnia's model best sets the "set and forget" mentality. Syncs are near instant and I'm always assured that I'm working on the latest version of API endpoints. Apps like Paw use a git-based approach to revision history, but I think this actually over-complicates the sync feature. For ensuring I'm always working on the latest version of something, I'd rather have the sync model be closer to Dropbox's than git's, and Insomnia is closer to Dropbox in that regard.

        Some features like automatic public-facing documentation aren't supported, but we currently don't have any public APIs, so this didn't matter to us.

        See more

        related Paw posts

        Jason Barry
        Jason Barry
        Cofounder at FeaturePeek ¡ | 4 upvotes ¡ 838.1K views

        We've tried a couple REST clients over the years, and Insomnia REST Client has won us over the most. Here's what we like about it compared to other contenders in this category:

        • Uncluttered UI. Things are only in your face when you need them, and the app is visually organized in an intuitive manner.
        • Native Mac app. We wanted the look and feel to be on par with other apps in our OS rather than a web app / Electron app (cough Postman).
        • Easy team sync. Other apps have this too, but Insomnia's model best sets the "set and forget" mentality. Syncs are near instant and I'm always assured that I'm working on the latest version of API endpoints. Apps like Paw use a git-based approach to revision history, but I think this actually over-complicates the sync feature. For ensuring I'm always working on the latest version of something, I'd rather have the sync model be closer to Dropbox's than git's, and Insomnia is closer to Dropbox in that regard.

        Some features like automatic public-facing documentation aren't supported, but we currently don't have any public APIs, so this didn't matter to us.

        See more
        OpenAPI logo

        OpenAPI

        159
        116
        0
        Allows the owner of a network-accessible service to give universal access
        159
        116
        + 1
        0
        PROS OF OPENAPI
          No pros available
          CONS OF OPENAPI
            No cons available

            related OpenAPI posts

            Joshua Dean KĂźpper
            Joshua Dean KĂźpper
            CEO at Scrayos UG (haftungsbeschränkt) ¡ | 4 upvotes ¡ 62.3K views

            We use Swagger Inspector in conjunction with our universal REST-API "Charon". Swagger Inspector makes testing edge-cases hassle-free and lets testing look easy. Swagger Inspector was also a great help to explore the Mojang-API, that we are dependent on, because it is the central repository for minecraft-account-data.

            We previously used Postman but decided to switch over to Swagger Inspector because it also integrated seamlessly into Swagger UI, which we use for displaying our OpenAPI specification of said REST-API.

            See more