Slashdot Mirror

← Back to Stories (view on slashdot.org)

MEAN Vs. LAMP: Finding the Right Fit For Your Next Project

Posted by samzenpus on from the best-tools-for-the-job dept.

snydeq writes: LAMP diehards take note: The flexible simplicity of MongoDB, ExpressJS, AngularJS, and Node.js is no joke and could very well be a worthwhile stack for your next programming project, writes InfoWorld's Peter Wayner. "It was only a few years ago that MongoDB, Express.js, AngularJS, and Node.js were raising eyebrows on their own. Now they've grown up and ganged up, and together they're doing serious work, poaching no small number of developers from the vast LAMP camp. But how exactly does this newfangled MEAN thing stack up against LAMP? When is it better to choose the well-tested, mature LAMP over this upstart collection of JavaScript-centric technologies?"

11 of 175 comments (clear)

  1. The Fuck? by OverlordQ · · Score: 4, Insightful

    >This isn't a problem if every single entry fits into exactly the same format, but how often is the world that generous?
    > What if two people share the same address but not the same account?

    You dont make it a unique field?

    > What if you want to have three lines to the address instead of two?

    You have an empty field?

    > Who hasn’t tried to fix a relational database by shoehorning too much data into a single column? Or else you end up adding yet another column, and the table grows unbounded.

    Yeah, I cant read this crap considering the very next section is 'Disk space is cheap'. If it's cheap, who cares about 1 extra field in the database.

    Remember guys MongoDB is webscale

    --
    Your hair look like poop, Bob! - Wanker.
    1. Re:The Fuck? by Anonymous Coward · · Score: 2, Insightful

      Might as well just call this place, Digg 3.0 - Getting Shittier All the Time.

    2. Re:The Fuck? by MightyMartian · · Score: 4, Insightful

      It's almost as if the writer doesn't understand what a relational database is.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    3. Re:The Fuck? by rockmuelle · · Score: 4, Insightful

      And the author hasn't looked at a relation database in the last few years, either. PostgreSQL, Oracle, MySQL, and I'm sure the other big ones all have JSON (or similar) column types now that let you attach semi-structured elements to your records. You get all the benefits of a RDBMs (ACID, referential integrity, 40 years of history) _and_ all the benefits of NoSQL.

      Seriously, there's no good reason not to start with PostgreSQL and only add MongoDB if you really have a good use case for it (you know, you suddenly need to be Web Scale). Personally (and professionally), I use both, with PostgreSQL as the main DB for everything and MongoDB for read-only collections of indexed data.

      My challenge to devs out there: spend the hour it takes to learn SQL and understand what you can actually do with it. And, stop pretending that an RDBMS won't scale to meet your needs (spoiler alert: it will).

      -Chris

    4. Re:The Fuck? by drakaan · · Score: 4, Insightful

      Not to be rude, but what the hell are you talking about?

      SQL engines are often slower than what? In what scenario? Operating on what hypothetical database schema with how many records spread across how many tables?

      SQL engines have problems with massive parallelism? Why? Which ones?

      How well do you *really* know SQL in general and the capabilities of different database engines in particular? I suspect you may know less than some people who know SQL *really* well (as opposed to *pretty* well).

      I apologize for the tenor of this post, but that portion off the article was ridiculous, and thus far all of the comments in support of it have demonstrated a similar lack of familiarity with actual databases, their operation, or performance tuning.

      --
      "Murphy was an optimist" - O'Toole's commentary on Murphy's Law
    5. Re:The Fuck? by Anonymous Coward · · Score: 4, Insightful

      What's really concerning is that I've had "new school" web devs completely laugh at me when I suggest they ask their resident DBA questions about database performance, etc. Apparently, a DBA is just someone who makes images and restores backups now. "Hey guys, let's make a business that's completely reliant upon reliable data, and then completely ignore getting someone who's entire knowledge specialization is data management and arrangement... Yeah, fuck those dba guys..."

  2. Great comparison by Anonymous Coward · · Score: 5, Insightful

    Which is a better tool for outdoor work, a lawn mower or a snowblower?

  3. Re:Different types of terms by laffer1 · · Score: 4, Insightful

    I think the who problem with LAMP or MEAN is that it's trying to define one web stack. The world has moved on. Some companies deploy nginx now instead of apache or in combination with it. Netflix sends 33% of all Internet traffic on FreeBSD rather than Linux. I've seen so many people replace the P in LAMP to be python. We can't even agree on the P.

    My current stack at work is FATAPJ - FreeBSD, Apache, Tomcat, AngularJS, PostgreSQL, Java

    --
    MidnightBSD: The BSD for Everyone
  4. why would you ever? by Gravis+Zero · · Score: 2, Insightful

    When is it better to choose the well-tested, mature LAMP over this upstart collection of JavaScript-centric technologies?

    always

    --
    Anons need not reply. Questions end with a question mark.
  5. Relations by pigiron · · Score: 3, Insightful
    What if two people share the same address but not the same account?


    Then you need an account table, a customer table, and a relational table that contains instances of paired keys from each. Learn some elementary set theory for chrissakes! The article is full of other stupidities as bad as this. /. keeps getting dumber and dumber. "Gee, my My SQL table has too many columns."

    I'll bet it does, you nitwit.
  6. Normalization by Frankie70 · · Score: 3, Insightful

    The fool thinks the only reason for normalization is to save space.