DEV Community

loading...

Discussion on: Building for Scale? Make a R.A.D.I.C.A.L. System!

Collapse
turnerj profile image
James Turner • Edited

Interesting article though I am curious why you chose to go through the list L-to-R rather than R-to-L, it caught me off guard while I was reading it given the acronym you've coined.

Your article did help me realise some terms for things I was already looking into like CEP so thanks for that! :)

Collapse
renatocf profile image
Renato Cordeiro Ferreira Author • Edited

Hi James, thanks for your comment!

I think this approach is more constructive, that is, it reminds me of the steps I would think about when building a system with these techniques:

  1. Lean inception helps to understand what to build.
  2. Agile methodologies explain how to build it.
  3. CEP deals with how to process the data.
  4. AI/ML handles how to learn from the data.
  5. Distributed environments are about where to run the system.
  6. Automated infrastructure is about how to run the system.
  7. Reactive Microservices Architecture puts everything together in a single structure.

In my mind it's more natural to explain 1 → 2, 3 → 4, and 5 → 6, although I feel I could begin with any of the pairs 1-2, 3-4, and 5-6 since they talk about planning, data and infrastructure respectively. I also like ending with the architecture because it is really what defines the system. In the end this coincided with the acronym backwards :)

I'm glad you learned some interesting new terms! Take a look at the e-book Fast Data Architectures for Streaming Applications by Dean Wampler, it's one of my inspirations for this section about big data and complex event processing.

Collapse
turnerj profile image
James Turner

Yeah, I see what you mean when looking at it like that - each point builds upon the next. It is just a shame that order isn't the same order as the actual letters in the acronym - L.A.C.I.D.A.R just doesn't have the same ring to it.

Forem Open with the Forem app