docker-compose
docker-compose up --build
- Monorepo: A mono-repo seemed suitable for this as there is need for sharing parts of the codebase across components (like
autogen
in grpc,docker-compose.yml
). Moreover, this is a small project now and the setup effort can be kept lower this way. Every component has scope to have their own repositories. - gRPC: Very high performance claims
- REST: Browser compatible
- 3 separate containers: To be able to scale independently when requied.
- pre built pandas container: Pandas (+numpy) build was taking a long
- gRPC generated code has issue
- gRPC documentation is difficult to find but Docs, Github help a ton.
- react-datetime-picker seems to have a papercut bug with the clock.
- Better Error handling and logs
- Inline Datetime component
- Move React environment variables to runtime/loadtime configurable
- Various aggregation levels (15min, 1hr, 1day, 5day, 1week, 1month)
- timezone support?
- Multiple files - belonging to different locations/countries. If location not provided, get aggregated?
- Support to add files
- CI/CD setup
- Performance Testing and Optimisations (like Dask?, react dynamic import?)
- React build performance