Header Image - Back4App Blog

Monthly Archives

7 Articles

GraphQL iOS: Using Cloud Functions in a Swift App

GraphQL iOS: Using Cloud Functions in a Swift App

On this article, I showed you how to use GraphQL with NodeJS Cloud Code in Back4app.

And on this guide, I showed you how to use Apollo GraphQL iOS Client with Swift.

Now let’s bring it all together and make lots of complicated operations by producing really easy code. And let’s also have XCode to automatically generate any API code for us even when we change Classes.

Sounds good? So get some coffee and get along!


Parse Self Hosted vs Back4App

Parse Self Hosted vs Back4App

Parse versus Back4App

Did you know that Parse and Back4app are two very different platforms? Often beginners confuse the two, which leads them to choose the wrong platform. We’re frequently asked by our users, what are the differences between Parse vs. Back4App. To help answer that, we have created the most comprehensive comparison of Back4App vs. Parse (self-hosted version).


Firebase Open Source Alternatives

Firebase Open Source Alternatives

Firebase Open Source Alternatives

This blog will provide a list of Open Source alternatives to Firebase and the benefits of using open source technologies for backend development. This article will explore the advantages of using Parse, Back4App, AWS Amplify, Kuzzle and Hoodie as open-source options to Firebase.

Even though Firebase is a feature-rich platform and great product, a proprietary framework has the following disadvantages over open-source platforms:

  • Vendor lock-in
  • Firebase owns the intellectual property over its framework
  • Lack of customization and flexibility to adapt the code
  • Dedicated hosting and private clouds are not an option at Firebase
  • Firebase base does not offer Enterprise contracts

Here is why you should use an open-source framework:


GraphQL and NodeJS integrations using Cloud Code Functions

GraphQL and NodeJS integrations using Cloud Code Functions

GraphQL brings sugar, spice, and everything nice to API developers, but it is basically a query language so you can specify what you are looking for.

What if you need more business intelligence than that in your application?

What if you need some logic along with it?

What if you want that neat NPM Module module along with it?

Well, fasten your seat belts because today I’ll show you something very powerful. And with great powers, comes great… well… great time savings, great possibilities, great lots of good stuff…

 


What is GraphQL

What is GraphQL

GraphQL is a query language for APIs developed by Facebook in 2012. In simple words, it’s used to load data from a server to a client (i.e. from an API to your application) much more efficiently than traditional services.

It’s fair to say that GraphQL is unlike anything you might have used before which is precisely why a large number of organizations have switched over to it for building APIs.

In this article, I’ll take a closer look at some of the major problems behind current REST APIs and how GraphQL solves them while improving productivity. I’ll also explain some of the key benefits developers can experience by using GraphQL and whether you should make the switch from REST to GraphQL.

Let’s get started.


GraphQL: is it the REST API “killer”?

GraphQL: is it the REST API “killer”?

After the implementation of the GraphQL support in Parse a lot of people reached me with a few questions, some of them worried about the future of REST API.
Is GraphQL going to “kill” it?
What will happen with my REST API methods? Do I need to rewrite my code?

In this article I will cover those questions, but short answer is: no, you don’t have to worry because GraphQL is not going to “kill” REST API and you also don’t have to worry about rewriting your already working REST API methods.