Disclosure: On this site you won’t find specific advice on “how to call function xyz()”. Interpreting C++ ARM and #pragma dwim is also out of scope.
We’re treating our readers as intelligent beings who can use Google and/or StackOverflow, where all such specific questions were answered more than once.
What you will find is opinions, more opinions, and even more opinions on all the aspects of software development - and with a large chunk of them based on real-world experience too.
Your mileage may vary. Batteries not included.
Back End Tools for MOGs
July 11, 2017 by • “No Bugs” Bunny
Quote:
Make sure that your reports are CSR-driven.
Another Quote:
The vast majority of Back-End Tools are intended for NON-programmers and NON-admins.
Filed under: Book: D&D of MOGs1st beta of Vol. VII-IX
Read moreSystem Monitoring
July 4, 2017 by • “No Bugs” Bunny
Quote:
We need to monitor EVERYTHING we can afford to monitor.
Another Quote:
Monitoring data doesn’t really require ACID transactions.
Filed under: Book: D&D of MOGs1st beta of Vol. VII-IX
Scaling Stateful Objects
June 27, 2017 by • “No Bugs” Bunny
Quote:
it is DB which is usually The Bottleneck™ – it means that we’re saving this enormous amount of load, exactly where it really matters.
Another Quote:
as discussed above, the real-world task is always about scaling the whole system, including database; and in this regard Stateless-App-based systems exhibit significant problems.
Filed under: Book: D&D of MOGs1st beta of Vol. VII-IXOn.System ArchitectureDistributed systems
Read moreScalability for MOGs
June 20, 2017 by • “No Bugs” Bunny
Quote:
Whenever Game Event is interrupted for significant time, as a rule of thumb it is better to roll back the interrupted Game Event rather than trying to restore the exact Game World State in the middle of the Game Event.
Another Quote:
Just like Scaling Up, improving performance doesn’t provide infinite scalability. However, it happens that it is all about numbers.
Filed under: Book: D&D of MOGs1st beta of Vol. I-III
Read more



