SQLite Is Serverless
291–300 of 453 posts
Re: SQLite Is Serverless
#292> Of those that are serverless, SQLite is the only one known to this author that allows multiple applications to access the same database at the same time. IIRC, MS Access allowed that, which explained a lot of its popularity.
This was a standard feature of flat file databases in the early 90s. There were many products. They often had an ODBC driver, which provided a SQL front end. dBase .dbf files were often used for storage. The arcane file locking in Windows is intended for exactly this kind of application. Apart from quality (!), SQLite's main advantage over these products is broad platform support. And continued existence.
Re: SQLite Is Serverless
#293Earlier quoted context omitted.
Would you mind elaborating on your ETL process a little more? Im a junior DE and curious about how I would implement this
It's pretty straightforward, really. I construct the .sqlite database from scratch each time in Python, building out table after table as I like it. Some configuration data is loaded in from files first. This could be some default values or even test records for later injection. The input data is loaded into the appropriate tables and then indexed as appropriate (or if appropriate). It is as "raw" as I can get it. Ea…
Re: SQLite Is Serverless
#294> It is important to understand these two different definitions for "serverless". When a database claims to be "serverless", be sure to discern whether they mean "classic serverless" or "neo-serverless". It's really not important to understand that distinction, because this author seems to be the only one making it. Everyone knows what "serverless" means at this point, and it's not an embedded DB.
Re: SQLite Is Serverless
#295Earlier quoted context omitted.
File formats don't have an API. > SQLite is a file format with a familiar API and uses SQL as the logic for searching/adding data to the file. That description is for a library, not a file format. SQLite is a library, that saves to a convenient format and allows you to query the file using the SQL syntax. File formats dont have "logic". You are arguing the equivalent that Word is a file format. While there is a Word…
> File formats don't have an API. So when you read/write to any other file format, you just read/write bytes directly to/from disk and re-implement the parsing and read/write logic in your own code every time? > File formats don't have "logic". Every file format has logic otherwise it's just random entropy in an arbitrarily long byte stream on a disk. How to read/parse and interact with that format depends entirely o…
Re: SQLite Is Serverless
#296Earlier quoted context omitted.
>There is an agreed upon def of serverless. Sorta but not really. The fact people have worked backwards from marketing names to try and constructively define inherently self-contradictory branding (rather than create a descriptive category into which we place questionable names and ignore them) is an embarrassment for everyone except the marketing departments.
It's called a buzzword, nothing more nothing less, it's like "cloud computing", eventually it becomes meaningless.
Ill give u that its hard to discern when a thing is a real change and when it isnt, as the titans of industry try to peacock around.
Id just examine what they actually mean, for good measure. Theyre trying to sell things they have no idea about - but thats why the hierarchy of commerce is.
Re: SQLite Is Serverless
#297Earlier quoted context omitted.
It's pretty straightforward, really. I construct the .sqlite database from scratch each time in Python, building out table after table as I like it. Some configuration data is loaded in from files first. This could be some default values or even test records for later injection. The input data is loaded into the appropriate tables and then indexed as appropriate (or if appropriate). It is as "raw" as I can get it. Ea…
Awesome - elegantly simple using very common technologies.
I have gotten some CS students who were about to shoot flies with various cannons turned on to SQLite. I kept a couple of the decent books about it nearby and would shove it into their hands at that point. Usually a week later they would be raving about it.
Re: SQLite Is Serverless
#298Choose your own definitions... but SQLite is not serverless by common parlance. Author creates two definitions for serverless which don't match the common usage. Serverless is more about DevOps / deploy experience than how the program leverages OS processes internally. Apparently MS and AWS are ISPs? Maybe SQLite could be serverless if you defined it as incapable or running as a server on its own?
They have their own IPs and global networking infrastructure
Re: SQLite Is Serverless
#299Earlier quoted context omitted.
Penny wise pound foolish. I had a president waste two to three hours a day instead of using a 40 dollar service to take care of the incredibly simple and repetitive task. Eventually when I was planning to leave anyways I asked him what his time was with per hour. I guess it was less than minimum wage at the time. (5.25 an hour) I'm probably going to have nightmares filled with screens of the access database corruptio…
What's anyone's time worth? Might have kept him from doing something foolish.
Re: SQLite Is Serverless
#300I think a good under-appreciated use case for SQLite is as a build artifact of ETL processes/build processes/data pipelines. Seems like lot of people's default, understandably, is to use JSON as the output and intermediate results, but if you use SQLite, you'd have all the benefits of SQL (indexes, joins, grouping, ordering, querying logic, and random access) and many of the benefits of JSON files (SQLite DBs are jus…
With the right pragmas it is both faster and more compact than JSON. It is also much more "human readable" than gigabytes of JSON.
I only wish there was a way to open an http-fetched SQLite database from memory so I don't have to write it to disk first.