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…

 


AWS – Reduzir Custos S3

AWS – Reduzir Custos S3

Como reduzir os custos do S3 – Simple Storage Service?

O Amazon Simple Storage Service (Amazon S3) é um dos serviço mais populares serviços Amazon Web Services (AWS). Para a maioria das empresas, o S3 é um maiores gastos entre todos os serviço as da AWS. Neste artigo, discutiremos diferentes abordagens para reduzir os custos do Amazon S3 e melhorar sua margem.


AWS – Como reduzir os custos de transferência de dados?

AWS – Como reduzir os custos de transferência de dados?

Como reduzir custos de transferência de dados na AWS?

Qualquer organização que utilize a AWS deve ter um plano de gerenciamento de custos na nuvem – se você já excedeu ou não o orçamento, a melhor hora para começar é agora. Aqui estão cinco procedimentos práticos que ajudarão você a reduzir os custos de transferência de dados (data transfer ou bandwith).

  1. Conecte os endpoints ou Cloudflare
  2. IPs privados versus IPs elásticos
  3. Utilize uma AZ única
  4. Implemente APIs no formato GraphQL
  5. Use o Cloudfront


AWS – Como reduzir os custos de EBS

AWS – Como reduzir os custos de EBS

EBS — Como reduzir os custos?

A maioria das empresas está gastando muito mais que o necessário em armazenamento EBS! Ao criar aplicações e cargas de trabalho na AWS, é preciso controlar o modelo econômico de sua arquitetura. Abaixo, os cinco passos para se reduzir os custos de EBS junto a AWS.

  1. Armazenagem do tipo magnético é 50% mais barata
  2. Reduza o tamanho de volume superdimensionados
  3. Termine instâncias (apenas desligar não é suficiente)
  4. Armazenamento efêmero
  5. Use o S3 para fazer backup de dados

O artigo completo está disponível em:

How to reduce AWS costs?


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.


AWS – Reduzir Custos EC2

AWS – Reduzir Custos EC2

Como reduzir os custos da AWS – EC2 – Elastic Compute Cloud

O presente artigo detalha com a Back4App reduziu os custos da AWS em mais de USD 500 mil. Aqui está um resumo das ações para se reduzir os custos de EC2:

  1. Desligar instâncias não utilizadas
  2. Reduzir instâncias superdimensionadas
  3. Utilizar instâncias reservadas – Economia de até 70%
  4. Utilizar o marketplace da AWS para adquirir instâncias reservadas
  5. Atualize as instâncias para geração mais moderna
  6. Utilizar instâncias SPOT – Economia de até 90% 
  7. Implementar rotinas de auto-scaling
  8. Selecione a região correta da AWS para minimizar custos

O artigo completo está disponível em inglês abaixo.

How to reduce AWS costs?


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.