Unix Internal / C / C++ / Multi-Threaded Programming / TCP-IP Protocol 
======================================================================

- What was the architecture, throughput of transactions and technology of the systems you have worked on?
- What was your role and how did you contribute to the design of the system?
- Why did you choose the specific architecture (MQ/Unix Queues/in-memory processing?
- How will you take care of server clustering, load balancing especially when one of the server processes goes down?
- How did you address fault tolerance and increased performance?
- Did you use 'waves' or 'baskets' and what was the algorithm used?
- What design considerations you had to address multi-programmer environment?
- What methodology/strategy you used for locking/unlocking records during in-memory processing?
- How would you debug the multithreaded application, if in production you would have removed any extra code including that for debug? - If one of the instances of a process is deadlocked, how ill you find that
out, how will you debug and what corrective action can be taken?
- Are you familiar with publish-subscribe mechanisms, what design issues you need to consider for such implementation?