Skip to content

Latest commit

 

History

History
151 lines (113 loc) · 9.64 KB

README.md

File metadata and controls

151 lines (113 loc) · 9.64 KB
Raw

Contracts Example

This is an example around 3 main entities and some business rules.

Entities

  • Profile:

    • A profile can be either a client or a contractor.
    • The clients create contracts with contractors. Contractors do jobs for clients and get paid by them.
    • Each profile has a balance property.

  • Contract:

    • A contract between and client and a contractor.
    • Contracts have 3 statuses: NEW, IN_PROGRESS, TERMINATED.
    • contracts are considered active only when in status IN_PROGRESS
    • Contracts group jobs within them.

  • Job

    • A contractor gets paid for jobs by clients under a certain contract.

Business Rules

  • getContract(id: ID!): Returns the contract only if it belongs to the profile calling (either client or contractor). See the integration tests at getContract.test.ts.
  • makeProfileDeposit(input: {amount: Float}): Deposits money into the the the balance of a client, a client can't deposit more than 25% his total of jobs to pay (at the deposit moment). See the integration tests at makeProfileDeposit.test.ts.
  • payJob(id: ID!): Pay for a job, a client can only pay if his balance >= the amount to pay. The amount should be moved from the client's balance to the contractor balance. See the integration tests at payJob.test.ts.
  • listJobs(filter: { paid: Boolean }, limit: Int, nextToken: String): Get all paid/unpaid jobs for a user.
  • listContracts(filter: { unterminated: Boolean }, limit: Int, nextToken: String): Get all or terminated/unterminated contracts for a user.
  • bestProfession(filter: { start: Date, end: Date }): Returns the profession that earned the most money (sum of jobs paid) for any contactor that worked in the query time range.
  • bestClients(filter: { start: Date, end: Date }, limit: Int): Returns the clients the paid the most for jobs in the query time period. Limit query parameter should be applied, default limit is 2

You can find a complete end to end user story in the project wiki.

Getting Started

You have 2 ways to start developing:

  1. Using Gitpod, or doing a local setup manually as described in the HOW-TOs below.

Open in Gitpod

  1. Once you are there you will need to define an AWS account to deploy your stack, i.e.:
