Remove inter-service dependencies for better separation of concerns

[Snehil-Shah]

Problem

Some design choices didn't end up as planned. We currently use a multithreaded Java interface to initialize and run our consumer clients. This design defeats the purpose of using a microservices architecture.

Currently the email service is set up on the same interface as the user facing logger, which means the Java interface needs to be running on both the server and client side, which is a fallacy!
Current architecture fails to account for distribution and scalability.

Outcome

Each consumer microservice should ONLY depend on Kafka as the single source of truth. Each consumer should be independent of each other.

This will require a long bit of engineering time for all the refactoring and for a personal project, I think the current implementation is good enough to show a small microservices architecture facilitated by Kafka. Hence, for the moment, there are no plans to fix this