DEV Community: guigoncalves

How to chose an AWS database

guigoncalves — Sat, 21 Jan 2023 16:38:32 +0000

In order to ensure optimal performance, scalability and cost-effectiveness, selecting the appropriate database type is crucial for any application. This text aims to explore the various database options provided by Amazon Web Services (AWS) and provide guidance on when each should be used.

Introduction to the options

RDS

Relational Database Service (RDS). RDS is a fully managed service that makes it easy to set up, operate, and scale a relational database in the cloud. It supports popular database engines such as MySQL, PostgreSQL, and Oracle. RDS is a great choice for applications that need to store structured data and support complex queries and transactions.

DocumentDB

DocumentDB, also known as AWS MongoDB, is a fully managed, fast, and highly available document database that makes it easy to store, manage, and query semi-structured data. DocumentDB is a great choice for applications that need to store and query semi-structured data, such as JSON documents. It is also a good choice for applications that need to scale horizontally, as it supports automatic sharding and partitioning.

DynamoDB

DynamoDB is a fully managed, highly scalable, and fast NoSQL database service that supports both document and key-value data models. DynamoDB is a great choice for applications that need to store and retrieve large amounts of data with low latency. It supports automatic sharding and partitioning, which makes it easy to scale horizontally. Additionally, it supports secondary indexes, which allows you to query the data in different ways.

Amazon Elasticsearch Service

Amazon Elasticsearch Service, which is a fully managed service that makes it easy to deploy, operate, and scale Elasticsearch clusters. It is a great choice for applications that need full-text search and analytics capabilities. Amazon Redshift, which is a fully managed data warehouse service that makes it easy to analyze large amounts of data using SQL and your existing business intelligence tools.

Object Storage

An example is Amazon Simple Storage Service (S3) is an object storage service, which allows you to store and retrieve any amount of data from anywhere on the web. S3 is a great choice when you need to store and retrieve large amounts of unstructured data, such as images, videos, audio, and text files.

How to chose one or another

you should consider factors such as the type of data you need to store, the size of your data, and the type of queries you will be running.
Relational databases such as RDS are a great choice for applications that need to store structured data and support complex queries and transactions. NoSQL databases such as DocumentDB and DynamoDB are a great choice for applications that need to store and query semi-structured data or handle large amounts of data with low latency.
Additionally, Amazon Elasticsearch Service and Amazon Redshift are great options for applications that need full-text search and analytics capabilities and S3 is perfect in case you want to store objects, such as videos, files or images.

GraphQL basics and how it differs from REST

guigoncalves — Sat, 14 Jan 2023 19:26:54 +0000

GraphQL is a query language for your API that was developed by Facebook in 2012. It allows the client to define the structure of the data it needs, and the server will return only the requested data. In this way, it differs from REST (Representational State Transfer) which is an architectural style for building web services.

Advantages

One of the main advantages of GraphQL is its flexibility. With REST, the client must make multiple requests to different endpoints to retrieve all the necessary data, which can lead to over-fetching or under-fetching of data. With GraphQL, the client can specify exactly what data it needs in a single request, and the server will return only that data. This allows for more efficient data retrieval and reduces the amount of data transfer over the network.

Another advantage of GraphQL is its ability to handle complex and nested data. With REST, retrieving nested data requires multiple requests to different endpoints, which can be time-consuming and difficult to manage. With GraphQL, the client can specify exactly what nested data it needs in a single request, and the server will return that data in a single response.

Real Time Subscription

GraphQL subscriptions allow for real-time updates by enabling the client to subscribe to specific events or changes and receive updates over a WebSocket connection as the data changes. This feature is supported by most of the GraphQL implementations, and can be implemented using a GraphQL client library such as Apollo Client.

Disadvantages

However, GraphQL does have some disadvantages as well. One of the main disadvantages is that it can be more difficult to cache the data in a GraphQL API compared to a REST API. This is because the structure of the data returned by a GraphQL API can vary depending on the client's request, whereas the structure of the data returned by a REST API is fixed. Additionally, GraphQL does not have as wide of support as REST, and may not be as well suited for certain types of applications.

Conclusion

In conclusion, GraphQL is a powerful tool for building APIs that is particularly well suited for applications that require flexible, efficient data retrieval and real-time updates. However, it does have some disadvantages and may not be the best choice for every application. It is important to weigh the pros and cons of both GraphQL and REST before deciding which is the best option for your specific use case.

Versioning GraphQL and Rest API's

guigoncalves — Thu, 12 Jan 2023 13:32:27 +0000

When building an API, it's important to consider how you will handle versioning. The ability to evolve your API over time while maintaining backwards compatibility is crucial for ensuring a smooth experience for your users. In this article, we'll go over some best practices for versioning a GraphQL API and a REST API, and how to implement them with code snippets.

Handling versioning with version on header:
One common approach to versioning API is to use a field or header to specify the version. This allows clients to specify which version of the API they want to use, and the server can respond accordingly. For example, a client could include a version field in their query, and the server would use that to determine which schema/resource to use.

GraphQL example:

const express = require("express");
const graphqlHTTP = require("express-graphql");

const app = express();

const schemaV1 = /* your v1 schema */;
const schemaV2 = /* your v2 schema */;

app.use("/graphql", graphqlHTTP((req) => {
    const version = req.headers["version"];
    const schema = version === "v1" ? schemaV1 : schemaV2;
    return {
        schema,
        graphiql: true
    };
}));

In this example, the server is using the version header passed in by the client to determine which schema to use.

Handling versioning with url:
A common approach to versioning REST API's is to include the version number in the URL. For example, you could have /v1/resource and /v2/resource as your endpoint for different versions of your API.

const express = require("express");
const app = express();

app.use("/v1/resource", (req, res) => {
    // v1 resource endpoint
});

app.use("/v2/resource", (req, res) => {
    // v2 resource endpoint
});

In this example, the server is using different endpoint for different versions of your API.

Best practices:

Avoid making breaking changes to the API
Introduce new fields or types, or deprecate old fields or types in GraphQL API
Introduce new endpoints or deprecate old endpoints in REST API
Provide a migration path for existing clients
Document the API clearly and communicate changes to users
Provide release notes and detailed documentation for each field, type or endpoint.