Rubber Ducky for Engineers - How to use ChatGPT as a Search Engine
There sits a yellow, small rubber ducky with a cowboy hat on. You know, the ones you might see at a carnival for some silly little game to win a prize of a giant stuffed unicorn.
There sits a yellow, small rubber ducky with a cowboy hat on. You know, the ones you might see at a carnival for some silly little game to win a prize of a giant stuffed unicorn.
We are living in a time where things are buzzing – buzzing with words like AI (artificial intelligence) or ML (machine learning). Many think “AI is taking over the world!” No…AI is not taking over but it is certainly changing the way we are doing things. In this article, we’ll give a bird’s eye overview to this “buzz buzz” about AI, different applications for AI, and how you can get started.
Apollo Federation is an open source architecture that is designed to help your organization implement and orchestrate GraphQL services at scale. That's a sentence with a lot of words, but why do we care? Why is it useful? In this article, we'll take a closer look at the Whys and the WTFs of Apollo Federation.
One of the most genius things that the creators of GraphQL ever did was give us GraphiQL. GraphiQL is an in-browser tool that you can use to send queries to a GraphQL API. To start working with GraphQL, you don't have to build a server. You don't have to write a parser. You don't have to set up a client solution. Instead, you can just start sending queries.
Many of the most common misconceptions about GraphQL have to do with the whereabouts of data. It's often thought of as a database. It's often thought of as a replacement to REST. It's often associated with a certain type of database.
One popular misconception about GraphQL is that you have to tear down all of your REST APIs in order to build a GraphQL server. The flexibility of GraphQL allows you to use all of your favorite REST data sources while enjoying the organizational benefits of a GraphQL schema. In this article, we'll take a closer look at how we can incorporate the data from a REST API into an existing GraphQL server.
When you build a GraphQL API, you provide a lot of freedom and flexibility to your clients. They have the flexibility to query data from multiple sources in a single request. They also have the ability to request large amounts of related, or connected, data in a single request. Left unchecked, your clients could have the capability of requesting too much from your service. Not only will the strain of large queries affect server performance, it could also take your service down entirely. Some clients might do this unintentionally, whereas other clients might have more malicious intent. Either way, you need to put some safeguards in place and monitor your server’s performance in order to protect against large or malicious queries.
GraphQL fields can return lists and objects, but of course, they can also return singular values. These are called scalar types. A scalar in computer science represents a single variable, an atomic unit that can hold one value at a time. A lot of data for our apps falls into the scalar category: names, email addresses, phone numbers. These are leaves of the tree: lone values instead of objects.