4 ms·
You have got to admire the evil villany we're up against. Buying the 'M' in LAMP and then exploiting that position. Business first, not the heart and minds of
by timhastings 16y ago
You have got to admire the evil villany we're up against. Buying the 'M' in LAMP and then exploiting that position.
Business first, not the heart and minds of developers.
Luckily the 'L' + 'A' + 'P' cannot be bought.
LAPP stack anyone?
- wlievens 16y agoIf you're going the "non-default" route of using postgresql you might as well ditch PHP. Unless P=Python? :-) LAMP is a loaded acronym which these days basically means "a web app built using FOS but not in Java or Ruby".
- timhastings 16y agoI am using the LNNMMMMP stack at the moment... Linux, nginx, node.js, memcached, MySQL, Mono, MongoDB and PHP. Am I normal?
- ax0n 16y agoNo. You, sir, are not normal. I'd love to know what sort of evil hackery you're cooking with that setup, though.
- timhastings 16y agoI'm cooking up a Twitter Recommendation Engine for users, hashtags, and links etc. For example: http://tagwalk.com/tag/MySQL http://tagwalk.com/tag/MySQL
- ax0n 16y agoPlayed with it a bit. I like it :D
- timhastings 16y agoThanks!
- mahmud 16y agoEven for a twitter recommendation engine, that's just a lot of moving parts. I hope your development is driven by accurate profiling and benchmarks. It's much better to have a dirty, but very surgical fix in a specific bottle-neck, than to have your application "scaled" with too many layers of individually "optimized" components, that bog each other to a crawl when combined.
- timhastings 16y agoThere are a lot of moving parts, but these are separate sub-systems with well defined boundaries of interaction. Each sub-system is implemented using technologies selected for specific characteristics. Mono for long-running and complex backend processes. nginx, PHP, MySQL, memcache - for presentation - quick! node.js provides an event bus between PHP and Mono MongoDB is taking over from storing large blobs of JSON in MySQL.
- mahmud 16y agoMakes sense. I was on the opposite side of things, when I did we last. I had language integrated into the web server, and I wrote my own caching primitives. All optimization went into the request handler, and optimizing a single function is easier than debugging a whole stack. A decent solution, but it had no massive inputs, so I slept better at night knowing it wasn't being tested.
- msquared 16y agonginx ftw
- cullenking 16y agoI am in the same boat, though not with your exact setup. It's easy to acrue alot of individual components, especially if you are a tinkerer, when developing a non-trivial application. rails, sinatra, mysql, resque, custom email server (looking for a name...), memcached. How the heck do you mix in mono?!?
- nl 16y agoP always has stood for Perl/PHP/Python (in that order.. it came about back when Perl was more popular than PHP)
- anilbioma 16y agoRemove M for MySQL in LAMP and make it M for MongoDB
- mahmud 16y agoIf your engineering problems are solved with a little phonetic consistency, you might as well rename a real database "Mostgres" and be done with.
- beagledude 16y agomongo is still a joke for most applications
- cullenking 16y agoYour kidding right? It has a time and a place, and can pretty "easily" be substituted for mysql/etc in most applications. We just put together a really fun project, a very vanilla community news aggregator aimed at cyclists. Took two days of core coding and another day or two playing around with styling/functionality, but mongo was a fantastic fit. http://veloscoop.com http://veloscoop.com [edit] I mis-clicked and upvoted you when I meant to downvote. Incendiary statements about valuable technology has no purpose here.
- Roboprog 16y agoI take it the extra P is for PostgreSQL? As far as I could ever tell, the only advantage MySQL ever had over PostgreSQL 10 years ago is that it ran on Windows, and Postgres did not, back then. Oh, and by skipping ACID features, MySQL was faster. So, back in the day, that drove me to conclude that all the MySQL fans were crazy, and I decided to use Postgres at home, since Windows != server, and having done quite enough XBase once upon a time, DB integrity had some value to me. LAPP? Bring it! Is the final P PHP, or Perl (which would be my preference)? Maybe make it an R for Ruby? :-)
- gaius 16y agoLARP in that case... The parallels are eerie ;-)
- steveklabnik 16y agoMost Rubyists (I have no numbers for this, just a general sense of the community, I could be totally wrong, all generalizations are false, etc) use Nginx nowadays, so it'd be more like LNPR.
- SkyMarshal 16y agoMost Rubyists also seem to be squarely in the NoSQL camp too, so try LNNR.
- piotrSikora 16y agoI've been using BNPP (*BSD, nginx, PostgreSQL, Python) for a while now, works like a charm :)