Home
Ilyas Toumlilt

Ilyas Toumlilt

PhD, Distributed Systems

Contact me

Intro

Hello World! Welcome to my corner of the web.

Here you’ll find writing about my Distributed Systems Research, building the Concordant Startup, my Open Source contributions, previous PhD Thesis contributions, and the engineering ideas I keep coming back to.

I also teach operating systems at Sorbonne University and occasionally in engineering schools in Grenoble, Paris and Zurich.

Beyond research, I’m curious about technology, blockchain systems, and spending unreasonable amounts of time in running shoes.

More details about me

Latest Projects & Blog posts

The Concordant.io Platform

  • open source
  • project

Concordant is a startup born from distributed systems research, turning local-first data, edge collaboration, and consistency guarantees into a developer platform.

Concordant brings local-first data, edge collaboration, CRDTs, and stronger consistency guarantees into a developer platform for mobile and collaborative applications.

View on GitHub More details

PhD Graduation

A summary list of my PhD thesis contributions

A ceremony-day look back at four years of PhD work: thesis manuscript, publications, open-source prototypes, research collaborations, and teaching.

More details

PhD Thesis Defense

(Archive) Livestream video and documents

21 Dec 2021

Highly-Available and Consistent Group Collaboration at the Edge with Colony

Published at the 22nd International Middleware, Dec 2021, Québec, Canada

01 Nov 2021

AntidoteDB

The geo-replicated database behind the first edge prototype of my thesis work, and one of the open-source systems I contributed to during my PhD.

24 Apr 2021

See older articles and projects ...

My Github Feed

GitHub contributions chart
Ilyas Toumlilt itoumlilt

  1. itoumlilt reviewed pull request #91 at criteo/node-disruption-controller

    commented

  2. itoumlilt commented on pull request #91 at criteo/node-disruption-controller

    Ok: false, Preparing: false is already how a refused budget is marked (terminateAllImpactedBudgets reads it as "refused and nothing has been started"). So anyt…

  3. itoumlilt commented on pull request #91 at criteo/node-disruption-controller

    This runs on every reconcile while the budget waits: at least once per retry interval, plus any other event. A 30m notice at the default 1m interval counts abo…

  4. itoumlilt commented on pull request #91 at criteo/node-disruption-controller

    The opening is never compared with retry.deadline. If startDate - noticePeriod is after the deadline, the disruption waits, then gets rejected by the internal…

  5. itoumlilt commented on pull request #91 at criteo/node-disruption-controller

    On your first open point, I'd drop the fallback. retry.deadline is the latest time the disruption can be granted, not when it starts. Using it as the anchor ha…

  6. itoumlilt reviewed pull request #13 at criteo-forks/strimzi-kafka-operator

    LGTM

  7. itoumlilt reviewed pull request #13 at criteo-forks/strimzi-kafka-operator

    changes_requested