- About the Project
- Key Features
- Technical Highlights
- Architecture
- Technology Stack
- Getting Started
- Usage
- Team
- Development Workflow
- Contributing
- License
Kono is a production-deployed crypto trading simulator that enabled users to practise trading with Β£10,000 in virtual assets. Built with enterprise-grade architecture, the platform demonstrates proficiency in modern full-stack development, real-time systems, and cloud infrastructure. The platform was successfully launched in March 2025 and served real users in production.
- Risk-free learning: Users mastered trading strategies without financial risk
- Real market simulation: Live price feeds from 163+ cryptocurrencies via WebSocket
- Gamification: Global rankings and performance tracking increased user engagement
- Scalable architecture: Successfully supported concurrent users with Redis caching and microservices
- Type-safe development: Full TypeScript implementation with strict type checking
- Modern React patterns: Hooks, Context API, custom hooks for WebSocket management
- Performance optimisation: Code splitting, lazy loading, memoisation
- Responsive design: Mobile-first approach with Tailwind CSS
- Internationalisation: i18n support for English and Korean markets
- RESTful API design: Structured endpoints with proper HTTP semantics
- Real-time data: WebSocket implementation for live price feeds
- Caching strategy: Redis for high-performance data retrieval
- Authentication: OAuth2 integration with secure JWT handling
- Rate limiting: Protection against abuse and API throttling
- CI/CD Pipeline: GitHub Actions for automated testing and deployment
- Cloud hosting: AWS infrastructure (EC2, RDS, Elastic Beanstalk)
- Monitoring: Prometheus + Grafana for observability
- Database: MariaDB for transactional data with optimised queries
βββββββββββββββ ββββββββββββββββ βββββββββββββββ
β React βββββββΊβ Spring Boot βββββββΊβ MariaDB β
β Frontend β β Backend β β Database β
βββββββββββββββ ββββββββββββββββ βββββββββββββββ
β β
β βΌ
β ββββββββββββββββ
β β Redis β
β β Cache β
β ββββββββββββββββ
β
βΌ
βββββββββββββββ
β Upbit β ββββ Real-time Price Updates (WebSocket)
β API β
βββββββββββββββ
Key Design Decisions:
- Direct integration with Upbit WebSocket API for real-time cryptocurrency prices
- Stateless API for horizontal scaling
- Database optimisation with proper indexing
- Redis caching strategy for frequently accessed data
Prerequisites
Ensure you have the following installed:
- Node.js >= 18.0.0
- npm >= 9.0.0 or yarn >= 1.22.0
- Git for version control
Installation
# Clone the repository
git clone https://github.com/hyogshin/kono-client.git
cd kono-client
# Install dependencies
npm install
# or using yarn
yarn install
# Set up environment variables
cp .env.example .env
# Edit .env with your configuration
# Start development server
npm run dev
# or
yarn devThe application will be available at http://localhost:5173
Environment Variables
VITE_API_URL=your_backend_api_url
VITE_WS_URL=your_websocket_urlDevelopment Commands
# Start development server with hot reload
npm run dev
# Build for production
npm run build
# Preview production build locally
npm run preview
# Run linter
npm run lint
# Run type checking
npm run type-checkKey User Flows
- Sign up β Receive Β£10,000 virtual assets
- Browse markets β View real-time prices for 163+ cryptocurrencies
- Execute trades β Buy/sell with instant balance updates
- Track portfolio β Monitor performance and transaction history
- Compete globally β Climb the leaderboards
A collaborative 5 member team that successfully delivered a production-grade trading platform in 11 weeks.
| Member | Role | Key Contributions |
|---|---|---|
![]() Hayden |
Frontend Lead, DevOps & PM | WebSocket real-time integration, frontend architecture |
![]() Jenny |
Backend Engineer | Ranking API, Redis caching, database optimisation |
![]() Keen |
Full-stack Engineer | Trading logic, API integration, full-stack features |
![]() Sep |
Backend Engineer | OAuth2 authentication, S3 architecture, API security |
![]() June |
DevOps Engineer | CI/CD pipeline, monitoring |
We follow industry-standard Agile methodologies with structured sprint cycles:
| Sprint | Period | Focus | Key Deliverables |
|---|---|---|---|
| Planning | 17/02 - 02/03/2025 | Service planning & technical review | Service concept, technology stack selection |
| Sprint 1 | 03/03 - 20/03/2025 | MVP development setup | API design, ERD, architecture, GitHub/server setup, Swagger documentation, CI/CD pipeline |
| Sprint 2 | 24/03 - 06/04/2025 | Core feature development | MVP completion, 1st production deployment (31/03) |
| Sprint 3 | 07/04 - 20/04/2025 | Promotion & iteration | User feedback integration, performance optimisation, feature updates |
| Sprint 4 | 21/04 - 03/05/2025 | V2 release & maintenance | Major update deployment, final optimisations, presentation prep |
We welcome contributions from the community! Here's how you can help:
Reporting Issues
- Use the issue tracker
- Provide clear reproduction steps
- Include environment details (OS, browser, Node.js version)
- Add screenshots or error logs if applicable
Submitting Pull Requests
- Fork the repository
- Create a feature branch:
git checkout -b feat/amazing-feature - Commit your changes:
git commit -m 'feat: add amazing feature' - Push to the branch:
git push origin feat/amazing-feature - Open a Pull Request with a clear description
Commit Convention
We follow Conventional Commits:
| Type | Description |
|---|---|
feat |
New feature implementation |
fix |
Bug fix |
docs |
Documentation updates |
style |
Code formatting (no logic changes) |
refactor |
Code refactoring |
test |
Adding or updating tests |
chore |
Build process or auxiliary tool changes |
perf |
Performance improvements |
This project is currently in active development. All rights reserved by the Kono team.
For commercial use or collaboration inquiries, please contact the team members.











