Dynamic Booking and Proxy System
Budget: €1,500 – €3,000 EUR
Project Title:
Automated Booking and Scheduling Bot with Dynamic Weekly Timing and Proxy Management
Project Description:
We are building a server-controlled automation system that manages booking tasks, timing patterns, and multiple user sessions (operators).
The goal is to create a backend service that can:
Distribute tasks across multiple connected workers or operators
Handle real-time booking and queue management
Automatically generate dynamic time slots each week based on custom rules
Optionally use proxy pools (legally acquired) for network routing and redundancy
Implement full error handling and recovery, including temporary network failures such as 502, 503, and 504
Core Features and Requirements:
Central Server Control
The main server manages all bots (workers) and assigns tasks automatically.
Admin can view and control all active workers (permissions, sessions, etc.).
Workers connect securely via API or socket.
Dynamic Weekly Schedule System
Each week can have a different timing pattern for when booking attempts occur.
Example:
Monday: 10 bookings at 10:00, then 5 more 5 minutes later
Wednesday: 8 bookings every 3 minutes between 09:00 and 10:00
These rules must be configurable through an admin dashboard.
The system automatically generates time slots based on these patterns.
Each slot can have multiple capacities (e.g., allow more than one booking per slot).
Queue and Branching Logic
When a customer or booking request enters:
If there is available capacity, confirm booking.
If not, place it in a waiting queue.
When a cancellation or new opening occurs:
Automatically promote the first in the queue.
Notify relevant users or operators.
Operators can accept or reject new bookings with a timeout.
All logic must be transaction-safe using database locks or Redis.
Proxy Pool Management (Optional but Important)
Support multiple proxy pools (HTTP, SOCKS5, or internal network).
Each campaign can be linked to one or more proxy pools.
Proxies should be used in round-robin, random, or sticky rotation.
Log every request with its proxy and result.
All proxies must be legally obtained. This system must not be used to bypass site protections.
Error Handling and Retry System
Handle all typical web errors gracefully: 502, 503, 504, 429, and timeouts.
Include retry logic with exponential backoff and a circuit breaker system.
Log all failed attempts.
If an endpoint fails repeatedly, pause requests for a set duration.
Notifications and Alerts
Notify customers when bookings are confirmed or promoted from waiting.
Notify operators when they receive new assignments.
Support push, email, or internal notifications.
Admin Dashboard
Manage sites, customers, schedules, slots, operators, and proxy pools.
View queues, available slots, and statistics such as:
Current active slots
Waiting queue length
Average wait time
Proxy pool health
Option to trigger slot generation manually or schedule it daily.
Database Overview (Simplified):
laundries: site or location data with capacity
customers: client details
reservations: booking status, queue position, assigned operator
slots: generated time slots
schedule_patterns and entries: weekly timing rules
proxy_pools and campaign_proxies: proxy lists and assignments
Suggested Tech Stack:
Backend: Node.js (Express/NestJS) or Python (FastAPI/Django)
Database: PostgreSQL with transactions
Cache/Lock: Redis
Scheduler: Node cron or Celery Beat
Frontend (optional): React or Next.js
Deployment: Docker
Deliverables:
Fully working backend service (API, scheduler, and worker logic)
Database schema and migration scripts
Basic admin dashboard for management
Documentation (README) explaining:
System setup
How to define weekly schedules
How proxy pools are configured and logged
Important Notes:
This project must not be used to violate the Terms of Service of any third-party website.
Proxy usage is allowed only for load balancing and network redundancy.
Focus of the project is on automation, scheduling, and coordination, not on bypassing website security.
Budget and Timeline:
Please provide your estimated timeline and budget.
Looking for developers experienced in backend architecture, scheduling systems, PostgreSQL, Redis, and proxy or worker coordination.
Automated Booking and Scheduling Bot with Dynamic Weekly Timing and Proxy Management
Project Description:
We are building a server-controlled automation system that manages booking tasks, timing patterns, and multiple user sessions (operators).
The goal is to create a backend service that can:
Distribute tasks across multiple connected workers or operators
Handle real-time booking and queue management
Automatically generate dynamic time slots each week based on custom rules
Optionally use proxy pools (legally acquired) for network routing and redundancy
Implement full error handling and recovery, including temporary network failures such as 502, 503, and 504
Core Features and Requirements:
Central Server Control
The main server manages all bots (workers) and assigns tasks automatically.
Admin can view and control all active workers (permissions, sessions, etc.).
Workers connect securely via API or socket.
Dynamic Weekly Schedule System
Each week can have a different timing pattern for when booking attempts occur.
Example:
Monday: 10 bookings at 10:00, then 5 more 5 minutes later
Wednesday: 8 bookings every 3 minutes between 09:00 and 10:00
These rules must be configurable through an admin dashboard.
The system automatically generates time slots based on these patterns.
Each slot can have multiple capacities (e.g., allow more than one booking per slot).
Queue and Branching Logic
When a customer or booking request enters:
If there is available capacity, confirm booking.
If not, place it in a waiting queue.
When a cancellation or new opening occurs:
Automatically promote the first in the queue.
Notify relevant users or operators.
Operators can accept or reject new bookings with a timeout.
All logic must be transaction-safe using database locks or Redis.
Proxy Pool Management (Optional but Important)
Support multiple proxy pools (HTTP, SOCKS5, or internal network).
Each campaign can be linked to one or more proxy pools.
Proxies should be used in round-robin, random, or sticky rotation.
Log every request with its proxy and result.
All proxies must be legally obtained. This system must not be used to bypass site protections.
Error Handling and Retry System
Handle all typical web errors gracefully: 502, 503, 504, 429, and timeouts.
Include retry logic with exponential backoff and a circuit breaker system.
Log all failed attempts.
If an endpoint fails repeatedly, pause requests for a set duration.
Notifications and Alerts
Notify customers when bookings are confirmed or promoted from waiting.
Notify operators when they receive new assignments.
Support push, email, or internal notifications.
Admin Dashboard
Manage sites, customers, schedules, slots, operators, and proxy pools.
View queues, available slots, and statistics such as:
Current active slots
Waiting queue length
Average wait time
Proxy pool health
Option to trigger slot generation manually or schedule it daily.
Database Overview (Simplified):
laundries: site or location data with capacity
customers: client details
reservations: booking status, queue position, assigned operator
slots: generated time slots
schedule_patterns and entries: weekly timing rules
proxy_pools and campaign_proxies: proxy lists and assignments
Suggested Tech Stack:
Backend: Node.js (Express/NestJS) or Python (FastAPI/Django)
Database: PostgreSQL with transactions
Cache/Lock: Redis
Scheduler: Node cron or Celery Beat
Frontend (optional): React or Next.js
Deployment: Docker
Deliverables:
Fully working backend service (API, scheduler, and worker logic)
Database schema and migration scripts
Basic admin dashboard for management
Documentation (README) explaining:
System setup
How to define weekly schedules
How proxy pools are configured and logged
Important Notes:
This project must not be used to violate the Terms of Service of any third-party website.
Proxy usage is allowed only for load balancing and network redundancy.
Focus of the project is on automation, scheduling, and coordination, not on bypassing website security.
Budget and Timeline:
Please provide your estimated timeline and budget.
Looking for developers experienced in backend architecture, scheduling systems, PostgreSQL, Redis, and proxy or worker coordination.