Usage and getting started

Introduction
Yap is a microservices API gateway that shines at the heart of any microservices or serverless architecture, which aims to be a smaller, more expressive, and more robust foundation for API management and automation workflows with low-code approach and security.
1. GraphQL schema
GraphQL schema define the structure of data that clients can query. In this example, we'll create a server for querying a collection of books by title and author.
1
# Comments in GraphQL strings (such as this one) start with the hash (#) symbol.
2
​
3
# This "Book" type defines the queryable fields for every book in our data source.
4
type Book {
5
  title: String
6
  author: String
7
}
8
​
9
# The "Query" type is special: it lists all of the available queries that
10
# clients can execute, along with the return type for each. In this
11
# case, the "books" query returns an array of zero or more Books (defined above).
12
type Query {
13
  books: [Book]
14
}
Copied!
Resolvers
Yap is a resolvers framework work only on GraphQL. Each resolvers receives a Yap Context object that encapsulates an incoming HTTP AWS Lambda trigger message and the corresponding response to that message, and arguments from GraphQL
ctx is often used as the parameter name for the context object similar to Koa or ExpressJS.
1
const resolvers = {
2
  Query: {
3
    books: async (parent: any, args: Argument, context: Context, info: Info) => {
4
      // ...
5
    },
6
  },
7
};
Copied!
Connectors
API management is the process of creating and publishing web application programming interfaces (APIs), enforcing their usage policies, controlling access, nurturing the subscriber community, collecting and analyzing usage statistics, and reporting performance. API management provides the core competencies to ensure a successful API program through developer engagement, business insights, analytics, security, and protection.
1
import { Info, Argument, Context } from "@youngapp/yap";
2
import { DataConnector } from "@youngapp/rds";
3
import conn from "./connections.ts";
4
​
5
// Connections
6
const dataConnector = new DataConnector(...conn.DATAQ);
7
​
8
const resolvers = {
9
  Query: {
10
    books: async (parent: any, args: Argument, context: Context, info: Info) => {
11
      return dataConnector.findOne({ table: 'books' });
12
    },
13
  },
14
};
Copied!
Policies
It’s important to realize that exposing your API services makes easier to manage them. Why? 
When you keep your API policies separate, you ensure control over their performance and delivery. Independence is the key to your API policies’ success and future deployment.
Further, it’s important to modernize your API strategy. 

Keeping API well-structured prevents overexposing API that results in stucking in little things. Unifying API policies simplifies API management.
1
<check-header name="Authorization" failed-check-httpcode="401" failed-check-error-message="Not authorized" ignore-case="false">
2
    <value>f6dc69a089844cf6b2019bae6d36fac8</value>
3
</check-header>
Copied!
Application
Yap application is an object containing an array of middleware functions and policies which are composed and executed in a stack-like manner upon request. Yap is similar to many other middleware systems that you may have encountered such as Koa, Connect.
The obligatory workflow application:
1
import { Yap } from "@youngapp/yap";
2
import typeDefs from "./schema.graphql";
3
import resolvers from "./resolvers.ts";
4
import policies from "./policies.xml";
5
​
6
// The Yap constructor requires three parameters: your schema
7
// definition, policies and your set of resolvers.
8
const app = new Yap({ typeDefs, resolvers, policies });
9
​
10
// A simple typescript node project for AWS Lambda.
11
exports.handler = app.handler;
Copied!
Usage with TypeScript
The Yap for JavaScript bundles TypeScript definition files for use in TypeScript projects and to support tools that can read .d.ts files. Our goal is to keep these TypeScript definition files updated with each release for any public API.
Pre-requisites
Before you can begin using these TypeScript definitions with your project, you need to make sure your project meets a few of these requirements:
Use TypeScript v2.x
Includes the TypeScript definitions for node. You can use npm to install this by typing the following into a terminal window:
1
 npm install --save-dev @types/node
Copied!
If you are targeting at es5 or older ECMA standards, your tsconfig.json has to include 'es5' and 'es2015.promise' under compilerOptions.lib. See tsconfig.json for an example.
Installing
It's an official version for JavaScript, available for Node.js backends, Serverless and AWS Lambda.
With yarn
1
yarn install yap
Copied!
With npm
1
npm install yap
Copied!
Hello API
Yap application is an object containing resolvers functions and policies which are composed and executed in a stack-like manner upon request. Yap is similar to many other middleware systems that you may have encountered such as Koa, Connect.
Minimalist application with http.Server
1
import { Yap } from "@youngapp/yap";
2
import typeDefs from "./schema.graphql";
3
import resolvers from "./resolvers.ts";
4
​
5
// Your schema definition and resolvers GraphQL
6
const app = new Yap({ typeDefs, resolvers });
7
​
8
app.listen(3000, () => {
9
  console.log('Example app listening on port 3000!')
10
})
Copied!
(npx comes with npm 5.2+ and higher, see instructions for older npm versions)
Then open http://localhost:3000/ to see your api.
 When you’re ready to deploy to production, create a minified bundle with npm run build or yarn build.
1
my-api
2
├── README.md
3
├── node_modules
4
├── package.json
5
├── .gitignore
6
├── serverless.yml
7
├── tslint.json
8
├── tsconfig.json
9
└── src
10
    ├── policies.xml
11
    ├── schema.graphql
12
    ├── resolvers.ts
13
    ├── scenarios.yaml
14
    └── app.ts
Copied!
Yap community
Application and resolvers
Last modified 1yr ago
Copy link
Contents