as this is the most flexible architecture possible. Product strategy flops around so much, architecture has to as well.
Conversation
Replying to
What's a backend example? DevOps test events?
2
Replying to
stream processing blog.confluent.io/2015/01/29/mak tools like Spark/Samza/etc are the darling of big data crowd now not Hadoop (batch processing)
3
1
1
Replying to
basic idea is anything and everything can be modeled as a stream of events that can be reduced into some current view of reality.
1
2
Replying to
I am already on the stream bandwagon on ux and management/org structure front, now good to see mirroring goes all the way thru
1
1
Replying to
what does streaming in context of management/org structure mean?
4
Replying to
It's about managing end-to-end information flows rather than supply/distro chain. The atoms are commodity now.
2
1
Replying to
another thought here. Big concept in event processing is all data is just aggregates/views of individual events.
1
2
Replying to
also that they can be temporary and you can easily create new aggregates on an as-needed basis.
1
2
Replying to
teams in Slack-orgs seem as if they could work the same way. Teams get aggregated around hot/important data flows.
3
1
Replying to
we need another meetup around this stuff like the one we had on containers/docker in 2013
Replying to
I would go. This conversation has been helpful to me already. Understand better impedance mismatches I encounter.
1


