pablocastilla / nsb-structuremap-nhibernate Goto Github PK

Hi Pablo,

First, I want to say thanks for all your effort.

This issue is not related to this repository only.

I'm planning the create architecture of my next Web Application Framework, there is the single server for now, but I want to make my plan for 100 million daily visits, so It must be ready for it :)

Details of framework:

UI side is a little confused because there are so many options to consider. (AngularJs, ReactJs for client, NodeJs+Express or Async WebApi for server) Only thing that I know I will use VS2015 for this project:)
But for know I will start with VS2013.

I will use RabbitMq+MassTransit on the middleware.

Redis for Analytics, GraphDb as graph queries, and ElasticSearch for search. All of them must be synchronized. Not real time. Lazily. I guess all databases will consume same "Queue", but they will update themselves asynchronously. Maybe RedisConsumer could consume 100 messages from the queue, ElasticConsumer could consume 5 messages at the same time. But the end of the day all DBS are synchronized.

• Is RabbitMq (enterprise service bus) the best practice for it?
• How Cache mechanism will interact with this framework?
• Is this architecture ok? What do you think?
• Are Facebook, Amazon like huge traffic sites using ESB? In-house? What do you think about that?

I could not find a better place to write these :)

I'm waiting your response impatiently.

Note: SignalR is used to push messages to UI.