On 8/25/23 12:16, Neeraj giri wrote:
Our team is currently working with Solr 8.11 in cloud mode to power our search system, built using Java Spring at the application layer. We're facing a challenge in maintaining up-to-date pricing information for our ecommerce platform, which experiences frequent data changes throughout the day. While attempting to achieve real-time data updates, we've encountered issues related to Solr's latency and overall system performance.
What are the issues? Be as detailed as you can be, include complete error messages. Which exact Solr 8.11 version are you running? There are three released versions that start with 8.11.
As of now, we've implemented a process that halts data writes during the day. Instead, we retrieve updated pricing data from a separate microservice that maintains a cached and current version of the information. However, we believe this approach isn't ideal due to its potential impact on system efficiency.
There's not much information here about what your microservice actually does or what problems you have had with it.
We're seeking guidance on designing an architecture that can seamlessly handle real-time updates to our Solr index without compromising the search latency that our users expect. Writing directly to Solr nodes appears to increase read latency, which is a concern for us. Our goal is to strike a balance between keeping our pricing information up-to-date and maintaining an acceptable level of system responsiveness.
What exactly does "writing directly to Solr nodes" mean, and what is the alternative?
Your message includes very few details. The details are needed to provide a solution.
Thanks, Shawn
