JADE (programming language): Difference between revisions
m →History |
trim most of the puffery |
||
| Line 1: | Line 1: | ||
[[File:JADE (programming language) logo.png|thumb|The JADE logo]] | [[File:JADE (programming language) logo.png|thumb|The JADE logo]] | ||
'''JADE''' is an [[object-oriented]] software development and deployment platform | '''JADE''' is an proprietary [[object-oriented]] software development and deployment platform consisting of a programming language, integrated [[application server]] and [[object database]] management system. | ||
Designed as an end-to-end development environment to allow systems to be coded in one language from the [[database server]] down to the [[client (computing)|clients]], it also provides APIs for other languages, including [[.NET Framework]], Java, [[C (programming language)|C]]/[[C++]] and [[Web service]]s. | |||
As a programming language, its main competitors are [[Java (programming language)|Java]] and [[C Sharp (programming language)|C#]], while as a database it competes with other object-oriented databases and [[post-relational database]]s such as [[Versant Object Database|Versant]], [[Caché (software)|Caché]] and [[Matisse (DBMS)|Matisse]] as well as traditional relational database software packages such as [[Oracle database|Oracle]] and [[Microsoft SQL Server]]. | As a programming language, its main competitors are [[Java (programming language)|Java]] and [[C Sharp (programming language)|C#]], while as a database it competes with other object-oriented databases and [[post-relational database]]s such as [[Versant Object Database|Versant]], [[Caché (software)|Caché]] and [[Matisse (DBMS)|Matisse]] as well as traditional relational database software packages such as [[Oracle database|Oracle]] and [[Microsoft SQL Server]]. | ||
Although a free limited licence is available for development, using the JADE platform requires per-process fees to be paid. | |||
==Language== | ==Language== | ||
In syntax, JADE is very similar to [[Pascal (programming language)|Pascal]]; its syntax is based on the language [[Modula-2]], which was derived from Pascal. | In syntax, JADE is very similar to [[Pascal (programming language)|Pascal]]; its syntax is based on the language [[Modula-2]], which was derived from Pascal. While it includes innovations lacking in Pascal or Modula-2, it lacks certain features of other modern object-oriented languages such as C# and Java. | ||
===Programming model=== | ===Programming model=== | ||
Like all of the other popular programming languages used to create database-driven software, JADE is fully [[object-oriented programming|object-oriented]]. JADE was designed to have all the most important features of object-oriented programming, but | Like all of the other popular programming languages used to create database-driven software, JADE is fully [[object-oriented programming|object-oriented]]. JADE was designed to have all the most important features of object-oriented programming, but does not support the overloading of methods or operators, and lacks parameterised constructors. | ||
Classes in JADE are kept together in [[logical schema|schemas]]. Schemas serve the same purpose as [[Java package]]s or [[namespace (computer science)|namespaces]] in .NET, but | Classes in JADE are kept together in [[logical schema|schemas]]. Schemas serve the same purpose as [[Java package]]s or [[namespace (computer science)|namespaces]] in .NET, but have a hierarchy, and inherit classes from superschemas. This becomes useful especially when programming using the [[model-view-controller]] methodology, as model classes can be put in one schema, then the controller and view classes can be built on top of the model classes in a subschema. | ||
===Program structure=== | ===Program structure=== | ||
JADE programs are developed using a user interface that allows programmers to visually create [[class (computer science)|classes]] and define their properties and methods. Instead of locating methods in large files, programmers select the method they would like to edit and only the code for that particular method is displayed. Also instead of compiling all the code of a program at once, in JADE, each method is compiled individually as soon as the method is completed, meaning code can be checked immediately. | |||
All the code for a JADE application is stored in its object-oriented database. This | All the code for a JADE application is stored in its object-oriented database. This allows for multi-user development as the database maintains concurrency control, and with each piece of the code being a separate object in the database, it is often possible to recode a system while it is live and online as long as the parts of the system being changed are not in use. | ||
==Features== | ==Features== | ||
The main goal of JADE was to | The main goal of JADE was to create a seamlessly integrated programming language that would allow developers to create one application that would go from end-to-end instead of having to write three separate applications for the [[database server]], [[application server]] and [[presentation client]] and then write the code for them to communicate with each other. | ||
===Object database=== | ===Object database=== | ||
The most striking difference between JADE and other object-oriented programming languages is that its [[object database]] is a native part of its language. For example, when creating an object in JADE, it can be created as transient or persistent. Creating an object as | The most striking difference between JADE and other object-oriented programming languages is that its [[object database]] is a native part of its language. For example, when creating an object in JADE, it can be created as transient or persistent. Creating an object as ''transient'' is similar to creating objects in other object-oriented programming languages - the object is simply created in memory, and then lost when the program ends. On the other hand, when an object is created as ''persistent'', when the program ends, the object will still exist and be there the next time the program starts up. So, when an object is ''persistent'' JADE automatically works in the background to store and retrieve the object in the database when necessary. Persistent objects can be distributed across multiple co-operating servers, with JADE automatically handling object caching and cache coherency. | ||
There are very few differences between manipulating transient and persistent objects | There are very few differences between manipulating transient and persistent objects so JADE makes it ''appear'' to the programmer as if all the objects in the entire database were in local memory. Most of the time, JADE's object-oriented database is used in a multi-user system, and so JADE makes it appear to the programmer as if all the objects in the database were stored in shared memory that all users connected to the system can access, even from different computers. | ||
With all of the program code centralised on the database server as well the data, | With all of the program code centralised on the database server as well the data, all client nodes can be programmed as if they were running on the database server. | ||
JADE's database is | JADE's database is inherently object-oriented, and [ACID]-compliant, and has all of the standard features such as atomic transactions, locking, rollback, crash recovery and the ability to keep one or more [[secondary database server]]s synchronised with the main database for backup, disaster recovery and performance reasons. | ||
JADE | To interoperate with relational databases for reporting, [[business intelligence]] and [[data warehouse]] purposes JADE since 2010 has provided a "Relational Population Service" that enables automatically replicating objects from it's native object-orientated database to one or more [[relational database]]. This feature supports Microsoft SQL Server versions 2000, 2005 and 2008. | ||
===Three-tier model=== | ===Three-tier model=== | ||
Database-driven software, often uses a [[three-tier (computing)|three-tier]] methodology with applications being split into three tiers — data storage, processing and presentation. In the data storage and processing tiers, JADE systems are a collection of co-operating servers, called [[node (networking)|nodes]], and multiple nodes may be involved in each tier. Each type of node has a different name and all are capable of manipulating objects and executing business logic. A collection of nodes can be deployed across one or several machines. Database servers handle data storage and can also execute business logic, while application servers handle processing. In a three-tier model, presentation clients provide the user interface. JADE also provides a two-tier client that combines the abilities of an application server and presentation client. Traditionally, these three tiers would be created by combining three programs and having them communicate to form one system. Having the different programs separate like this has many advantages, the main one is that the system becomes scalable, that is, raising the power of the system involves simply adding more nodes. | |||
Designing a system like this gives the programmer a decision to consider every time they want to code in a particular function. They need to decide whether the function would run best on the database server, application server or presentation client before they begin coding as it will be difficult to change that decision once the functionality is coded into one of the tiers. | Designing a system like this gives the programmer a decision to consider every time they want to code in a particular function. They need to decide whether the function would run best on the database server, application server or presentation client before they begin coding as it will be difficult to change that decision once the functionality is coded into one of the tiers. | ||
| Line 67: | Line 69: | ||
====HTML documents==== | ====HTML documents==== | ||
JADE supports deployment of applications to the web through its HTML documents feature. These work very similarly to ASP.NET, where developers create templates of HTML pages and leave parts in the template for the program to fill in. | |||
The advantages of using HTML documents are: | The advantages of using HTML documents are: | ||