Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Add "data transfer format" to the use cases for SQLite in the "When to Use" document. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | version-3.23 |
Files: | files | file ages | folders |
SHA3-256: |
d232f16b87ce1af7109aa459ee824f27 |
User & Date: | drh 2018-04-07 11:54:16.881 |
Context
2018-04-07
| ||
12:00 | Fix a typo on the "when to use" page. (check-in: 1963430c3f user: drh tags: version-3.23) | |
11:54 | Add "data transfer format" to the use cases for SQLite in the "When to Use" document. (check-in: d232f16b87 user: drh tags: version-3.23) | |
2018-04-06
| ||
12:16 | Align the use of the "BLOB" affinity in lang_createtable.html with the definitions in datatype3.html. (check-in: e4161dc6b1 user: drh tags: version-3.23) | |
Changes
Changes to pages/whentouse.in.
︙ | ︙ | |||
62 63 64 65 66 67 68 69 70 71 72 73 74 75 | <p>There are many benefits to this approach, including improved performance, reduced cost and complexity, and improved reliability. See technical notes [file-format benefits|"aff_short.html"] and [application file-format|"appfileformat.html"] and [faster than the filesystem|"fasterthanfs.html"] for more information. <tcl>hd_fragment website {using SQLite for websites}</tcl> <li><p><b>Websites</b></p> <p>SQLite works great as the database engine for most low to medium traffic websites (which is to say, most websites). The amount of web traffic that SQLite can handle depends | > > > > | 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 | <p>There are many benefits to this approach, including improved performance, reduced cost and complexity, and improved reliability. See technical notes [file-format benefits|"aff_short.html"] and [application file-format|"appfileformat.html"] and [faster than the filesystem|"fasterthanfs.html"] for more information. This use case is closely related to the <a href="#wireproto">data transfer format</a> and <a href="#container">data container</a> use cases below. </li> <tcl>hd_fragment website {using SQLite for websites}</tcl> <li><p><b>Websites</b></p> <p>SQLite works great as the database engine for most low to medium traffic websites (which is to say, most websites). The amount of web traffic that SQLite can handle depends |
︙ | ︙ | |||
150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 | SQL database engine in this scenario. Database requests are serialized by the server, so concurrency is not an issue. Concurrency is also improved by "database sharding": using separate database files for different subdomains. For example, the server might have a separate SQLite database for each user, so that the server can handle hundreds or thousands of simultaneous connections, but each SQLite database is only used by one connection.</p> </li> <li><p><b>File archive and/or data container</b></p> <p> The [SQLite Archive] idea shows how SQLite can be used as a substitute for ZIP archives or Tarballs. An archive of files stored in SQLite is only very slightly larger, and in some cases actually smaller, than the equivalent ZIP archive. | > > > > > > > > > > > > > > > > > > > > > > | 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 | SQL database engine in this scenario. Database requests are serialized by the server, so concurrency is not an issue. Concurrency is also improved by "database sharding": using separate database files for different subdomains. For example, the server might have a separate SQLite database for each user, so that the server can handle hundreds or thousands of simultaneous connections, but each SQLite database is only used by one connection.</p> </li> <tcl>hd_fragment wireproto {data transfer format}</tcl> <li><p><b>Data transfer format</b><p> <p>Because an SQLite database is a single compact file in a [file format|well-defined cross-platform format], it is often used as a container for transfering content from one system to another. The sender gathers content into an SQLite database file, transfers that one file to the receiver, then the receiver uses SQL to extract the content as needed. <p>An SQLite database facilitates data transfer between systems even when the endpoints have different word sizes and/or byte orders. The data can be a complex mix of large binary blobs, text, and small numeric or boolean values. The data format can be easily extended by adding new tables and/or columns, without breaking legacy receivers. The SQL query language means that receivers are not required to parse the entire transfer all at once, but can instead query the received content as needed. The data format is "transparent" in the sense that it is easily decoded for human viewing using a variety of universally available, open-source tools, from multiple vendors. </li> <tcl>hd_fragment container {data container}</tcl> <li><p><b>File archive and/or data container</b></p> <p> The [SQLite Archive] idea shows how SQLite can be used as a substitute for ZIP archives or Tarballs. An archive of files stored in SQLite is only very slightly larger, and in some cases actually smaller, than the equivalent ZIP archive. |
︙ | ︙ |