TMS RemoteDB 1.9.1 for Tokyo
TMS RemoteDB allows you to create database applications that perform SQL operations on a remote http server, instead of a database server, using a TDataset descendant. This makes it easy to convert existing Delphi client-server applications into 3-tier applications with minimal changes in source code.
Optimized memory usage
Keeps existing component behavior (like TFieldDefs, for example)
Requires minimum code change in client application
Supports FireDac, dbExpress, UniDac, among others
The RemoteDB Server is a Delphi application/service that listen to http requests. When clients perform requests, the RemoteDB Server will forward the requests to the actual database server being used, using the specified database-access component. The SQL is performed and the results are returned back to the client. You can choose the components that will perform the SQL statements from a wide-range of options such as FireDac, dbExpress, dbGo (ADO), among others, using component adapters. The SQL database can be any database server supported by the components used, and must be thread-safe (most are).
From the Delphi client application, you can use as many TXDataset components as you need to perform the regular SQL operations. All TXDataset components are linked to a TRemoteDBDatabase component via a Database property. The RemoteDBDatabase component is the one in charge of forwarding the SQL requests to the RemoteDB Server and retrieving back the values. All operations on the client are transparent and just like any TDataset usage: you specify the SQL statement, Open the dataset (or ExecSQL), define the list TField components, Params, connect TDatasource components to it, etc..
Wide Range of Database Component Access at Server Side
When building the server, you can use a wide range of database-access component to connect to your database. This has many advantages:
You can use your existing know-how on a specific component set;
You can fine-tune your server side with specific options that your components provide to you;
Your client application will behave exactly like the component you use on server side. This allows you much bigger compatibility and easy transition to TMS RemoteDB. If your existing client application uses FireDAC, for example, you can use it at server side, making your client-side TXDataset behaves almost exactly as a TFDQuery. It's the same for all other components supported by TMS RemoteDB.
Http client available in Windows, macOS, iOS and Android
Support for Http Secure (Https)
Transparent handling of chunked and gzip-encoded responses
Http server based on http.sys stack (Windows only - minimum Vista and Server 2008)
Support for Http Secure (Https)
TGenericDatabase component for direct database server connections, in a traditional client-server architecture
Kernel-mode caching and kernel-mode request queuing (less overhead in context switching)
Multiple applications/process can share (respond) the same port (at different addresses)
Secure Sockets Layer (SSL) support in kernel-mode
TMS Aurelius Integration
If your application is already using our ORM framework TMS Aurelius for database access, then making it a 3-tier application with TMS RemoteDB will require just a few lines of code. TMS Aurelius provides a new adapter for RemoteDB that you can use as the connection to your database (IDBConnection interface) pretty much like the other options like FireDac, dbExpress, UniDac, etc ... You don't need to change a single line in your Aurelius application - just change the connection to use TMS RemoteDB and it becomes 3-tier.
Supported Data-Access components
Advantage Database server