Hi Priyanka,

1) We are trying to build a lightstreamer architecture for stock market consumer clients to be able to consume data filtered based on region, country name, strategy & then security names (basically its a drill- down approach filtration) where our consumer client can subscribe to items based on the filtration they subscribe to. So, can a consumer client on lightstreamer be able to consume data filtered on multiple levels so that the data requested is available only to that particular client? If yes, then how?
A possibility is to leverage the getItems method of the MetadataProvider interface, which you can implement to customize the items to subscribe to on the basis of the user who is issuing the request.

2) Where does lightstreamer store the data fed on its server before it is consumed? What is the internal hardware involved? Is there an inbuilt queue of some sort & some offset mechanism involved in lighstreamer where I can start consuming data from a particular offset (only the latest & not the previous messages like in Kafka) ?
To get more in-depth details about Lightstreamer internals, you might want to take a look at Paragraph 3.3.5 of the General Concept document. That said, it is no clear to me what you mean about "internal hardware".
Data are consumed at client side, and the way it is done depends on the kind of subscription model chosen. You can dive into all these details by looking at the Paragraph 3 of the aforementioned document.

Let us know if you need any clarifications on some specific point.
Regards,
Gianluca