Journal #232 – Operation deployment successful, I think

Part of me felt that today’s deployment wasn’t a true success but I will take whatever win I can get.

Now, if you are wondering why I haven’t mention where I work or whom I’m doing the project for, it’s because I like to keep some sort of privacy. Besides, the project I’m on is rather confidential, close to being secretive. So no names and no details.

Anyway, I met my team at the cafeteria located at the customer’s building at around 9.05am. I had my second breakfast of fried bee hoon (rice vermicelli), fried egg, hash brown, and fried beancurd (tofu). I also had a cup of black coffee, a variant that we call Nanyang Coffee, typically found in Singapore’s coffeeshop and hawker centers. The taste was decent but not as good as those from Starbucks due to the preparation process.

After that, my team and I made our way up to the datacenter where we will do the deployment. Got escorted in, signed in, and we went about doing our work.

During deployment, that’s how I found out that the server side application wasn’t compiled and published properly. The Impersonation annotation somehow remained on all the WCF services. So I reverted the changes.

Then I discovered another combined issue caused by the NGINX, the client application, and RabbitMQ. IIS got stuck processing series of requests from the NGINX to two of the WCF services, which relied on the RabbitMQ for additional processing. The part of the application doing the RabbitMQ was unable to proceed due to exceptions and were unable to proceed. With the requests stuck, additional requests couldn’t be processed, and the client application was pretty much unusable.

By now, it’s almost lunch and so my colleague and I went about systematically simplify the whole application stack so that we can at least get some sort of functioning application.

After lunch, we focused on getting more functionality out of the application and uncovered more bugs and potential usability problems.

So that’s what I meant by getting whatever win I could get. I see it as only through deployment and testing then we can find more issues that we can fix before going UAT. To me, that’s part of delivering quality to the customer.

With that, tomorrow I will go back to office and focus on fixing those found issues and prepare it for another round for deployment.