Package-level declarations

Empty implementation of GameServiceImpl that performs no storage operations. Used primarily for testing scenarios where storage interaction is not needed. All methods are no-ops and return default or dummy values.

In-memory fake implementation of GameServiceImpl for testing purposes. Stores game states in memory rather than persisting to an actual storage backend. Useful for unit tests and scenarios where real storage is not available or desired.

Primary implementation of the game service for managing game state persistence. Provides integration with various storage backends (file system, MongoDB) and handles game state synchronization, player management, and storage operations.

Service interface for managing game state persistence and retrieval operations. Provides methods for saving, loading, and managing game states across different storage backends.