Header Image - Back4App Blog

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.

Hasura Alternatives – Top Competitors

Hasura Alternatives – Top Competitors

Hasura proceeds to innovate and dominate the real-time GraphQL market. While it extends a frequently refined collection of products for many varieties of development requirements, it may be not always the easiest, most agile, or cheapest option. There’s a frequently increasing inventory of cloud companies that extend products and services in ways that can avail developers with easiness and affordability.

In this blog post, I’ll show some of the alternatives to Hasura; some companies that are still young but still useful to developers.  Others are more stable businesses and running for a while.  The tutorial will include subsequent competitors:

  • Back4App – GraphQL database hosting platform
  • Parse – Open-Source GraphQL framework
  • GraphCool – Open-Source framework to deploy serverless GraphQL backends
  • AWS App Sync – Service to run GraphQL in the cloud
  • Postgraphile – GraphQL APIs from a Postgres schema
  • Subzero – GraphQL & REST APIs for databases

Mastering Web API authentication with Parse – Javascript SDK and GraphQL flavours

Mastering Web API authentication with Parse – Javascript SDK and GraphQL flavours

Many applications, especially websites, need to restrict access to their content, and having user accounts that show only information relevant to that user in a secure way is the most popular way to accomplish that.

Today we will learn how to implement the Login functionality to an already existing HTML page, writing very little code and having Parse doing all the heavy lifting for you, and in order to do that, I chose this template which you can download for free.

We will be using two distinct technologies that you can choose from: the Javascript SDK and GraphQL through Javascript.

GraphQL is our brand new shiny technology that was just released and my goal is to compare both ways to do the same thing, so you can pick the one you like best.
SPOILER ALERT!! I am sure you will like GraphQL better…

That already has all the necessary files for visually display the file but lacks functionality, which we will be adding.


Como fazer um aplicativo? 13 passos para um app de sucesso!

Como fazer um aplicativo? 13 passos para um app de sucesso!

Como desenvolver um aplicativo? 

Quer fazer algo grande? Tem uma excelente ideia para o próximo aplicativo de um bilhões de dólares?

Como criar um aplicativo?

Este artigo detalhará as lições aprendidas durante nossa jornada de empreendedora de 13 anos, gerenciando uma empresa de desenvolvimento de software e criando centenas de aplicativos móveis. Vamos revelar os segredos ocultos de como dar vida às suas ideias. Forneceremos etapas práticas com base em nossa própria experiência em aplicativos para dispositivos móveis e compartilharemos algumas dicas que funcionaram bem para nós. Aqui estão os 13 passos para criar um aplicativo de sucesso.

  • Anote sua ideia de alto nível
  • Escolha entre Android ou iOS, mas não desenvolva os dois ao mesmo tempo
  • Wireframe, Mockup e Protótipo
  • Coletar feedback dos clientes
  • Crie o backend de aplicativo
  • Codifique seu frontend
  • Crie um Landing Page
  • Implemente seu Painel de Controle
  • Otimize seu aplicativo para SEO
  • Teste seu aplicativo com usuários reais
  • Publique seu aplicativo
  • Promova seu aplicativo para alcançar os usuários certos
  • Melhore seu aplicativo com o feedback do cliente

Backend as a Service – O que é?

Backend as a Service – O que é?

Backend as a Service – O que é?

Um BaaS ou mBaaS ou Backend como Serviço é uma plataforma que automatiza o desenvolvimento de backend e cuida da infraestrutura de nuvem. Utilizando um BaaS, você terceirizará as responsabilidades inerentes a manutenção e gerenciamento de servidores para um terceiro e para focar no desenvolvimento do frontend. Além disso, um BaaS fornecerá um conjunto de ferramentas para ajudá-lo a criar um código de backend e acelerar o processo de desenvolvimento. Ele está pronto para usar recursos como gerenciamento de dados, APIs, integrações de mídia social, armazenamento de arquivos e notificações push.

Abaixo, o que você aprenderá lendo este artigo:

  •  O que é um backend como serviço
  • Frontend vs. Backend
  • As diferenças entre um BaaS e um backend personalizado
  • BaaS vs. MBaaS
  • As razões para usar um backend como um serviço
  • Quando utilizar um BaaS
  • Vantagens e desvantagens de um backend como serviço
  • BaaS versus provedores de infraestrutura
  • Principais características de um backend como serviço
  • Quem deve usar um BaaS
  • Arquitetura de uma BaaS
  • Comparação de provedores de serviços de BaaS

Backend as a Service – What is a BaaS?

Backend as a Service – What is a BaaS?
Definition of BaaS

What is a backend as a service?

A BaaS or mBaaS or Backend as a Service is a platform that automates backend side development and takes care of the cloud infrastructure. Using a BaaS, you will outsource the responsibilities of running and maintaining servers to a third party and focus on the frontend or client-side development. On top of that, a BaaS will provide a set of tools to help you to create a backend code and speed up the development process. It has ready to use features such as data management, APIs, social media integrations, file storage, and push notifications.

Here is what you will learn reading this article:

  • What is a Backend as a Service
  • Frontend vs. Backend
  • The differences between a BaaS vs. a Custom Backend
  • BaaS vs. MBaaS
  • The reasons to use a backend as a service
  • When to use a BaaS
  • Advantages and Disadvantages of a backend as a service
  • BaaS versus infrastructure providers
  • Main features of a backend as a service
  • Who should use a BaaS
  • How the architecture of a BaaS looks like
  • Comparison of BaaS service providers

Setting up coding standards tools for Javascript projects

Setting up coding standards tools for Javascript projects

Have you ever wasted a lot of time merging endless files just because someone committed a file with a different code style and refused to fix it?

Have you ever had problems with your code editor because it was formatting your code on save leaving it with some weird line breaks, or using tabs instead of spaces?

Have you ever pushed a commit to fix a typo, trying to reference _MyVar instead of _myVar?

If your answer is Yes to any of the questions above, or you just don’t want to find yourself in any of these situations, stick with me.

Instant GraphQL API on Back4App

Instant GraphQL API on Back4App

After a lot of coffee and code, we are excited to announce the GraphQL support on Back4App!

Since version 3.5, Parse Server automatically provides a GraphQL API in addition to the REST API. Version 3.6 is already available as a beta at Back4App, and you can now enjoy a powerful, also instantly, generated GraphQL API, for your new or existing apps.