In Part One, we set up a basic build environment using Webpack and Babel. We then test drove this environment by creating a simple React component.
In Part Two, we’ll enhance our build environment, then start building our Spotify client using React. By the end of this post, you’ll have a greater understanding of React components and how to create and structure them to work together.
I’ve been using the React ecosystem extensively at work during the past eight months. We’ve built apps to help us monitor our trading positions, edit our pre-trade risk checks, and control our strategies.
It’s proven a fantastic ecosystem to work with given its composable nature and approachable learning curve. With React, it’s become almost fun to deliver a consumer-grade UI for Enterprise use.
I thought I’d share what I’ve learned so far through a primer. Over three parts, I’m going to show you how to:
Messaging has multiple uses in system design. It can aid communication between application components, enable asynchronous processing, and form the basis for a distributed architecture. My last project involved receiving financial data in multiple formats, transforming it into a single canonical form, analyzing it for patterns, and forwarding findings to a web app. This mapped naturally… Continue reading
I work at a stock exchange. Last winter, we were hit with new requirements from regulators. In short, we needed to step up our market surveillance. We had to start monitoring our order activity in real-time and flag any patterns which are considered potentially abusive. To address this, I built a system using Clojure (backend)… Continue reading