Thomas Coopman - Infinite Tree

On the meetups I attend, some people know me as the Elm guy. Yet, when reading the title of this post, you can see that I’m going for Bucklescript lately. In this post I’m going to try to explain my choice for Bucklescript. If you are in doubt, maybe some points in this post can help, but my advice would be to just try and research both languages and see for yourself. »

Recently I’ve started using Bucklescript (and Reason) over Elm for various reasons (Something I might blog about later). In this post I’m exploring integrating Bucklescript with Typescript. Let’s start with a blank typescript project with webpack You can find the inital commit of a Typescript project here. There is nothing special in this commit, some npm dependencies: source-map-loader, ts-loader, typescript, webpack, webpack-dev-server. The ts-config.json file is generated with tsc --init, nothing is changed. »

Tonight I’m giving a talk at Fronteers about Frontend microservices. Mind you, I don’t want to go into what a microservice is, so a talk about Frontend services is fine as well. What is important for me is that we’re not building a big ball of frontend. We’re paying so much attention to having a good architecture on the backend, with lots of (micro)services but at the same time, we’re building one huge single page application (SPA). »

In this post I’m exploring some ways of modelling aggregate boundaries in an event sourced system. This is mostly to crystallise some thoughts that I had after some event storming sessions, but it might be interesting to someone else. The domain I’m using in this post is the domain that Michel Grootjans and I have created for the workshop Playing with projections (We already gave it a few times, for example at DDD Europe and will also give a session at I T. »