@vgr as this is the most flexible architecture possible. Product strategy flops around so much, architecture has to as well.
-
-
Replying to @kylemathews
@kylemathews What's a backend example? DevOps test events?2 replies 0 retweets 0 likes -
Replying to @vgr
@vgr stream processing http://blog.confluent.io/2015/01/29/making-sense-of-stream-processing/ … tools like Spark/Samza/etc are the darling of big data crowd now not Hadoop (batch processing)3 replies 1 retweet 1 like -
Replying to @kylemathews
@vgr 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 reply 0 retweets 2 likes -
Replying to @kylemathews
@kylemathews I am already on the stream bandwagon on ux and management/org structure front, now good to see mirroring goes all the way thru1 reply 0 retweets 1 like -
Replying to @kylemathews
@kylemathews It's about managing end-to-end information flows rather than supply/distro chain. The atoms are commodity now.2 replies 0 retweets 1 like -
Replying to @kylemathews
@vgr also that they can be temporary and you can easily create new aggregates on an as-needed basis.1 reply 0 retweets 2 likes -
Replying to @kylemathews
@vgr teams in Slack-orgs seem as if they could work the same way. Teams get aggregated around hot/important data flows.3 replies 0 retweets 1 like
@kylemathews aside. Just remembered you were working on a GTD app when we met. Stream model of orgs = GTD with 10x focus on hard-landscape
-
-
Replying to @kylemathews
@vgr how does product-driven work here then? That's your secret sauce algorithms for processing external stream flows?1 reply 0 retweets 0 likes - 3 more replies
New conversation
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.