https://github.com/dmuth/ticket-sales

A proof of concept node.js server I put together to handle locking and claiming of seats at an event.
https://github.com/dmuth/ticket-sales

Last synced: 8 months ago
JSON representation

A proof of concept node.js server I put together to handle locking and claiming of seats at an event.

• Host: GitHub
• URL: https://github.com/dmuth/ticket-sales
• Owner: dmuth
• License: other
• Created: 2013-05-24T04:57:23.000Z (about 13 years ago)
• Default Branch: main
• Last Pushed: 2020-09-03T22:23:23.000Z (almost 6 years ago)
• Last Synced: 2025-04-12T14:51:26.757Z (about 1 year ago)
• Language: JavaScript
• Size: 25.4 KB
• Stars: 4
• Watchers: 4
• Forks: 2
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • License: LICENSE.md

Awesome Lists containing this project

README

          
# ticket-sales

A proof of concept node.js server I put together to handle locking and claiming of seats at an event.

## Installation

Make sure you have node.js on your system of at least version 0.6.  If you're on a Mac 

and have Homebrew installed, just type `brew install node`.

Next, clone this project:

    git clone git@github.com:dmuth/ticket-sales.git

Install the NPM modules:

    npm install

    

Run the unit tests (if you like):

    npm test

    

Play around with the test script (if you like):

    ./test.sh

    

To start the server:

    node ./main.js

    

## Event data structure

This is a standard Javascript object:

    {

    name: "name of the event",

    _comment: "Comment for programmers inspecting this data structure",

    sections: { 

        orchestra: { // A sample section. We can have as many of these as we want.

            a: { // Row A. This can be an arbitrary string.

                "1": { // Our individual seat

                    status: "available" // By default the status is available.  Can also be "locked" and "sold"

                    expires: (integer) // When a locked seat expires. This is a time_t.

                }

            }

        }

    }

## HTTP API Endpoints

- `/` - Hello world!

- `/seat/check/:section/:row/:seat` - Check if a certain seat is available

- `/seat/lock/:section/:row/:seat` - Lock a certain seat

- `/seat/claim/:section/:row/:seat` - Claim a locked seat that has been sold externally

- `/seat/unlock/:section/:row/:seat` - Unlock a seat

- `/seat/num_available` - How many seats are available?

## Future enchancements

- Find rows of seats that are together

## Scaling up

This will work only on a single server for now.  In the future, I would look into using Dyanmo DB

instead of internal data structures for storing event seats.  The round trip time to Dynamo should 

be on the order of 1-2 milliseconds, which is plenty fast enough for intended use.