It was almost seven years ago when I started to write on blogpost (Blogger right now).
From the beginning it was a heavy technology blog about my software development, and I have never thought that someone would read these articles. Now, at the end of 2016 I have about 86.5K unique views, what means more than 30 visitors daily, on average. This is amazing. Thank you people (and bots :D)!
Anyway, I still plan to write and make a little more software. However I decided to move out from blogspot. Previously I wanted to write an article why I decided to leave blogspot, but I've recently found Trisha Gee post about why she is moving from blogspot to hugo. This is a perfect article, I can only repeat this explanation, so it's better to just put a link here :)
So, I'm closing this blog, and moving to hugo (my own choice is hugo - however other static site generators look great as well) and my own domain lifeinide.com.
Thursday, December 29, 2016
Wednesday, August 3, 2016
Reads vs writes in production database of web application
I recently think about CQRS-like patterns we partially used in current application, and pros'n'cons of migrating more towards full CQRS, which is mostly about separating reads from writes. Previously I assumed that in usual application "we may have probably 100 times more reads than writes", what would qualify to have a value from these two models separation. I wanted to check it later on the production, but I forgot. Now we are close to start a big redesign of the whole application, and I've just remembered about that. So, how does it look for real production? This is data from postgres pg_stat_database of one of my projects:
tup_returned | 58956902163
tup_inserted | 3348809
tup_updated | 4557408
tup_deleted | 245501
Does it look that I made a big mistake previously and we have ~7200 times more reads than writes? It will be funny to investigate that in the near future...
Subscribe to:
Posts (Atom)