Remove articles breaking-down-the-monolith-1
article thumbnail

Seamlessly Swapping the API backend of the Netflix Android app

The Netflix TechBlog

How we migrated our Android endpoints out of a monolith into a new microservice by Rohan Dhruva , Ed Ballot As Android developers, we usually have the luxury of treating our backends as magic boxes running in the cloud, faithfully returning us JSON. Background The Netflix Android app uses the falcor data model and query protocol.

Latency 233
article thumbnail

The Three Cs: Concatenate, Compress, Cache

CSS Wizardry

I began writing this article in early July 2023 but began to feel a little underwhelmed by it and so left it unfinished. In this post, I’m going to break these processes down into each of: ? Concatenating our files on the server: Are we going to send many smaller files, or are we going to send one monolithic file?

Cache 291
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Jamstack CMS: The Past, The Present and The Future

Smashing Magazine

In this post, we’re taking a stroll down memory lane to look at the CMSs that gave rise to the Jamstack CMSs we have today and peek beyond the horizon of what’s next. Jamstack CMS: The Past, The Present and The Future. Jamstack CMS: The Past, The Present and The Future. Mike Neumegen. 2021-08-20T08:00:00+00:00. 2021-08-20T09:19:47+00:00.

Ecommerce 139
article thumbnail

Frankenstein Migration: Framework-Agnostic Approach (Part 2)

Smashing Magazine

In this article, we’ll be putting all the theory to the test by performing step-by-step migration of an application, following the recommendations from the previous part. For this article, as a starting point, I picked a jQuery application from the TodoMVC project — an example that may already be familiar to a lot of you.

Storage 66
article thumbnail

Transforming enterprise integration with reactive streams

O'Reilly Software

In this article, we will discuss the need for—and how to achieve—modernization in the field of enterprise integration. This is mixing concerns and leads to code that becomes strongly coupled, monolithic, hard to write, hard to read, hard to evolve, hard to test, and hard to reuse. Let’s dive into this concept for a bit.

article thumbnail

The Challenges and Traps of Architecting Sociotechnical Systems

Strategic Tech

Monolithic architectures do not allow us to invest in high ROI parts of the system without spreading our investments across low value parts of the system, because everything is tightly coupled. Nicole Forsgren and Jez Humble report this finding in their recently-published book Accelerate , drawing on their extensive empirical research. “If

Systems 40
article thumbnail

How We Improved SmashingMag Performance

Smashing Magazine

We were designing and building things, setting up new products, refactoring the components, and publishing articles. The entire site is built with progressive enhancement in mind, meaning that you, dear reader, can read every Smashing article in its entirety without the need to boot the application at all. We had to fix that.