3 ms·
> That sounds controversial but it is clearly true - most of the world is moving towards REST APIs returning structured objects (JSON documents). Yes, but mos
by indymike 5y ago
> That sounds controversial but it is clearly true - most of the world is moving towards REST APIs returning structured objects (JSON documents).
Yes, but most RESTful apis are backed by an OS that is file oriented. Why? because the server deals with persistence while the API deals with compute. The Windows approach is not winning, hosting APIs on the file oriented OS works better for most. Why? because ultimately APIs are a compute problem not a persistence/storage problem. That said, for interacting with a RESTful api, what tool do you use? A programming language like JavaScript, C#, Python, or Java or a shell scripting language like bash, zsh, or PowerShell?
- JasonFruit 5y agoCompute is a verb. I will die on this hill.
- emteycz 5y agoIt can be both. Many words are both (or even more than these 2).
- Someone1234 5y ago> Yes, but most RESTful apis are backed by an OS that is file oriented. No? Most RESTful APIs are backed by databases. There's are a lot of variance there (Sql, NoSql, Cloudy Vs. Monothithic) but it isn't files. Even for file storage and delivery databases BLOB storage are often used rather than filesystem files. When all you're using a filesystem for is storing a large continuous memory-mapped blob so that you can avoid interacting with the filesystem's APIs almost entirely, you aren't exactly championing a filesystem's utility in the internet age. I'd go as far as to say that directly exposing filesystem files to the outside world is an anti-pattern (because it doesn't scale).
- ubercore 5y agoIn the context of a file-based vs api-based shell scripting language, I think the point stands though. That's the main problem with the original statement, I think.