Sunday, December 7, 2014

How our Lambda Architecture could fail ?

After coming to the meetup event,, it's very informative event and lots of useful information. Then I have some new ideas , that could solve problems I get during development and deployment using Lambda Architecture in 1 year production at FPT Online, where tons of data hit the server and all system have to make decisions, checking, booking, mining , bidding in near-real-time.
If you miss this talk, you can check this link for more details

Some main issues when deploying and implementing the lambda arch in practice:
not Agile enough "The problem with the Lambda Architecture is that maintaining code that needs to produce the same result in two complex distributed systems is exactly as painful as it seems like it would be. I don’t think this problem is fixable."
Refer link

=> Keep it simple as possible, but not simpler

We are in the dawn of "Fast Data"

Using User Tracking with real-time decisions

=> Fast data is really popular in practice, real-time marketing and marketing automation is the new trend 

I made simple diagram here, for easy understanding, combines cool ideas from with Lambda Architecture to create a new system that reacts faster with 2 types of new data:
  • behavioral data
 (game, interests, sessions, touch, ...)

  • context data 
(location, time, referrer, lead ,...)
Apply Marketing Automation with RFX framework