GT.M: Жоғары өнімділік кілт-мәнді дерекқоры және M тілі платформасы

GT. M is a high throughput key–value database engine optimized for transaction processing. (It is a type also referred to as "schema less", "schema free", or "NoSQL".) GT. M is also an application development platform and a compiler for the ISO standard M language, also known as MUMPS. GT. M, an abbreviation for Greystone Technology M, was developed by the Greystone Technology Corp in the 1980s. It is an implementation of ANSI standard M for AIX and Linux. In addition to preserving the traditional features of M, GT. M also offers an optimizing compiler that produces object code that does not require internal interpreters during execution. The database engine, made open source in 2000, is maintained by FIS. GT. M is used as the backend of their FIS Profile banking application, and it powers banks in Spain, France, Italy, the Netherlands, Romania and India; Capital One 360 in the United States; Tangerine (Scotiabank) in Canada; Atom Bank; Tandem Bank; Sainsbury's Bank; Scottish Widows and Barclays Direct in the UK. It is also used as an open source backend for the Electronic Health Record system WorldVistA and other open source EHRs such as Medsphere's OpenVista. It is listed as an open source healthcare solution partner of Red Hat. Today it consists of approximately 2 million lines of code.

GT. M consists of a language subsystem, a database subsystem, and utility programs. The language subsystem and database subsystem are closely integrated, but each is usable without the other. The language and database subsystems share common data organization and typing.

Unlike the database where global variable nodes must fit within a database block, local variable strings can grow to 1MB. The GT. M run time provides dynamic storage allocation with garbage collection. The number of local variables and the number of nodes in local variables are limited only by storage available to the process. The default scope of a local variable is the lifetime of a process. Local variables created within routines using the New command have more limited scope. GT. M routines are dynamically compiled and linked for execution in the address space of each process. With the exception of the 32 bit implementation of GT. M for the x86 Linux platform, object modules can also be placed in shared libraries with the standard ld command, in which case the memory used is shared. This is important because an application such as VistA has over 20,000 routines whose compiled object code exceeds 200MB. A large hospital running VistA can have thousands of concurrently running user processes. With a couple of small exceptions, GT. M includes a nearly complete implementation of ISO standard M (affectionately known as MUMPS for historical reasons). In GT. M, M code can freely call out to C code (or code in other languages with a C compatible interface), and C code can freely call in to M code (so the top level program can be a C main ). For example, is a GT. M module in CPAN, m python for access from Python or EGTM binding for Erlang. Web services written in GT. M can be deployed under an Internet super server such as inetd or xinetd. Web enabled applications can use layered software such as EWD or CFMumps.

On Linux on x86 64 & IA 32 (x86), and on OpenVMS on Alpha/AXP, GT. M is released as Free / Open Source Software (FOSS) under the terms of the GNU Affero General Public License, version 3. On other platforms, it is available under proprietary licenses.

GT. M is predominantly used in healthcare and financial services industry. The first production use of GT. M was in 1986 at the Elvis Presley Memorial Trauma Center in Memphis, Tennessee. Through FIS Profile, it powers banks in the United States, Canada, Spain, France and Italy. SQL and ODBC access to GT. M databases exists as separate commercial products.