2014-05-07
2014-05-07. Open Source › mORMot Framework
Here are some benchmark charts about MongoDB integration in mORMot's ORM.
MongoDB appears as a serious competitor to SQL databases, with the potential benefit of horizontal scaling and installation/administration ease - performance is very high, and its document-based storage fits perfectly with mORMot's advanced ORM features like Shared nothing architecture (or sharding).
2014-05-07. Open Source › mORMot Framework
MongoDB (from "humongous") is
a cross-platform document-oriented database system, and certainly the best
known NoSQL database.
According to http://db-engines.com in April
2014, MongoDB is in 5th place of the most popular types of database
management systems, and first place for NoSQL database management
systems.
Our mORMot gives premium access to this database, featuring full
NoSQL and Object-Document Mapping (ODM) abilities to the
framework.
Integration is made at two levels:
SynMongoDB.pas unit;mORMotMongoDB.pas unit.MongoDB eschews the traditional table-based relational database structure in favor of JSON-like documents with dynamic schemas (MongoDB calls the format BSON), which matches perfectly mORMot's RESTful approach.
This second article will focus on integration of MongoDB with our ORM.
2014-05-07. Open Source › mORMot Framework
MongoDB (from "humongous") is
a cross-platform document-oriented database system, and certainly the best
known NoSQL database.
According to http://db-engines.com in April
2014, MongoDB is in 5th place of the most popular types of database
management systems, and first place for NoSQL database management
systems.
Our mORMot framework gives premium access to this database,
featuring full NoSQL and Object-Document Mapping (ODM) abilities to
the framework.
Integration is made at two levels:
SynMongoDB.pas unit;mORMotMongoDB.pas unit.MongoDB eschews the traditional table-based relational database structure in favor of JSON-like documents with dynamic schemas (MongoDB calls the format BSON), which matches perfectly mORMot's RESTful approach.
In this first article, we will detail direct low-level access to the
MongoDB server, via the SynMongoDB.pas unit.
2014-04-18
2014-04-18. Open Source › mORMot Framework
We have just released a set of slides introducing ORM, SOA, REST, JSON, MVC, MVVM, SOLID, Mocks/Stubs, Domain-Driven Design concepts with Delphi, and showing some sample code using our Open Source mORMot framework. You can follow the public link on Google Drive! This is a great opportunity to […]
2014-02-28
2014-02-28. Open Source › mORMot Framework
One of the main features you may miss when discovering NoSQL ("Not-Only SQL"?) databases, coming from a RDBMS background, is ACID.
ACID (Atomicity, Consistency, Isolation, Durability) is a set of properties that guarantee that database transactions are processed reliably. In the context of databases, a single logical operation on the data is called a transaction. For example, a transfer of funds from one bank account to another, even involving multiple changes such as debiting one account and crediting another, is a single transaction. (Wikipedia)
But are there any ACID NoSQL database?
Please ensure you read the Martin Fowler
introduction about NoSQL databases.
And the corresponding
video.
First of all, we can distinguish two types of NoSQL databases:
By design, most Graph-oriented databases are ACID!
This is a first good point.
Then, what about the other type?
In Aggregate-oriented databases, we can identify three sub-types:
2013-06-07
2013-06-07. Open Source › mORMot Framework
Our mORMot framework tries to implement security via:
- Process safety;
- Authentication;
- Authorization.
Process safety is implemented at every n-Tier level:
- Atomicity of the SQLite3 database core;
- RESTful architecture to avoid most synchronization issues;
- ORM associated to the Object pascal strong type syntax;
- Extended test coverage of the framework core.
Authentication allows user identification:
- Build-in optional authentication mechanism, implementing both per-user
sessions and individual REST Query Authentication;
- Authentication groups are used for proper authorization;
- Several authentication schemes, from very secure SHA-256 based challenging to
weak but simple authentication;
- Class-based architecture, allowing custom extension.
Authorization of a given process is based on the group policy,
after proper authentication:
- Per-table access right functionalities built-in at lowest level of
the framework;
- Per-method execution policy for interface-based services;
- General high-level security attributes, for SQL or Service remote
execution.
We will now give general information about both authentication and authorization in the framework.
In particular, authentication is now implemented via a set of classes.
2013-02-12
2013-02-12. Open Source › mORMot Framework
Up to now, our SynDB database classes were handling
ODBC, OleDB providers and direct Oracle or
SQLite3 connection.
We have added a DB.pas based layer, ready to be used with
UniDAC, NexusDB, or the BDE.
Any other TDataset based component is ready to be interfaced,
including UIB, AnyDAC or DBExpress.
The ZEOS library (in its latest 7.0.3
stable version, which works from Delphi 7 up to XE3) has also been
interfaced, but without the TDataset/DB.pas layer:
our SynDBZEOS.pas unit calls the ZDBC layer, which is not
tied to DB.pas nor its RAD components, and is therefore
faster. By the way, it will work also with the Starter edition of
Delphi (which does not include the DB components) - just like the other
"regular" SynDB classes.
This is a work in progress, any testing and feedback is welcome!
We had to circumvent some particularities of the libraries, but I guess we have
something interesting.
A dedicated "SynDBDataset" sub-folder has been created in the repository, to contain all
SynDBDataset.pas-based database providers.
SynDBNexusDB.pas unit has been moved within this sub-folder,
as SynDBUniDAC.pas + SynDBBDE.pas units have
been added.
SynDBZeos.pas has a direct access to the ZDBC layer, so
is not part of the "SynDBDataset" sub-folder.
Here is some benchmark, mainly about Oracle and
SQlite3 database access.
Of course, our direct SynDBOracle / SynDBSQLite3
layers are the fastest around, and we can see that ZDBC layer is sometimes more
efficient than the TDataset components.
2012-08-01
2012-08-01. Open Source › mORMot Framework
For real applications, retrieving objects per ID is not enough.
Your project may have the need to retrieve objects by a textual field, e.g. a
name or identifier.
In this case, you can specify a published property of the
TSQLRecord as stored false, and it will be
defined as an unique column in
the underlying database.
For instance, in the
latest version of our performance benchmark sample code, you can define the
UNIK conditional to define both LastName and
FirstName properties as unique:
type
TSQLRecordSample = class(TSQLRecord)
private
fFirstName: RawUTF8;
fLastName: RawUTF8;
fAmount: currency;
fBirthDate: TDateTime;
fLastChange: TModTime;
fCreatedAt: TCreateTime;
published
property FirstName: RawUTF8 index 40 read fFirstName write fFirstName
{$ifdef UNIK}stored false{$endif};
property LastName: RawUTF8 index 40 read fLastName write fLastName
{$ifdef UNIK}stored false{$endif};
property Amount: currency read fAmount write fAmount;
property BirthDate: TDateTime read fBirthDate write fBirthDate;
property LastChange: TModTime read fLastChange;
property CreatedAt: TCreateTime read fCreatedAt write fCreatedAt;
end;
During insertion or update of records, the database will have to check for
uniqueness of those column values. It will have an additional performance cost,
since a search of the new value is to be performed among existing values.
In order to speed-up the process, a so-called index is created at the
database level.
As a consequence, further lookup using this property will benefit for this
index, and will be much faster than a classic loop throughout all
data.
In the mORMot core, we just made some modifications related to this feature:
TSQLRestServerStaticInMemory internal engine, and
insertion will have no speed penalty any more.2012-07-25
2012-07-25. Open Source › mORMot Framework
After having tested and enhanced the external database speed (including BATCH mode), we are now able to benchmark all database engines available in mORMot.
In fact, the ORM part of our framework has several potential database
backends, in addition to the default SQLite3 file-based engine.
Each engine may have its own purpose, according to the application
expectation.
The following tables try to sum up all available possibilities, and give some benchmark (average rows/seconds for writing or read).
In these tables:
SynDB;TObjectList' indicates a
TSQLRestServerStaticInMemory instance either static (with no
SQL support) or virtual (i.e. SQL featured via SQLite3 virtual table
mechanism) which may persist the data on disk as JSON or compressed
binary;BeginTransaction / Commit calls;SELECT * FROM table WHERE ID=?);SELECT * FROM table);ACID is an acronym for "Atomicity Consistency Isolation
Durability" properties, which guarantee that database transactions are
processed reliably: for instance, in case of a power loss or hardware failure,
the data will be saved on disk in a consistent way, with no potential loss of
data.2012-04-20
2012-04-20. Open Source › mORMot Framework
Our latest mORMot feature is interface-based service implementation.
How does it compare with the reference of SOA implementation (at least in the Windows world) - aka WCF?
"Comparaison n'est pas raison", as we use to say in France.
But we will also speak about Event Sourcing, and why it is now on our
official road
map.
Comparing our implementation with WCF is the opportunity to make our framework
always better.
