• Jeff Moden (10/21/2013)


    +1000. I just went through some real hooie on one of the apps designed before the current team started. One of the apps checks for the credentials of the user on ever screeen and every object touched. Some of the pull downs check for credentials for every item in the pull down. One click would generate a dozen calls to the same credential proc (and we have a LOT of credentials. It's one of the worst designs I've ever seen but not the only one I've seen like it. Of course, the outcry was "the database has a performance problem". It sure did... the problem was the application using it. 😉

    It'll become a problem in the future again because their "fix" was to cache the credentials. It's still making a dozen checks per object clicked. Time for the webserver to start taking the blame for crap code. :hehe: It's a real shame that they don't want to spend the time to fix the bloody root problem!!! :sick:

    This idea reminds me that Mongo DB Is Web Scale. Making a website try to act like a miniDB is actually sort of scary. Is it guaranteed to be written into the DB at some point? Will you be sure that the the user didn't loose connectivity and connect back to a different web server. I have an aircard at home for my web experience. I'm not sure if it is the aircard, the provider network, or my laptop's USB ports that are screwing up but I am having weak signals and dropouts on a regular basis for the last few weeks. Am I guaranteed to go back to the same web server? Can the cache on webserver1 overwrite webserver2?

    Another bad design example is the healthcare.gov website. They needed it to eventually get over 16M people to use it. Could you imagine designing a website that you are dumping every bit of your personal financial and health information into and it is trying to store it in live memory and can only handle 50-60K users at a time[/url]?



    ----------------
    Jim P.

    A little bit of this and a little byte of that can cause bloatware.