All #Architecture articles

Two days after our internal resume platform moved from Firestore to Firebase SQL Connect, the page that pushed us into it was still downloading 18 MB and locking up for a minute. The new database made a better query possible. Writing that query is what made the page fast.

How Domain-Driven Design principles can shape a cleaner, more meaningful front-end architecture.

Stop writing giant if-else blocks for data transformation. Build clean, extensible code with the Function Registry pattern instead.

Because the OpenAPI specification is a specification, just like the EcmaScript, HTML or CSS specification, we can reliably build tooling upon it. This tooling allows us to optimise our OpenAPI workflows and let us save precious time.

How would you incorporate OpenAPI within your project? In this chapter, we'll explore the two main approaches to using OpenAPI and the benefits of each workflow.

OpenAPI allows us to improve effeciency between teams and interdependent projects. It allows us to describe our API in a single document. In this part of the series, we will take you through the most important parts of an OpenAPI document.

To optimize project effeciency and to ensure a good communication between teams, we need contracts for our APIs. In this article, I will explain what the OpenAPI specification is and how it can help us to create contracts for our RESTful APIs.