8 ms·
This is an awesome idea. Every now and then a revolutionary concept comes along that points the way to all future computing. This is the future of any public fa
by andrewstuart 13y ago
This is an awesome idea. Every now and then a revolutionary concept comes along that points the way to all future computing. This is the future of any public facing computer. You must understand the concepts here if you are involved with web development at any level. If you haven't yet wrapped your head around this, then you should.
The key concept here is about security.
Imagine you could compile your web application/website into an application that has nothing else but the required network drivers and minimal hardware drivers needed to execute. That is (as far as I can tell from a brief look) what Mirage does. Using such an approach there's nothing for hackers to log in to - no shell to use, no other insecure cruft on the system potentially leaving holes. The attack surface of such a system is extremely low relative to putting fully powered and configurable interactive operating systems onto the Internet.
Hackers are showing that almost everything is hackable without expensive, constant, expert attention to security of every aspect of your systems. Even then zero day exploits expose systems within seconds or minutes of the exploit becoming known.
This is not to say that such systems cannot be hacked, but rather to say that in such an approach the attack surface is dramatically lower than in current approaches to deployment.
Perhaps more likely to change the way that people think about the concept of web application development in the longer term is that the application/server allows for the possibility of "high resolution server instances" in which a virtual machine can be started in milliseconds, perhaps to service only one query, and then vanish again. Instead of renting your instance from Amazon that runs per hour and does nothing most of the time, your infrastructure will be truly scalable with nothing running at all until its needed and then precisely as much computing power will be used as is required to meet the inbound demand. No longer will you need to "start a web server" which then chugs and rumbles into existence as all its various unneeded-at-most-times processes start. Instead, connect your application/server AMI to the Amazon spot instance marketplace.
- alco 13y agoThat is partly true. But if there is nothing to hack into, there will also be nothing to log in to for an admin or an ops person. In the case of Erlang, for instance, it provides a built-in remote shell which allows one to connect to a running Erlang process, get multitude of information about the VM, loaded code, etc. As long as there is a convenient way to maintain a running system, that same way can be used for hacking.
- andrewstuart 13y agoPerhaps deployment and management practices will change to take into account this approach to management, rather than forcing the existing insecure approach onto dedicated applications/servers.
- edwintorok 13y agoI wouldn't mind to have an SSH shell to MirageOS though. Perhaps something like TinySSH could be translated to OCaml?
- alco 13y agoYou mean a pseudo-shell? Because when you're running OCaml on top of a hypervisor, there is no OS and shell in the traditional meaning of those words. So nothing to connect to.
- edwintorok 13y agoYeah, I don't mean a classic shell or even the OCaml toplevel. But it would be nice to provide a "standard" way for applications to define their own commands, and to provide some builtin commands for monitoring (memory usage, open connections, etc.).
- alco 13y agoI'm afraid that going in the direction of using single-language platforms only draws us further for having a standard way of managing them.
- edwintorok 13y agoHmm, but there could still be a libraries that take care of the common tasks: how to talk to an SSH client, how to get some basic info from the Mirage kernel, etc. Since these unikernels are so specialized maybe SSH would be overkill, but I wouldn't want each developer to invent their own potentially insecure way of communicating with the unikernels.
- anonymousDan 13y agoThe main issue I see is that everything has to be done in ocaml no? What about the maintenance overhead too?
- andrewstuart 13y agoThe dedicated application/server is such a powerful idea and security is such a big problem that perhaps some time in the future people will see the idea of "directly putting an operating system on the Internet" as risky madness. All development environments that matter will somehow come to support creation of dedicated application/servers.
- deleted 13y ago[deleted]
- rjsw 13y agoThere is nothing stopping someone from doing something similar in a different language. I made a start on modifying Movitz to build a Lisp system that would run on top of Xen.
- andrewstuart2 13y agoHoly crap, it's you! Sorry I tried to reset your password the other day. I thought I'd already signed up and forgotten. On a more on-topic note however, aside from the benefits of running any kernel, such as windows, I wonder if there are any practical benefits of something like this vs something like CoreOS/docker. I'm sure since it's Xen you could run a windows kernel on Linux, but aside from that, I don't know.
- andrewstuart 13y agoHoly crap, it's me! I did get the password reset in the middle of the night and wonder what that was about then I saw andrewstuart2 and realised what had happened. Seems we are the same person. Do you spend your life saying "It's spelled S-T-U-A-R-T", then people say "errrr, S-T-E-U-W-A-R-T?".
- andrewstuart2 13y agoHaha the worst I've gotten is "Okay, S-T-U-W-A-R-T?". I suppose there has to be some downside to having some royal Scottish blood.
- amirmc 13y agoThis thread had me really confused for quite a while. I thought it was one person replying to their own messages.
- pstuart 13y agoIndeed. One must be eternally vigilant with the name.
- andrewstuart 13y agoAre you Paul? My brother's name is Paul.
- avsm 13y ago> On a more on-topic note however, aside from the benefits of running any kernel, such as windows, I wonder if there are any practical benefits of something like this vs something like CoreOS/docker. There are millions of lines less of code involved in the deployed Xen unikernel, since there's no Linux userspace/kernel divide involved any more. You can also use the same application source code just fine with CoreOS/Docker if you prefer, since it can also compile to normal POSIX binaries that use kernel sockets (via `mirage configure --unix` instead of `mirage configure --xen`). This is the main benefit of using modular OCaml code that can swap out entire subsystems at compile time.