CEO, Perry Street Software. Developer. 🏳️‍🌈
We need more desserts in our architectural diagrams! Photo by Annie Spratt on Unsplash

We started this 6-part series on how to build web APIs by introducing the variety of architectures that have been proposed or put into use by various languages and frameworks over the years. Among the most commonly discussed architectures online is the Clean architecture, which aspires to produce a separation…

Don’t get tangled up by your .Zip operation! Photo by Mikel Parera on Unsplash

Our mobile client has invested heavily in reactive programming. In addition to providing cleaner design patterns for us to interact with asynchronous services (network API calls, disk reads, etc), reactive programming enables us to write near-identical code on both Android and iOS.

Note the use of the term near-identical. There…

Do you need all these classes? Do cookies need chocolate chips? YES! Photo by Mae Mu on Unsplash

It’s time to see what a Clean API endpoint actually looks like in practice. Per our earlier blog post about the Endpoint Responsibility Checklist, we know that the steps in an execution path in response to an HTTP request are:

🔵Receive→🟢Validate→🔴Validate→🟢Enqueue→🟢Respond

Note the line above — we are going to…

Light and Dark. Success and Failure. Functional and Reactive. Photo by Andrew Karn on Unsplash

In order to have an “architecture” to your code, you need a map and a path, a diagram and some arrows. But what, exactly, do we mean by a “path” — what is the nature of the arrows and how do they behave?

Put another way — as we pass…

Eric Silverberg

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store