caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Markus Rudy <webmaster@burgerdev.de>
To: caml users <caml-list@inria.fr>
Subject: [Caml-list] OCaml for cloud-native apps
Date: Fri, 18 May 2018 22:17:59 +0200	[thread overview]
Message-ID: <4c05eaff-8613-c9c8-fc65-30340b169010@burgerdev.de> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1358 bytes --]

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: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2018-05-18 20:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-18 20:17 Markus Rudy [this message]
2018-06-02 19:56 ` Yawar Amin
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=4c05eaff-8613-c9c8-fc65-30340b169010@burgerdev.de \
    --to=webmaster@burgerdev.de \
    --cc=caml-list@inria.fr \
    /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;
as well as URLs for NNTP newsgroup(s).