<commit_before>
### Enhancements

This section lists the enhancements performed for Hazelcast 3.5 release.

- **Eventing System Improvements**: RingBuffer and Reliable Topic structures are introduced.
- **XA Transactions Improvements**: With this improvement, you can now obtain a Hazelcast XA Resource instance through `HazelcastInstance`. For more information, please see [XA Transactions](#xa-transactions).
- **Query and Indexing Improvements** 

The following are the other improvements performed to solve the enhancement issues opened by the Hazelcast customers/team.
 
- While configuring JCache, duration of the `ExpiryPolicy` can be set programmatically but not declaratively [[#5347]](https://github.com/hazelcast/hazelcast/issues/5347).
- Since near cache is not supported as embedded but only at client, at the moment, there is no need for `NearCacheConfig` in `CacheConfig` [[#5215]](https://github.com/hazelcast/hazelcast/issues/5215).<commit_msg>New Query Evaluation Strategy described in release notes.<commit_after>
### Enhancements

This section lists the enhancements performed for Hazelcast 3.5 release.

- **Eventing System Improvements**: RingBuffer and Reliable Topic structures are introduced.
- **XA Transactions Improvements**: With this improvement, you can now obtain a Hazelcast XA Resource instance through `HazelcastInstance`. For more information, please see [XA Transactions](#xa-transactions).
- **Query**: Predicates are now evaluated using a single thread to prevent a parallel slowdown. This has been proven to be beneficent for most of use-cases. You can revert to the old behaviour by setting a System Property `hazelcast.query.predicate.parallel.evaluation` to `true`.

The following are the other improvements performed to solve the enhancement issues opened by the Hazelcast customers/team.
 
- While configuring JCache, duration of the `ExpiryPolicy` can be set programmatically but not declaratively [[#5347]](https://github.com/hazelcast/hazelcast/issues/5347).
- Since near cache is not supported as embedded but only at client, at the moment, there is no need for `NearCacheConfig` in `CacheConfig` [[#5215]](https://github.com/hazelcast/hazelcast/issues/5215).
{'fraction_non_alphanumeric': 0.08152173913043478, 'fraction_numerical': 0.016304347826086956, 'mean_word_length': 5.421511627906977, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2269218', 'n_tokens_mistral': 608, 'n_tokens_neox': 564, 'n_words': 254}