Split Java API into multiple microservices rather than 1 larger service
Right now the API for membership.eclipse.org serves a lot of functions for different facets of the site. The split between portal and membership form is decently clean, and can likely be actualized into 2 microservices rather than 1 larger combined service.
We will need to test and evaluate this to make sure there are no hiccups to this process, but this would be good for management of code and to make management of code cleaner and more straightforward. It would also reduce the impact of builds for different sections of the service in other parts of the membership.e.o site, which is always a bonus.