export AWS_ACCESS_KEY_ID=AKIAIOSFODNN7EXAMPLE
export AWS_SECRET_ACCESS_KEY=wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
export AWS_DEFAULT_REGION=us-west-2

  1. If it is the first time you use AWS CDK you will need to bootstrap it (i.e. cdk bootstrap aws://ACCOUNT-NUMBER/REGION).

  2. Install the top project level dependencies: npm install (not needed if you are using Gitpod)

  3. Next we need to bootstrap the project (i.e. download the dependencies): npm run bootstrap (not needed if you are using Gitpod)

  4. Next build: npm run build (not needed if you are using Gitpod)

  5. Now you have to deploy the stack: npm run deploy

  6. Finally you can access your AppSync Console in order to exercise the API (e.g.: https://us-east-1.console.aws.amazon.com/appsync/home?region=us-east-1#/apis)

Notes:

  • This project uses Lerna for building the monorepo.
  • We do not rebuild the code on deploy to improve the performance of the development workflow, so remember to run npm run build && npm run deploy.
  • We are explicitly not using the workspaces because we need the graphql-resolver-libraries to be in the node_modules subfolder for packaging.
  • There are useful GraphQL queries on the project wiki.

Testing

This project uses both unit tests (*.spec.ts) and integration tests (*.test.ts).

  • Use npm test to run the unit test all across the packages
  • Use npm run it to run the integration tests all across the packages (you need to execute npm run deploy first)

Useful commands

  • npm run lint Check lint issues on the different packages
  • npm run prettier Check prettier issues on the different packages
  • npm run regenerate-graphql-schema Regenerates the GraphQL schema from the individual schema files
  • npm run regenerate-graphql-schema-types Regenerates the GraphQL schema types in graphql-model
  • npm run build Builds the codebase
  • npm run deploy Deploys the project to AWS cloud
  • npm run destroy Removes the project from the AWS cloud (i.e. rollbacks deploy)

Technical Stack

This project mainly uses:

Questions and Answers

  • Q: Why we choose DynamoDB over for example a traditional relational database?
    • A: Because the queries that support the implementation will scale up-to levels that any relational database can reach
  • Q: Why DynamoDB?
    • A: Just for convenience (it can be built with the stack), I can do the same with MongoDB
  • Q: Is it everything optimized then?
    • A: No, just some things are currently optimized (because of time constraints) but DynamoDB will allow that optimization.
  • Q: Why we choose Lambda instead of a express-server?
    • A: Because the implementation will self-scale rather than us having to setup and manage a cluster
  • Q: Why we choose GraphQL instead of REST?
    • A: Because facilitates the implementation of the clients by leaving them to define how to use the API as well as the type system expressiveness value added
  • Q: Why not including an UI?
    • A: I can totally do it, not included due time constraints and because the AWS AppSync GraphQL console is very effective to showcase the system.
  • Q: Are all the tests included?
    • A: Nop just a few, again because of time constraints.

Entities

This project uses DynamoDB for persistence and particularly the single-table design pattern.

Entity PK SK PK1 SK1 PK2 SK2 PK3 SK3
Profile Profile#[USERNAME] Profile#[USERNAME]
Job Job#[ID] Job#[ID] Contractor#[USERNAME] Paid#[PAID] Client#[USERNAME] Paid#[PAID] Payment [DATE]
Contract Contract#[ID] Contract#[ID] Contractor#[USERNAME] Status#[STATUS] Client#[USERNAME] Status#[STATUS]

Access Patterns

  • Access Contract by ID: PK = Contract#[ID] AND SK = Contract#[ID]
  • List Non Terminated Contracts by Profile (Client or Contractor):
    • Non-Terminated Contracts for a Contractor: PK1 = Contractor#[USERNAME] AND SK1 BETWEEN Status#IN_PROGRESS AND Status#NEW
    • Non-Terminated Contracts for a Client: PK2 = Client#[USERNAME] AND SK2 BETWEEN Status#IN_PROGRESS AND Status#NEW
    • Please note that: IN_PROGRESS < NEW < TERMINATED if ordered alphabetically
  • List Unpaid Jobs:
    • Non-Terminated Contracts for a Contractor: PK1 = Contractor#[USERNAME] AND SK1 = Paid#false
    • Non-Terminated Contracts for a Client: PK2 = Client#[USERNAME] AND SK2 = Paid#false
  • Best Profession: PK3 = Payment AND SK3 BETWEEN start AND end
  • Best Clients: PK3 = Payment AND SK3 BETWEEN start AND end

HOW-TOs

How-to manual configure my environment

  1. Install the software dependencies as detailed in .gitpod.Dockerfile (e.g. aws-cdk, aws-sam-cli, etc.)
  2. Use npm install to download the lerna dependencies used in the following steps
  3. Use npm run bootstrap to bootstrap the project (i.e. install all the dependencies)
  4. Use npm run build to build it

Regenerate the GraphQL Schema

The schema is generated from different independent schema files split by type (i.e. Profile.graphql, Contract.graphql, etc.). To generate the combined schema file we use graphql-schema-utilities and specifically a script named regenerate-graphql-schema so execute npm run regenerate-graphql-schema in order to regenerate schema.graphql

Note: We do not do it automatically at the stack deploy in order to not slowdown every single deploy and/or to avoid un-intended changes to be produced automatically since the schema doesn't change so frequently.

Regenerate the GraphQL Schema Types

This project generates Typescript types for the GraphQL API operations. In order to regenerate those types you must execute npm run regenerate-graphql-schema-types