When a database works as a backend for an application, it implements an OLTP solution. This means that the database is supposed to perform a lot of small transactions on a regular basis. The car portal database we used as an example in previous chapters is an example of a typical OLTP data structure. The application working with this database executes a transaction each time a user does something: creates an account, modifies the password, enters a car into the system, creates or changes an advertisement, and so on. Each of these actions causes a transaction in the database that would create, change or delete a row/couple of rows in one or more tables. The more users work with the system, the more often the transactions are performed. The database should be able to handle the load, and its performance is measured by the number of transactions per second it can handle...
Germany
Slovakia
Canada
Brazil
Singapore
Hungary
Philippines
Mexico
Thailand
Ukraine
Luxembourg
Estonia
Lithuania
Norway
Chile
United States
Great Britain
India
Spain
South Korea
Ecuador
Colombia
Taiwan
Switzerland
Indonesia
Cyprus
Denmark
Finland
Poland
Malta
Czechia
New Zealand
Austria
Turkey
France
Sweden
Italy
Egypt
Belgium
Portugal
Slovenia
Ireland
Romania
Greece
Argentina
Malaysia
South Africa
Netherlands
Bulgaria
Latvia
Australia
Japan
Russia