gatsby-starter-hello-world VS artwork

When I was learning web development I built my portfolio site using the Gatsby-starter-hello-world template without using Typescript. Typescript was on my things-to-learn bucket list but never got to it until I started working professionally. After learning Typescript I cannot imagine building anything without it!

{ "name": "gatsby-starter-hello-world", "private": true, "description": "A simplified bare-bones starter for Gatsby", "version": "0.1.0", "license": "MIT", "scripts": { "build": "gatsby build", "develop": "gatsby develop", "format": "prettier --write \"**/*.{js,jsx,json,md}\"", "start": "npm run develop", "serve": "gatsby serve", "clean": "gatsby clean", "test": "echo \"Write tests! -> https://gatsby.dev/unit-testing\" && exit 1" }, "dependencies": { "gatsby": "^2.18.4", "react": "^16.12.0", "react-dom": "^16.12.0" }, "devDependencies": { "prettier": "^1.19.1" }, "repository": { "type": "git", "url": "https://github.com/gatsbyjs/gatsby-starter-hello-world" }, "bugs": { "url": "https://github.com/gatsbyjs/gatsby/issues" }}

gatsby new [YOUR-PROJECT-NAME] https://github.com/gatsbyjs/gatsby-starter-hello-world

They developed a solution, and open sourced it as GraphQL.

I'm using the Official GraphQL, HowToGraphQL and several other websites to curate my own notes on GraphQL.

Your cloud architecture, system design and project leadership skills should be more important than language specifics when interviewing. That being said, I recommend learning about Node.js internals (e.g. the event loop); ES6+ language improvements; and some trending tools and libraries like TypeScript, Docker, Serverless Framework and GraphQL. Know enough about Express and serverless functions justify using one over the other when designing a system.

API stands for Application Programming Interface. APIs define how two pieces of software can connect and talk to each other. If your application were a big company, your API's job would be to keep in touch with external parties (customers or company partners, for example). Most APIs are organized around some standard, like REST or GraphQL, so that everybody knows how to use them.

GraphQL is developed by Facebook initially for their mobile app and has been adopted widely across web apps.

Last week, I built a microservice: a resource for a section of the landing page of the platform, which renders from a database loaded with data. In technical terms, I built and consumed an API. I used Dynamo DB (a database provided by Amazon Web Services (AWS))) to store my data, creating a table with desired fields for me to use in populating my table. GraphQL was used as playground for me to query and mutate my database. i.e. a way of creating, reading, updating and deleting information from the database, a process technically known as CRUD.

GraphQL, if you are not familiar, is a way of having APIs which are query-able similar to SQL for a database.

GraphQL.org

More than that, it's a good idea for storing non-sensitive data across the application. It might be a Redux or GraphQL state or some global app-wide variables. On the other hand, you shouldn’t use that for storing tokens and secrets, as the storage is not encrypted in any way.

AWS AppSync is a fully managed GraphQL API which is a serverless offering by AWS.