Interface DataService

All Known Implementing Classes:
DataSvc

public interface DataService
Service for sourcing, mapping and consuming data.

The service is in charge of two data flows: - push, given to consumers - pull, obtained from sources

The mappers facilitate a one way type transformation if needed.

The interface is very abstract about how data is obtained, but here are my general ideas of where the abstraction is coming from. - push cause one or multiple consumers to modify stored data - pull cause one or multiple suppliers to fetch stored data - mappers are stateless type transformers in memory

Example use-case: - PlayerJoinEvent is mapped to a generic event - that generic event is then consumed and mapped until the data is in a database.

- Some kind of data is wanted to place on a web page - It is requested and the suppliers and mappers give the wanted type of data.

Further research needed: - Can this limited type system represent types of data that need parameters (such as differentiate between two servers data)