I have an HTTP web server that runs on the Digital Ocean Apps platform. I was wondering if they support Hazelcast. However, I don’t know if network discovery will work properly on the apps platform.
I don’t want to enable Hazelcast TCP discovery if machines outside of the apps platform can join the Hazelcast cluster. I only want machines within the App platform to join the cluster.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Sign up for Infrastructure as a Newsletter.
Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Hello,
I believe that going with a Droplet may provide a more suitable environment compared to the App Platform.
Droplets offer a higher degree of control and flexibility. This is particularly beneficial for Hazelcast deployments, as it allows for precise configuration of network settings and performance parameters. In environments where specific customizations are necessary, Droplets provide the necessary infrastructure freedom.
Regarding the Digital Ocean App Platform, it does not inherently support Java as a buildpack, which is a critical consideration given that Hazelcast is Java-based. This constraint could significantly impact the deployment process and overall functionality.
However, if you still want to give the App Platform a try, you could use a Dockerfile or a Docker image. By containerizing your Hazelcast application with Docker, you can encapsulate the Java environment within the container.
Hope that this helps.
Best,
Bobby