Discussion: SQLITE for large applications

[Áureo Dias Neto]

Friends, I run information systems and always my teachers say that sqlite is not reliable to use as a database for production environment ..

The problem with this statement is that they can not give me a good argument to support this idea, and also, I've done several tests with a few thousand records and the bank behaves well ..

I wanted to know your opinion on this subject, SQLITE is reliable and worth it or do not use it as a bank for the production environment .. hugs!

[António Ramos]

If you use the scheduler, FORGET SQLITE!! "database locked" will be your worst enemy!

--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups "web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Áureo Dias Neto]

Antonio,

I get it with cron?

[Dave S]

I think the main issue with sqlite is scaling.  If you have a lot of requests, or many requests with the scheduler running, you will see performance slip, with the DATABASE LOCKED status being part of that (the other is that sqlite doesn't have a dedicated isam/vsam driver, but uses the unix/linux/windows (and macOS?) filesystem).

I'm using sqlite in a production environment with a scheduler, but very low traffic.  I also use sqlite in my development environment for a variety of projects, but none of them have heavy traffic either.

/dps