-
Why should you use an Event Driven Architecture (EDA)?
There is a lot of documentation on EDA and people working with SOA and call backs will naturally gravitate to EDA , but i have often wanted a simple reason why. Here i will attempt this and focus on service based EDA's.
1. It Naturally mirrors organisations.
High level EDA events are business events. With EDA anybody may receive these events and act accordingly. This means extending events to new applications is a trivial excercise.
2. Low integration costs
Integration expenses are massive, EDA makes it really easy for systems to communicate even more so than SOA's which require writing a...
-
EDA vs Cloud storage
Cloud storage promises a lot of the things that EDA does namely almost unlimited scaling however EDA implemented in the Cloud has significant advantages.
Firstly while Cloud storage Data may scale extremely well , it does so by using masses amounts of caching or disk spindles. In itself this is not an issue but if you have say 1,000,000 users querying/polling a 10 Gig Table While the performance is likely to be good the CPU usage will be massive and this is where cloud computing bites you - in the pocket. And the situations will get worse as data increases.
However EDA...
-
OSLO to be or not
Based on the limited information so far .
Im not really sure about Oslo ( as opposed to Dublin and Azure which i think will be big hits) it reminds me a LOT of UML and associated higher end tools which manage synch the UML to code and database schemas.
For a start we have to learn a new language ( ok its similar but there are a lot of differences) that immediately has to be a barrier to entry . In return it doesn't make anything easier it just unifies a lot of different thigns under a bigger umbrella...
-
.Net services message persistance
Well looks like .Net services doesn't have persistant messaging ( no queues or persistance of subscriptions ) . This will probably be address in v2 . There is a 30 second message buffer for polling replies but this is not the same.
This is especially an issue for mobile computing ( PDAs , phones etc which are often offline) and for wrapping legacy systems. Though its unlikely that legacy systems will be wrapped by .Net services ( more likely the service bus will redirect it to locally hosted services) .
Im not a big fan of queues however. See post.
-
What is Azure Services ?
Are Azure services a cloud or are they an ESB ?
While Azure does not have this it has FAR more than most ESB in terms of connecting clients to services. Sure it has router support
Azure >> ESB (Internet hosted , with integrated internet security , scalable)
Azure >> Cloud computing ( not just Client - Service routing and hosting but also it has sender-receiver relay , multicast , firewall pass through , and enterprise-cloud security integration)
The big thing is people see it as a cloud .. however i think the biggest thing is it can redirect clients...