https://github.com/rahad123/partition-for-data-optimization

https://github.com/rahad123/partition-for-data-optimization

docker docker-compose knex mocha postgresql typescript

Last synced: 9 days ago
JSON representation

• Host: GitHub
• URL: https://github.com/rahad123/partition-for-data-optimization
• Owner: rahad123
• Created: 2024-02-21T16:59:49.000Z (9 months ago)
• Default Branch: main
• Last Pushed: 2024-02-26T17:57:01.000Z (9 months ago)
• Last Synced: 2024-10-11T22:41:30.006Z (about 1 month ago)
• Topics: docker, docker-compose, knex, mocha, postgresql, typescript
• Language: TypeScript
• Homepage:
• Size: 40 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Partition for Data Optimization

#### A few days ago, I faced sluggish search performance when querying a key in a table housing millions of indexed records, despite having optimized the indexing. However, employing range partitioning—a type of horizontal partitioning—proved to be the solution. By partitioning the data into distinct segments, the search process became more efficient and manageable.

## Requirements

- Docker ([Documentation](https://www.docker.com/get-started/))

- Docker Compose

- Postgresql ([Download](https://www.postgresql.org/))

- Node.js ([Download](https://nodejs.org/en))

- NPM (Will be download with Node.js)

#### There is one part of this project.

- Backend - Nodejs + Postgresql ( http://localhost:3000 )

## Installation

- Copy .env.example to .env

```

 cp .env.example .env

```

### Run Docker

```

npm run dev:docker

```

If you need to Re-Run docker, you should remove the container which was created before

```

npm run dev:docker:down

```