In this tutorial, I will walk you through building a quick static site by doing a static build using ReactJS & create-react-app, then show you how to deploy that static site on AWS using S3 buckets as well as how to cache it & add SSL certificates with CloudFront CDN & Certificate Manager. - Source: dev.to / 27 days ago

Because of that, we'll need a valid public certificate, which we can request in Certificate Manager for free. - Source: dev.to / 9 months ago

Check out Amazon certificate manager (ACM) . Essentially, you can have free public certificates for use with Amazon services with auto renewal. You don't have to use route 53 as your registrar but you do have to prove domain ownership in order to get certificates. Source: over 1 year ago

AWS Certificate Manager for securing the website and managing the ssl certificate. - Source: dev.to / over 1 year ago

Now we need to have the site secure with SSL/TLS. So we can either add a load balancer and associate it with a certificate from AWS ACM or directly create a certificate on the instance. Let's do the latter using OpenSSL. - Source: dev.to / over 1 year ago

'id' data type and field to help support caching: https://graphql.org/learn/caching/. Source: over 1 year ago

> Take a look at this. I repeat: client-side caching is not a problem, even with GraphQL. The technical problems regarding GraphQL's blockers to caching lies in server-side caching. For server-side caching, the only answer that GraphQL offers is to use primary keys, hand-wave a lot, and hope that your GraphQL implementation did some sort of optimization to handle that corner case by caching results. Don't take my... - Source: Hacker News / about 2 years ago

> Checkout Relay.js: https://relay.dev/ Relay is a GraphQL client. That's the irrelevant side of caching, because that can be trivially implemented by an intern, specially given GraphQL's official copout of caching based on primary keys [1], and doesn't have any meaningful impact on the client's resources. The relevant side of caching is server-side caching: the bits of your system that allow it to fulfill... - Source: Hacker News / about 2 years ago

This is clever! Can anyone help me understand how this lines up with the original value proposition of GraphQL? I was under the impression that the Big Idea behind GraphQL was, amongst other things, client-side caching[1]. I’m probably missing some nuance here, so bear with me: if your GraphQL client is caching properly, then what would this syntax give a developer that a URL query parameter parser couldn’t? [1]... - Source: Hacker News / about 3 years ago