5 ms·
I understand conceptually how you could architect a desktop/server OS based on a local database instead of a local filesystem, and it's deeply intriguing to me
by crazygringo 4y ago
I understand conceptually how you could architect a desktop/server OS based on a local database instead of a local filesystem, and it's deeply intriguing to me in terms of how everything could share a common data language that is far more flexible than files but far more structured than text. Presumably things like terminal output would be formatted as query results instead of text. The database wouldn't reside in files on disk, it would reside directly in blocks on disk and in-memory as required.
But this seems to be proposing a distributed database that runs across computers, which confuses me. Anything that runs across computers seems to me to be application-level, not OS-level, by definition. What does it even mean to be running a distributed database on "microkernel services" instead of on fully-fledged OS's? And then... where is the OS-level CPU coming from? If the database is distributed among computers then fine, but which computer is "running" the OS?
Both the nomenclature and distributed aspect are really throwing me off here.
- pjmlp 4y agoHave a look at IBM i (nee AS/400), it uses database instead of files, aptly named catalogs.
- skissane 4y agoDisagree, IBM i uses files: how do you create a database table in it? CRTPF command ("Create Physical File"). You create a file. And I don't know what you mean by "catalogs", in the context of IBM i. Are you talking about DB2 catalog views? (Which exist in DB2 on every other platform, and most other RDBMS have something equivalent, such as the ANSI standard INFORMATION_SCHEMA) Or are you confusing IBM i with MVS (in which the OS contains databases called "catalogs", in which you lookup a file name or file name prefix to find out which disk volume a file is stored on?)
- kmstout 4y agoThere's a cool little demo [0] of AS/400's files-as-databases concept: [0] https://www.youtube.com/watch?v=CDSgJE5mPJM https://www.youtube.com/watch?v=CDSgJE5mPJM
- marginalia_nu 4y agoA file system is a database though. Not a relational one, granted, but it's still basically nosql before it was cool.
- layer8 4y agoToday’s filesystems are more like the NoSQL equivalent of hierarchical databases, which were the very first database design, created in the 1960s, preceding RDBMSs.
- crazygringo 4y agoI don't think you can really call something a database if it doesn't have a query language, at least in contemporary practice. And I wouldn't call "cd", "ls", "mkdir", "rm", "cat" and "echo" a query language. Even the first navigational databases had a proper query language, although radically different from SQL.
- gkbrk 4y agoWould you call "get", "set", "del" and "rename" a query language? Because they are commonly used commands for Redis.
- ta988 4y agoNow add find, grep, xargs, sed, awk and put all those together with pipes
- jabbany 4y agoConsidering things like wildcards and glob matching these don't seem far off from what you'd use in a graph db query language. (E.g. something like neo4j)
- esjeon 4y ago"Language" is just an interface. You can SQL a filesystem if you want, and also can build 3rd party indexers that query engines can benefit from.
- 4y ago
- tremon 4y agoAnything that runs across computers seems to me to be application-level, not OS-level, by definition Novell Netware was also marketed as a Network Operating System, in the sense that none of its services were confined to the local machine: its entire purpose was to combine a network of computers into a single management unit.
- jasonwatkinspdx 4y agoSo I would strongly disagree with your notion that an OS cannot be a distributed system. Several OS's, such as Plan 9, were explicitly designed as distributed systems from the beginning. For Plan 9, running it on a solo computer is more the edge case than the common case they designed for, which was a small team with workstations sharing a central server. All of the computers are "running" the OS. The OS is more than one service on more than one machine.
- crazygringo 4y agoAh thank you. I had no idea. Turns out distributed operating systems were/are a thing: https://en.wikipedia.org/wiki/Distributed_operating_system https://en.wikipedia.org/wiki/Distributed_operating_system "Research and experimentation efforts began in earnest in the 1970s and continued through the 1990s, with focused interest peaking in the late 1980s. A number of distributed operating systems were introduced during this period; however, very few of these implementations achieved even modest commercial success." So looks like they're trying to keep the idea going?
- hansvm 4y ago"OS-level CPU" is just normal CPU that's been configured and handed out by some program (conventionally, the OS) for other things to use. If that initial process management program (call it an OS) also supports communicating with similar setups and receiving/dispatching jobs and queries then that's precisely the distributed OS you're looking for. You could _also_ architect a comparable system as user-space networking on top of a conventional OS, but that's by no means required.
- DSingularity 4y agoThere will be a day where the cloud becomes something like the OS
- c3534l 4y agoI think there is a very real need for a distributed operating system. Operating systems ultimately just virtualize hardware, and its clear to anyone that has used VMware or Xen that we're building such a system piecemeal and constantly reinventing the operating system wheel. I think this is absolutely where OS design is inevitably destined to evolve into.
- renox 4y agoThere's a need but don't forget that all the previous distributed OSs(Plan9, Mosix,..) didn't succeed. So 'inevitably destinated to evolve'? No..
- jdougan 4y agoI think it's gonna be like steam engines...lots of historical attempts until the stars align and suddenly people see the need.
- StillLrning123 4y agoFunny thing about steam engines is that we think about them as a thing of the past. But in reality steam engines just scaled up and turned into steam turbines, which are a backbone of society
- stonogo 4y agoThey succeeded just fine. Most people don't have a use for a distributed operating system, so they were not commercially viable. Since many of them were never meant to be commercial products, it's not really accurate to claim they were unsuccessful. The principles involved work fine to this day.
- c3534l 4y agoIt wasn't the right time yet. Virtualization has only just come to the data center and taken off. People no longer have their single expensive PC, but utilize a multitude of devices. Cloud storage is just making its way onto people's phones and devices. The full suite of VMware products is essentially already a commercially lucrative operating system for the data center / cloud. I think this is a long term trend rather than a fad. Its not the hottest new framework, but rather the culmination of incremental changes over decades. We might not call it an operating system - we'll probably give it a fancier name to generate hype. But the idea is the same none the less.
- gumby 4y ago> Anything that runs across computers seems to me to be application-level, not OS-level, by definition. Distributed OSes have been an active area of research since the 1970s at least.