(Migrated) SQLite support

(This message has been automatically imported from the retired mailing list)

Hello,

as of now it’s possible to run Zato clusters using SQLite instead of
Postgres, Oracle or MySQL.

This is a rather drastic change in that there is no central SQL database
in a cluster if SQLite is used.

This comes at a certain cost - one cannot use hot-deployment if there is
more than one server in a cluster. In other words, such clusters can:

  1. Have multiple servers but no hot-deployment
  2. Use one server with hot-deployment

Scenario 1. is a fairly common case in the twelve-factor app methodology …

http://12factor.net/

… where hot-deployment is never used anyway.

Scenario 2. on the other hand is great for development - one doesn’t
need to set up and manage accounts in an SQL database now.

And naturally, there are indeed environments with one server in a
cluster using hot-deployment - their architecture can now be simplified
if need be.

On 05/27/2014 04:37 PM, Dariusz Suchojad wrote:

as of now it’s possible to run Zato clusters using SQLite instead of
Postgres, Oracle or MySQL.

This is a rather drastic change in that there is no central SQL database
in a cluster if SQLite is used.

I should also add that an SQLite database is generated automatically for
new clusters.

No user action is needed, simply specify that odb_type is sqlite and
you’re good :slight_smile:

For instance, here’s how to create an SQLite-backed quickstart cluster

$ zato quickstart create ~/env/qs-1 sqlite localhost 6379

localhost:6379 is the connection to Redis, which stays, but an SQLite
database is created on the fly.

On 05/27/2014 04:37 PM, Dariusz Suchojad wrote:

as of now it’s possible to run Zato clusters using SQLite instead of
Postgres, Oracle or MySQL.

This is a rather drastic change in that there is no central SQL database
in a cluster if SQLite is used.

I should also add that an SQLite database is generated automatically for
new clusters.

No user action is needed, simply specify that odb_type is sqlite and
you’re good :slight_smile:

For instance, here’s how to create an SQLite-backed quickstart cluster

$ zato quickstart create ~/env/qs-1 sqlite localhost 6379

localhost:6379 is the connection to Redis, which stays, but an SQLite
database is created on the fly.