While thinking back to when I was first learning about microservice architecture, I recall a few related subjects that I had come across such as asynchronous/connectionless messaging. The idea is that many areas of the system can operate independently of the client that invoked them. In other words, if I …
So the problem to solve today is environments as it comes to the event store implementation. Currently, we have 3 different environments, prod, qa, and dev. In true essence of COMPLETELY BLASPHEMY, the previous implementation had a single database that was used for all environments which is just… omg. That’s …
So we went with event store (geteventstore.com) and so far, it’s working pretty well out of the box, but I think we’re already starting to deal with some of the issues that come with event sourcing which is making sure that events are being processed in the right order. The …
The neat thing about this project is that it’s greenfield but… not. We understand our domain pretty well and we have an existing system to use as a reference, we just need to bring the system up to date with technology and practices. So obviously, rebuilding a system isn’t something …
So a few months ago, we got a new CTO that came to us from eBay and Amazon. His vision? Rejuvenate the software vision and maybe even convert us from an agency with a tech department to a tech company with some agency services. First order of business? Re-build the …