Keeping SSH sessions alive with Mac OS X Terminal Back to the Real World
Aug 03

Over engineering anecdote

Tech Add comments

I was comparing some notes with a local company that friends of mine work at. The application in question used a typical modern Java stack (WebWork, Spring, Hibernate) and in production has a bunch of machines to enable it to scale up.

The application is a new beta site, and as such doesn’t have a lot of traffic yet (not published highly).

Ironically, one of my current projects has millions of transactions a day, and runs on a lot less iron.

These days, with the right app (one that you can cache nicely) you can get scalable performance without breaking the bank at all.

5 Responses to “Over engineering anecdote”

  1. Anonymous Says:

    so what tech stack is your app developed with? RoR?

  2. Adam Bien Says:

    Sorry, but it isn’t a good sample for overenginnering…
    In the practice it also doesn’t matter, because hardware is really cheap. Clustering etc. is not using because of performance gains, but because of fail-over issues.
    It is all about nonfunctional requirements…
    You can build the fastest application, hacking everything in the doGet method of a servlet. Everything else is slower…

  3. master2 Says:
    <a href=”http://xoomer.alice

  4. divx full movie download Says:

    Hello, nice site look this:
    Last Action Hero

  5. download dvd movies Says:

    Hello, nice site look this:
    For the Moment
    007 You Only Live Twice
    Butterfly Effect, The

Leave a Reply

Spam is a pain, I am sorry to have to do this to you, but can you answer the question below?

Q: What are the first four letters in the word British?