Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Yawar Amin <yawar.amin@gmail.com>
To: Markus Rudy <webmaster@burgerdev.de>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml for cloud-native apps
Date: Sat, 2 Jun 2018 15:56:04 -0400	[thread overview]
Message-ID: <CAJbYVJJ02ir+_iiBc4w39voQP+unMozJjKdbS+sXR=mF3-14EQ@mail.gmail.com> (raw)
In-Reply-To: <4c05eaff-8613-c9c8-fc65-30340b169010@burgerdev.de>

[-- Attachment #1: Type: text/plain, Size: 1956 bytes --]

Hi Markus, check out https://mirage.io/

Anil Madhavapeddy's team has been working on the Mirage unikernel for
several years and they were recently acquired by Docker. The value
proposition is being able to compile a kernel and any other stack you need
right inside your server and spin up a new instance in a few milliseconds
as soon as a request comes in. Anil spoke about it in this classic episode
of the FLOSS Weekly podcast: https://twit.tv/shows/floss-weekly/episodes/302

Cheers,

Yawar

On Fri, May 18, 2018 at 4:17 PM, Markus Rudy <webmaster@burgerdev.de> wrote:

> Hi all,
>
> I started writing OCaml recently, coming from a background of Scala and
> Python. My interest was triggered by a HackerNews post announcing an
> MOOC [1] for a language I never heard of before. As you might
> comprehend, I was quickly pulled into this amazing world of global type
> inference, multi-paradigm programming and native compilation.
>
> Since my day job is heavily focused on cloud development, I also came
> round to write some Go code. You can tell that this language is designed
> for containers, but what struck me as odd were the many parallels that I
> saw to OCaml - static compilation to native code, object oriented
> programming, first-class functions. Made me wonder if OCaml would be a
> good fit for running in, say, Kubernetes.
>
> I wrote a simple TCP utility to accompany my mail server, which is
> running on k8s, and after having dealt with some quirks I found that the
> language and ecosystem fit the cloud-native paradigm quite nicely. It
> also motivated me to write some of my findings up [2] and see if I can
> come up with some cool use cases.
>
> Are you deploying OCaml in containers? Are you aware of some libraries
> and/or tooling to accelerate developing OCaml for the cloud?
>
> Cheers, Markus
>
> [1]: https://www.fun-mooc.fr/courses/parisdiderot/56002S02/session02/about
> [2]: https://github.com/burgerdev/cloudtools
>
>

[-- Attachment #2: Type: text/html, Size: 2718 bytes --]

  reply	other threads:[~2018-06-02 19:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-18 20:17 Markus Rudy
2018-06-02 19:56 ` Yawar Amin [this message]
2018-05-19 10:39 Markus Rudy
2018-05-22 14:07 ` Gerd Stolpmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJbYVJJ02ir+_iiBc4w39voQP+unMozJjKdbS+sXR=mF3-14EQ@mail.gmail.com' \
    --to=yawar.amin@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=webmaster@burgerdev.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox