Skip to content

DOC-470: migrate C++ client content #1725

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 7 commits into
base: main
Choose a base branch
from
Open

Conversation

amandalindsay
Copy link
Contributor

@amandalindsay amandalindsay commented Jun 6, 2025

Migrate C++ client content into Docs site
(this is to add the introductory, install and getting started content from the GH repo into the docs site)
WIP

Copy link

netlify bot commented Jun 6, 2025

Deploy Preview for hardcore-allen-f5257d ready!

Name Link
🔨 Latest commit 1836077
🔍 Latest deploy log https://app.netlify.com/projects/hardcore-allen-f5257d/deploys/6842bc0673addc0008c3231d
😎 Deploy Preview https://deploy-preview-1725--hardcore-allen-f5257d.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@oliverhowell oliverhowell changed the title Doc 470 part 1 DOC-470: migrate C++ client content Jun 6, 2025
@ihsandemir
Copy link
Contributor

Is there a way to automate this page generation from the markdown file at the repository to avoid duplications?

@oliverhowell oliverhowell requested a review from ihsandemir June 12, 2025 12:32
@oliverhowell oliverhowell marked this pull request as ready for review June 12, 2025 12:32
@oliverhowell oliverhowell requested a review from a team as a code owner June 12, 2025 12:32
@oliverhowell
Copy link
Contributor

Is there a way to automate this page generation from the markdown file at the repository to avoid duplications?

Building on the slack conversations, this isn't in scope for this release but we can look at this in another sprint to automate and single source the shared content.


The Hazelcast native {cpp} client is an official library that allows {cpp} applications to connect to and interact with Hazelcast clusters. The key features and benefits include:
The Hazelcast native {cpp} client is an official library that allows {cpp} applications to connect to and interact with Hazelcast clusters. With the Hazelcast {cpp} client, developers can build high-performance, distributed applications in {cpp} that leverage Hazelcast's powerful in-memory computing platform.
The key features and benefits include:

* Distributed Data Structures: the client offers access to various distributed data structures such as Map, Queue, Set, List, MultiMap, and RingBuffer. It also gives access to transactional distributed data structures such as transactional_map, transactional_queue, etc.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Distributed Data Structures: the client offers access to various distributed data structures such as Map, Queue, Set, List, MultiMap, and RingBuffer. It also gives access to transactional distributed data structures such as transactional_map, transactional_queue, etc.
* Distributed Data Structures: the client offers access to various distributed data structures such as Map, Queue, Reliable Topic, Set, List, MultiMap, RingBuffer, etc.

* Near Cache Support: the Near Cache feature allows frequently read data to be stored for faster read speeds compared to traditional caches.
* Enterprise-Level security: the client provides SSL support for enhanced security requirements.
* Distributed synchronization: the client offers distributed synchronization mechanisms through the CP Subsystem, including fenced_lock, counting_semaphore and latch.
* Smart Client functionality: by default, it operates as a smart client, meaning it knows the data location within the cluster and can directly request the correct member (note that you can disable this feature using the `client_config::set_smart_routing` method if you do not want the clients to connect to every member).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Smart Client functionality: by default, it operates as a smart client, meaning it knows the data location within the cluster and can directly request the correct member (note that you can disable this feature using the `client_config::set_smart_routing` method if you do not want the clients to connect to every member).
* Smart Client functionality: by default, it operates as a smart client, meaning it knows the data location within the cluster and can directly request the correct member (note that you can disable this feature using the `client_config::get_networking_config::set_smart_routing` method if you do not want the clients to connect to every member).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants