IMHO, J2EE and LAMP differ largely in scalability and complexity. J2EE is more targeted towards complex applications, while LAMP is more suitable for small - medium scale web applications.
I agree, J2EE does scale very well. It is also easy to design very flexible solutions with J2EE. Resource consumption is a downside, however for small to mid sized applications, it is possible to avoid the EJB route, and simple use an application framework such as Expresso, and deploy the solution on Tomcat. This reduces resources consumption significantly.
LAMP should be sufficient for a low complexity application and MySQL would be the first thing to become a limiting factor in load taking capacity, provided the hardware and network are capable enough. FYI, sourceforge.net is done in PHP with DB2 having replaced MySQL not too long ago. I guess LAMP would suffice for the Project Management Application.
Yes I think so too. LAMP would be a good choice for a small scale project management solution. Also there are good PHP based open source applications such as PHPCollab and TUTOS to use as a base.
Personally, I am also planning to look into C++ with XML as a platform for enterprise applications and web services. There are some really capable application development frameworks like ACE available for it. Generally, stuff that's available in J2EE is also available in C++. It's just that the former gets noticed since there's no c++.bigcorp.com. Oh, but my opinion may be biased due to my perennial rant against Java, the platform. ;)
Are the libraries available in C++ for enterprise applications as extensive as J2EE? I think most people choose J2EE because of the huge array of libraries/components available, which they can leverage right away. Another reason in favour of Java is automatic garbage collection. This makes it easier to create more robust applications. Does C++ have something equivalent. I have used Java for quite some time and have found it to be a reasonably good platform to use. However I have never used C++ to build enterprise level applications, so I am not familiar with it's strenghts. Java does have shortcomings, mainly those of speed. However there are ways to work around them. My biggest issue with Java used to be that Sun released too many libraries too soon without really ensuring quality. Though I believe they have become better at that. I am curious to know your reasons for disliking Java and preferring C++ :-)
On 09/09/03 11:07 +0530, Parag Shah wrote:
IMHO, J2EE and LAMP differ largely in scalability and complexity. J2EE is more targeted towards complex applications, while LAMP is more suitable for small - medium scale web applications.
Dunno. Linux, Apache, Perl/Python, PostgreSQL *scale*. You do know that you can do OO development with both Perl and Python, right? Of course, doing proper, scalable design helps in any case.
I agree, J2EE does scale very well. It is also easy to design very flexible solutions with J2EE. Resource consumption is a downside,
That is a problem with Java the runtime environment, and with Java the collection of libraries.
however for small to mid sized applications, it is possible to avoid the EJB route, and simple use an application framework such as Expresso, and deploy the solution on Tomcat. This reduces resources consumption significantly.
Or just do it in Python/Perl/C++ C/C++ iff you are feeling macho for web applications.
LAMP should be sufficient for a low complexity application and MySQL would be the first thing to become a limiting factor in load taking capacity, provided the hardware and network are capable enough. FYI,
PHP actually. PHP is good for simple web applications, but not much more than that. Personally, I would use PHP for the frontend and Perl for the backend if I needed RAD, and given enough time, Perl, Mason, and the CGI and Template modules.
sourceforge.net is done in PHP with DB2 having replaced MySQL not too long ago. I guess LAMP would suffice for the Project Management Application.
Yes I think so too. LAMP would be a good choice for a small scale project management solution. Also there are good PHP based open source applications such as PHPCollab and TUTOS to use as a base.
Personally, I am also planning to look into C++ with XML as a platform for enterprise applications and web services. There are some really
Buzzword Compliant Programming?
capable application development frameworks like ACE available for it. Generally, stuff that's available in J2EE is also available in C++. It's just that the former gets noticed since there's no c++.bigcorp.com. Oh, but my opinion may be biased due to my perennial rant against Java, the platform. ;)
Are the libraries available in C++ for enterprise applications as extensive as J2EE? I think most people choose J2EE because of the huge array of libraries/components available, which they can leverage right away.
Depends on what you mean by "libraries for enterprise applications". C++ has plenty of libraries, as well as the STL.
Another reason in favour of Java is automatic garbage collection. This makes it easier to create more robust applications. Does C++ have something equivalent.
For those of us who know how to manage memory, garbage collection isn't much of a gain. When we wish to avoid it, we use languages which do it for us without the memory hogging and performance thrashing JVM.
I have used Java for quite some time and have found it to be a reasonably good platform to use. However I have never used C++ to build enterprise level applications, so I am not familiar with it's strenghts.
C++ can be a scalpel in the hands of a reasonably competent programmer. Java makes some things easy, but the things that aren't really supported by Java are a pain.
Java does have shortcomings, mainly those of speed. However there are
Speed, and resource requirements.
Devdas Bhagat
-
Devdas Bhagat -
Parag Shah