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:
Lean inception helps to understand what to build.
Agile methodologies explain how to build it.
CEP deals with how to process the data.
AI/ML handles how to learn from the data.
Distributed environments are about where to run the system.
Automated infrastructure is about how to run the system.
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.
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.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
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:
Lean inceptionhelps to understand what to build.Agile methodologiesexplain how to build it.CEPdeals with how to process the data.AI/MLhandles how to learn from the data.Distributed environmentsare about where to run the system.Automated infrastructureis about how to run the system.Reactive Microservices Architectureputs everything together in a single structure.In my mind it's more natural to explain
1 → 2,3 → 4, and5 → 6, although I feel I could begin with any of the pairs1-2,3-4, and5-6since 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.
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.