GlassFish and MySQL, A Perfect Combination for Web Applications

This post is a summary of an article that discusses the use of MySQL and Glassfish in the context of Web Applications.

Why MYSQL and Glassfish?

  • They are fast, reliable, and easy to use.
  • Both provide an excellent, low-cost solution for quickly developing and deploying web applications
  • They are not only secure and reliable, but also scale to meet increasing demand and are highly responsive to user requests.
  • MySQL and GlassFish offer graphical tools that simplify administration
  • They integrate into developer tools such as the NetBeans IDE or the Eclipse IDE using plug-ins easily.
  • They can also be used with popular open-source development frameworks such as Ruby on Rails, Spring, Struts, and Seam
  • Both of them run on all major operating systems and hardware.

MYSQL:

  • is the world’s most popular open-source database.
  • supports ANSI standard SQL, the standard programming language for querying and managing relational databases.
  • supports the same language and, in general, the same feature set as other databases that support the standard.
  • MySQL statements follow a “Do action To target “
  • provides a client program called the MySQL monitor that allows users to enter SQL statements
  • uses SQL statements to perform database administrative tasks such as creating a database, …
  • includes a client program called mysqladmin that you can use to perform administrative actions such as creating and deleting databases, shutting down the MySQL server …
  • MySQL’s scale-out capabilities make it fast, scalable, and reliable.
    scale out refers to an architectural design that separates and spreads the database workload across different physical servers as shown in the following figure.
    This scale-out design helps MySQL run very fast — the MySQL database consistently scores among the top databases for performance and throughput — and it also makes MySQL very reliable because redundancy is built into the design
  • MySQL’s pluggable storage engine layer gives us the flexibility to choose the type of database best suited for our needs.

Glassfish:

  • Supports Java EE 5 standard. The following Technologies of Java EE 5 are implemented in Glassfish:
    • Java Servlet 2.5
    • JavaServer Faces (often referred to as JSF) 1.2
    • Enterprise JavaBeans (EJB) 3.0 — which includes the Java Persistence API
    • web services technologies such as Java API for XML-Based Web Services (JAX-WS) 2.0
    • Java Architecture for XML Binding (JAXB) 2.0
    • And support the use of annotations as well.
    • provides the technical richness that’s required to provide real-life solutions
    • is an extremely fast open-source application server.
    • takes advantage of the New I/O (NIO) APIs in the Java platform to scale to thousands of users.
    • ensures reliability through clustering and memory replication.
    • supports the type of web applications and mashups that are often associated with the term Web 2.0.
    • supports dynamic content through Java EE 5 web technologies
    • implements the Metro stack of web services technologies. Metro includes core web services technologies such as JAX-WS and JAXB that enable you to develop and use web services.
    • supports data persistence through a Java Persistence API engine

Glassfish VS Tomcat:
Tomcat is an open-source web container that runs Java servlets and JSP pages in web applications. Tomcat is popular in the open source community, and is often used with MySQL.

  • GlassFish provides a more extensive web technology implementation than Tomcat
  • Although Tomcat supports servlet and JavaServer Faces technology, GlassFish goes beyond that, supporting all Java EE 5 technologies., including the following:
    • Web tier technologies
    • Enterprise technologies
    • Web services technologies
    • Management and security technologies
    • GlassFish provides more comprehensive and easier-to-use administration and monitoring tools
    • GlassFish has better HTTP-related performance than Tomcat’s HTTP handler.
    • GlassFish clustering gives administrators more flexibility in terms of load balancing than Tomcat.
    • An application that runs in Tomcat will run in GlassFish without modification.

The next Blog entry will be about SOAP security and Glassfish :)

, , ,
  • Delicious
  • Facebook
  • Digg
  • Reddit
  • StumbleUpon
  • Twitter

Leave a Reply

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>