| |
|
LAMP alternative to J2EE and .Net |
|
|
|
Written by Content Team
|
|
Apr 07, 2005 at 08:06 PM |
A few days back, IndicThreads reported on how Python is starting to enter the enterprise application space and today we came across two more stories about how LAMP technologies (Linux, Apache, MySQL and Perl/Python/PHP) are challenging J2EE and .NET. J2EE and .NET better get ready for some serious competition in the near future.
Here are some excerpts from the articles:
"Perhaps as Java and .Net vie to outdo each other,
the LAMP stack might have a chance to pass both of them by as a favored
stack. Users can only benefit from having a third strong competitor to
force the Java and Microsoft camps to keep their mega-platforms state
of the art, as I see it."
"Early PHP applications could often be dismissed
as hacks built using crude methods, but modern versions of the language
offer many of the object-oriented tools available to C# or Java
developers, and its execution core is stable and efficient."
"The open source LAMP platform
is a mature alternative that has a lot to offer, particularly for projects on a tight budget."
Reference:
>> The LAMP alternative to J2EE or .Net
>> LAMP begins to light up the software world
Related:
>> A Python In Java Land
|
Comment by Guest on 2005-04-08 10:57:01
"..., particularly for projects on a tight budget"
The L, A, M of LAMP can be used in combination with J2EE today efficiently. Java is as free $ wise as Python/Perl/PHP plus has sophisticated free IDEs like Eclipse/NetBeans...
Exceution core has to be stable. Thats not even a comparison point.
As of today LAMP might be a competitor, but a
J2EE and .NET developer has a higher resale value (possibility of a resale). i.e., its like hyundai and honda. They both work, have all the bells and whistles, have a X yr warranty etc.. etc.. but I bet when it comes time to sell your car, your honda would fetch you more.
Same deal with skills..
|
Comment by Guest on 2005-04-08 20:34:07
I totally agree with the above comment. LAMP people seem to think that piggybacking Python/Perl/PHP on the successes of Linux, Apache and MySQL is somehow going to make them more attractive than Java or DotNet. The term LAMP itself is just a weak attempt to give credence to the "P" languages. |
Comment by Guest on 2005-04-08 22:58:36
If the option is to buy a hyundai or go without a car as you cannot afford the Honda, then I guess it is smarter to go for the hyundai. |
Comment by Guest on 2005-04-14 23:42:55
The LAMP stack is good for small internal apps, or perhaps low-volume shopping carts, but where is the equivalent of JAAS, JMS or JTA? Is a LAMP app scalable across more than two servers? Enterprise apps have to be a bit more hearty than a blogging or news site... |
Comment by Guest on 2005-04-27 22:03:45
Somebody something uses simple and quick or something good durable and reliable?, is java for that reason always a good consistent and portable option
|
Comment by Guest on 2005-04-29 03:34:56
The issue of scalability has come up here, as pointed by "LAMP not enterprise-ready". The L-A-M parts of LAMP are all scalable, because they are not tied into the P layer.
You are forgetting that PHP is for developing web applications, something that is excels at, because that is what it was designed to do from the beginning. Unlike Java, which was designed to program toasters, and then got expanded to a proper "platform", and finally got thrown in other stuff like JSP so that it can be used for -- yet another thing.
Another point that a lot of people forget (and its mentioned all over the internet) is that it seems that every other month there is a new framework coming out for Java and Java architects then realize -- oh wait, now we have completely restructure (most likely rewrite) our application to take advantage of the new framework coming out, because the way we are doing it now was completely wrong -- or was not "best practice" (which is almost never brings the best results).
I will give you this much. PHP, because of its structure allows for sloppy architecturing and design, and its very forgiving. This is party why its so fast and efficient. However, don't confuse this with "PHP encourages bad design". Bad design is all from the solution architect/programmer's point of view, and has nothing to do with the language. You can find poorly designed applications in any language.
PHP is fast, quick an efficient. It gets the job done, which in today's market where TTM is at the tip of every manager's tongue; is a real boon for all PHP programmers. |
Comment by Guest on 2005-05-11 02:27:00
"but where is the equivalent of JAAS, JMS or JTA?"
LAMP is complementary to those technologies, since PHP and Perl are interoperable with Java. The P's could be considered implementation languages of the web layer in the overall architecture. Many compelling reasons to use scripting languages for development of web applications. Language interoperability yields the best of both worlds.
I have never heard a good explanation of why Java is more scalable than LAMP. The LAMP stack can be scaled up with clusters of Apache/MySQL servers. Java can be scaled at the application server level. What's the difference? At least the PHP way doesn't require a special scheme to replicate application state, since sessions are stored in the database (just cluster the database).
|
|
|
|
|
Home | 
