-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25/01/12 20:32, Ryan Macy wrote:
> Simple is exactly what I'm trying to accomplish Nico. It's a pet
> project to increase my knowledge, yet the high cost of most database
> options on PaaS providers like Heroku leads me to believe that the
> users w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25/01/12 20:29, Ryan Macy wrote:
> I was trying to say that I don't believe this would have anything to
> do with SQLite, you would have to deal with these issues regardless of
> the solution that is selected.
Those issues (identity, authentication
Larry I think we moved past this.
I was put off but the bluntness of his response, I'm not trying cause
issues.
Ryan Macy
On 1/25/12 11:29 PM, "Larry Brasfield" wrote:
>(Top-posting undone for comprehensibility.)
>Ryan Macy wrote:
Would there be any reason SQLite would have a hard tim
Simple is exactly what I'm trying to accomplish Nico. It's a pet project
to increase my knowledge, yet the high cost of most database options on
PaaS providers like Heroku leads me to believe that the users would
welcome a [very] low cost simple DBaaS implementation. SQLite also hasn't
been in the
(Top-posting undone for comprehensibility.)
Ryan Macy wrote:
Would there be any reason SQLite would have a hard time functioning in
a database as a service model?
Roger Binns replied:
[Reasonable explanation of why SQLite as a service is not a good solution,
including "introduction of latency"
>This seems inconsequential
>Huh? If you are making it available as a service then you have to care
>about authentication. And identity - how do you tell users apart and keep
>their databases separate? How will you deal with attacks from malicious
>users? How will you add a security model to s
If you're building a small web service, SQLite3 will do fine. If you
want to scale big you might be able to use SQLite3 for some pieces of
it, but you can't scale up a web service to thousands of servers with
tens of cores and one single SQLite3 DB -- that just doesn't work
given SQLite3's archite
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25/01/12 19:52, Ryan Macy wrote:
> I used API generically (not necessarily SQLites API)
You can't use SQLite's API although it wasn't clear you realised that!
> I am creating an application in python that uses an RESTful API to
> allow the user co
Yes I have used SQLite previously, but not extremely extensively.
I used API generically (not necessarily SQLites API) , the whole idea is a
side project to increase my knowledge. I am creating an application in
python that uses an RESTful API to allow the user connect to my service
and submit sta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25/01/12 18:48, Ryan Macy wrote:
> Would there be any reason SQLite would have a hard time functioning in
> a database as a service model?
SQLite lives in the same process as the code using it.
> Each user would generate a database (or many databa
10 matches
Mail list logo
