New Architecture and Models
We design new models, adapted to nomadic users, enabling the design of suitable architecture for personal and home usages, users’ access from public facilities (“Hot spots”), workers at the office and on the move, mobile sub-networks, onboard of car, train, and aircraft and e-government. Those models are designed to address three usages, with different priorities:
- For personal usage, the priority concerns are ease of use and privacy protection,
- For business usage, the heterogeneity and mobility are the major issues with a priority and accessibility,
- For public services and e-government, the priority is the survivability of the infrastructure, and then integrated in a transversal trust and security model.
SEINIT delivers specification documents of the security framework with, in regard the threat and vulnerabilities addressed.
Popularity: 14% [?]
I agree that it’s silly to use a complex caching architecture when the main concern is i/o and everything can be fit into an in-memory index / database. My concern here is that some of LinkedIn’s queries sounds CPU-intensive, or at least require lots of random access. I have over 400k degree-two connections, and I’m sure lots of people have more. Sounds like something you don’t want to recompute on every query–but you do have to keep it somewhat up to date as the network changes.
Leave your response!