IGT Play Command

Play Command is a complete player-management solution for Lottery products. It is a high-performance and scalable digital solution designed to manage player-centric functions and game enablement within iLottery programs.

The solution follows a modular microservices architecture and supports player account management, wallet management, game administration, back-office administration, network integrations and external-system communication.

Key Architecture Interaction Patterns

Module Communication Model

Internal communication: As specified in the supplied architecture, one module communicates with another module through REST Services. JMB provides the event-driven messaging path.

Player / UI Trigger Flow

Back-office Flow

Event-driven Flow

Internal REST Communication

The application is developed using independently deployable Spring Boot microservices. Each service contains its own API, business logic, persistence, configuration, testing and operational concerns.

HTTP Operations

API Development Checklist

• Request validation
• Business validation
• Authentication and authorization
• Correct HTTP status codes
• Exception handling
• Logging and correlation ID
• Swagger/OpenAPI documentation
• Unit and integration tests
• Backward compatibility

Apache Camel is used for integration, routing, transformation and message-processing requirements.

JMS Flow

Quartz Scheduler is used for automated and recurring jobs, including batch processing, data synchronization, notifications and production scheduled activities.

Production Schedule Change

• Identify the Quartz job.
• Verify current schedule.
• Update required script/configuration.
• Validate the change.
• Deploy.
• Monitor job execution.
• Verify logs and business results.

PostgreSQL is used as the primary relational database. JPA and Hibernate provide the persistence layer.

Performance Optimization

• SQL query optimization
• Index optimization
• Schema design
• Pagination
• Connection pool tuning
• Transaction optimization
• Query execution plan analysis
• Avoid unnecessary database calls

Liquibase manages database schema and data changes in a controlled, versioned manner.

Common Liquibase Issues

• Invalid SQL
• ChangeSet already executed
• Incorrect change-set ordering
• Database connection issues
• Missing dependency
• Constraint conflicts
• Schema mismatch

Apache Solr provides search indexing and full-text search capabilities and integrates with business services.

Typical Use Cases

• Full-text search
• Fast retrieval
• Search filtering
• Large dataset searching
• Business-service search integration

Gateway Responsibilities

• Request routing
• Authentication
• Authorization
• Request filtering
• Rate limiting where applicable
• Circuit breaking
• Security enforcement
• Centralized monitoring

Technologies/patterns include Resilience4j and legacy Hystrix implementations where applicable.

Testing Flow

Feature / Enabler Story

Hotfix Process

Jira Updates

• Update Jira status.
• Attach unit-test results.
• Attach integration-test results.
• Add Pull Request reference.
• Update Effective Version.
• Update Fix Version.
• Assign reviewer.
• Track PR approval.
• Update deployment status.

Common Maven Activities

mvn clean
mvn test
mvn verify
mvn package

Nightly Build Validation

• Check Jenkins night-build status.
• Review failed stages.
• Analyze console logs.
• Identify code/build/environment issues.
• Check installation logs.
• Check Liquibase execution.
• Validate database changes.
• Fix issues.
• Re-run the build.
• Confirm successful installation.

Post Deployment Validation

• Verify application startup.
• Check application logs.
• Check database connectivity.
• Check dependent services.
• Validate APIs.
• Validate scheduled jobs.
• Execute smoke tests.
• Monitor application metrics.

Typical Support Activities

• Monitor application health.
• Investigate application errors.
• Analyze logs.
• Check database problems.
• Investigate integration failures.
• Validate scheduled jobs.
• Support deployments.
• Prepare hotfixes.
• Monitor application performance.
• Coordinate with QA and Support teams.

Application Issue

Build Failure

Jenkins Failure
      |
      +-- Compilation?
      |
      +-- Unit Test?
      |
      +-- Integration Test?
      |
      +-- Liquibase?
      |
      +-- Packaging?
      |
      +-- Deployment?
      |
      +-- Environment?

Database Issue

• Check database connectivity.
• Check SQL/query.
• Check Liquibase change set.
• Check locks.
• Check indexes.
• Check schema.
• Check query performance.

Production Incident Lifecycle

Business Understanding

• Understand Play Command business purpose.
• Understand player lifecycle.
• Understand wallet functionality.
• Understand game administration.
• Understand rewards and notifications.

Technical Understanding

• Understand microservice architecture.
• Understand REST APIs.
• Understand JPA/Hibernate.
• Understand PostgreSQL.
• Understand Liquibase.
• Understand Camel/JMS.
• Understand Quartz.
• Understand Solr.
• Understand Gateway and security.
• Understand circuit breakers.

DevOps Understanding

• Understand Git branching strategy.
• Understand Jira workflow.
• Understand Pull Request process.
• Understand Jenkins pipeline.
• Understand Linux deployment.
• Understand hotfix and backport process.

Operations Understanding

• Understand Grafana dashboards.
• Understand New Relic monitoring.
• Understand VisualVM.
• Understand logs and troubleshooting.
• Understand scheduled production jobs.
• Understand incident and RCA process.

The IGT Play Command platform is a scalable digital Lottery player-management solution built using a modern Java/Spring Boot microservices architecture.

The platform combines REST APIs, PostgreSQL, JPA/Hibernate, Apache Camel, JMS, Quartz, Solr, API Gateway, resilience patterns, Jenkins CI/CD, automated testing, GitHub-based development and modern observability practices.