Its not something we have considered so far as the system we built was very specific to our crowdfunding round and is probably not suited to running continuous investment rounds.
That being said I think there are a lot of valuable lessons to learn from our experience. Not just for crowdfunding platforms but for designing all kinds of systems.
I’m assuming that crowdfunding-total is a dead simple Go service that just keeps a counter in memory and periodically writes to disk, as stated.
I was wondering which communication protocol was chosen to communicate with this service given its extraordinary simplicity and at the same time demand for performance. Is HTTP too much in this case? Was it some form of RPC?
Very interesting read especially from someone who works in IT where high frequency - low latency is required. Makes sense for approach you chose to take & I managed to get in to show some support too.