main infrastructure diagram
| Service | Environment | Domain |
|---|---|---|
| Operator backoffice | development | https://bo-dev.unostage.com |
| Operator backoffice | staging | https://bo.unostage.com |
| Operator backoffice | production | https://bo.unoseamless.com |
| Player portal | development | https://portal-dev.unostage.com |
| Player portal | staging | https://unoplay.unoseamless.com |
| Player portal | production | custom domain |
Hosts for backend service are in the following format:
https://[OPERATOR-CODE].[HOST]/[SERVICE-NAME]
Example: https://dev.unoseamless.com/promo
Refer to the table below for the host and the service name path
| Service | Environment | Domain |
|---|---|---|
| Backend host | development | https://dev.unoseamless.com |
| Backend host | staging | https://uno.unoseamless.com |
| Backend host | production | https://[operator-code].unoapi.com |
| Service | Path |
|---|---|
| Activity Log | /log |
| Bonus | /bonus |
| Game | /games |
| Membership | /membership |
| Payment | /payment |
| Player | /player |
| Portal | /portal |
| Promotion | /promo |
| Report | /report |
| User | /user |
| System | /system |
This section will explain all services in the WL Seamless project. There are currently 12 services running in the WL Seamless project:
Every service share the same folder structure explained in the work directories section. Services communicate with each other through gRPC and exposes data to external services through the Rest API HTTP endpoints.
Report service and activity service are both Kafka subscriber service, meaning that both services acts as a Kafka subscriber and get most of input data from Kafka messages. Report service processes various input data including wallet transactions, game rounds, and player registrations and then processed into report data that can be fetched from gRPC or HTTP service. Meanwhile, the Activity Log Service processes audit log or data mutation information and processes them into activity log data.
Portal service is a service that acts as a sort of an API gateway that forwards request from player portal to each corresponding services in the system. For example, when a player is sending a login request from the player portal, Portal Service forwards the request to Player Service through gRPC service. The response is processed and returned to the client as HTTP response.
main infrastructure diagram