<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Jelastic on foojay.io - Friends of OpenJDK</title><link>https://foojayio.github.io/website/today/category/jelastic/</link><description>Recent content in Jelastic on foojay.io - Friends of OpenJDK</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 28 Aug 2023 12:47:43 +0000</lastBuildDate><atom:link href="https://foojayio.github.io/website/today/category/jelastic/index.xml" rel="self" type="application/rss+xml"/><item><title>GlassFish &amp; Payara Auto-Clustering for Jakarta EE Applications</title><link>https://foojayio.github.io/website/today/glassfish-payara-auto-clustering-jakarta-ee/</link><pubDate>Wed, 13 Oct 2021 13:27:30 +0000</pubDate><guid>https://foojayio.github.io/website/today/glassfish-payara-auto-clustering-jakarta-ee/</guid><description>&lt;figure class="alignleft is-resized"&gt;
 &lt;img fetchpriority="high" decoding="async" src="https://jelastic.com/blog/wp-content/uploads/2021/09/GlassFish-and-Payara-clustering.png" alt="" class="wp-image-55851" width="400" height="216"&gt;
&lt;/figure&gt;
&lt;p&gt;Ensuring trouble-proof 24/7 service delivery is among one of the most discussed areas in cloud hosting for the last few years. And the very obvious and commonly used solution here is building a clustered infrastructure for your project.&lt;/p&gt;
&lt;p&gt;Intending to help our customers to deal with such a non-trivial task and save time for other project-related activities, we created a special high-availability solution, designed to facilitate the Jakarta EE application hosting &amp;ndash; embedded &lt;strong&gt;Auto-Clustering for GlassFish and Payara&lt;/strong&gt; application servers.&lt;/p&gt;</description></item><item><title>Thorntail Fat, Thin and Skinny Approach for Java Microservices</title><link>https://foojayio.github.io/website/today/thorntail-fat-thin-skinny-java-microservices/</link><pubDate>Wed, 22 Sep 2021 16:25:45 +0000</pubDate><guid>https://foojayio.github.io/website/today/thorntail-fat-thin-skinny-java-microservices/</guid><description>&lt;p&gt;&lt;a href="https://thorntail.io/" target="_blank" rel="noopener noreferrer"&gt;Thorntail&lt;/a&gt;
, originally &lt;a href="https://wildfly-swarm.io/" target="_blank" rel="noopener noreferrer"&gt;WildFly Swarm&lt;/a&gt;
, is most suitable for packaging applications as &lt;em&gt;JAR&lt;/em&gt; , &lt;em&gt;WAR,&lt;/em&gt; or &lt;em&gt;EAR&lt;/em&gt; files. The most important value is in the functional agility the Thorntail provides. You can start with the stripped down version of Thorntail, adding the required parts and application code on top.&lt;/p&gt;
&lt;figure class="aligncenter is-resized"&gt;
 &lt;img fetchpriority="high" decoding="async" src="https://jelastic.com/blog/wp-content/uploads/2018/09/jvm-microservice.png" alt="microservices" class="wp-image-30149" width="329" height="411"&gt;
&lt;/figure&gt;
&lt;p&gt;Below we will describe how to build and deploy Thorntail based applications using Fat, Thin and Skinny approaches. The application will be packaged in the Jar/War format automatically with the help of &lt;a href="https://github.com/jelastic-jps/thorntail" target="_blank" rel="noopener noreferrer"&gt;Builder add-ons&lt;/a&gt;
 prepared by Jelastic. The topology will consist of Maven build node and JVM containers for running microservices.&lt;/p&gt;</description></item><item><title>Tomcat and TomEE Clustering Automation in the Cloud</title><link>https://foojayio.github.io/website/today/tomcat-tomee-clustering-automation/</link><pubDate>Mon, 30 Aug 2021 07:18:36 +0000</pubDate><guid>https://foojayio.github.io/website/today/tomcat-tomee-clustering-automation/</guid><description>&lt;figure class="alignleft"&gt;
 &lt;img decoding="async" src="https://jelastic.com/blog/wp-content/uploads/2021/08/image11.png" alt="Tomcat TomEE Automatic Clustering"&gt;
&lt;/figure&gt;
&lt;p&gt;Apache &lt;a href="https://tomcat.apache.org/" target="_blank" rel="noopener noreferrer"&gt;Tomcat&lt;/a&gt;
 is an open-source application server maintained by the Apache community. It is one of the most popular solutions for hosting Java applications due to its ease-of-use and lightweight yet versatile functionality. However, if you run the projects based on &lt;a href="https://jakarta.ee/" target="_blank" rel="noopener noreferrer"&gt;Jakarta EE&lt;/a&gt;
 8 (or higher), you may be interested to use &lt;a href="https://tomee.apache.org/" target="_blank" rel="noopener noreferrer"&gt;TomEE&lt;/a&gt;
 server with built-in required enterprise technology that isn&amp;rsquo;t found in Tomcat.&lt;/p&gt;
&lt;p&gt;Due to the extreme popularity of these stacks globally, and within Jelastic PaaS in particular, we&amp;rsquo;ve decided to share tips on how to install automatically clustered Tomcat and TomEE servers to get a highly available solution that can efficiently serve a large number of users, process high traffic, and be reliable.&lt;/p&gt;</description></item><item><title>Jakarta EE Application Deployment to Kubernetes Cluster in Jelastic PaaS</title><link>https://foojayio.github.io/website/today/jakarta-ee-application-deployment-kubernetes-cluster-jelastic-paas/</link><pubDate>Wed, 16 Jun 2021 06:58:31 +0000</pubDate><guid>https://foojayio.github.io/website/today/jakarta-ee-application-deployment-kubernetes-cluster-jelastic-paas/</guid><description>&lt;p&gt;Recently, we were asked to sponsor cloud hosting of a Jakarta EE project, called &lt;a href="https://cargo-tracker.j.scaleforce.net/" target="_blank" rel="noopener noreferrer"&gt;Cargo Tracker&lt;/a&gt;
. Being a member of Jakarta EE Working Group, Jelastic wanted to support the community and thus we started to run this application at one of our service providers (&lt;a href="https://jelastic.cloud/details/scaleforce/" target="_blank" rel="noopener noreferrer"&gt;Scaleforce&lt;/a&gt;
).&lt;/p&gt;
&lt;figure class="wp-block-embed is-type-rich is-provider-twitter wp-block-embed-twitter"&gt;
 &lt;div class="wp-block-embed__wrapper"&gt;
 &lt;blockquote class="twitter-tweet" data-width="500" data-dnt="true"&gt;
 &lt;p lang="en" dir="ltr"&gt;Cargo Tracker is now deployed to Kubernetes on the cloud using GitHub Actions. Thanks sponsors Jelastic and Scaleforce! &lt;a target="_blank" href="https://t.co/zhnmj0TB7Z"&gt;https://t.co/zhnmj0TB7Z&lt;/a&gt; // &lt;a target="_blank" href="https://twitter.com/Jelastic?ref_src=twsrc%5Etfw"&gt;@Jelastic&lt;/a&gt;, &lt;a target="_blank" href="https://twitter.com/scaleforce?ref_src=twsrc%5Etfw"&gt;@scaleforce&lt;/a&gt; &lt;a target="_blank" href="https://t.co/BRGkwxban2"&gt;pic.twitter.com/BRGkwxban2&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Automatic WildFly Managed Domain Clustering &amp; Scaling in Containers</title><link>https://foojayio.github.io/website/today/automatic-wildfly-clustering-managed-domain-scaling-containers/</link><pubDate>Mon, 31 May 2021 08:08:12 +0000</pubDate><guid>https://foojayio.github.io/website/today/automatic-wildfly-clustering-managed-domain-scaling-containers/</guid><description>&lt;p&gt;Nowadays it&amp;rsquo;s easy to get up and running WildFly standalone server in a container. But what if you need to enable clustering in Managed Domain mode, which is one of the key features of &lt;a href="https://jakarta.ee/" target="_blank" rel="noopener noreferrer"&gt;Jakarta EE&lt;/a&gt;
 in general? That is a not so easy task. Some people claim it&amp;rsquo;s nearly impossible in the cloud-native world, because Jakarta EE clustering was designed before the containers era. The old question at the official &lt;a href="https://developer.jboss.org/thread/249340" target="_blank" rel="noopener noreferrer"&gt;developers portal&lt;/a&gt;
 is still not answered with any adequate instructions, just proving the presence of the issue.&lt;/p&gt;</description></item><item><title>Elastic JVM: Configuring G1 GC for Automatic Vertical Memory Scaling</title><link>https://foojayio.github.io/website/today/elastic-jvm-configuring-g1-for-automatic-vertical-memory-scaling/</link><pubDate>Wed, 05 May 2021 13:45:22 +0000</pubDate><guid>https://foojayio.github.io/website/today/elastic-jvm-configuring-g1-for-automatic-vertical-memory-scaling/</guid><description>&lt;figure class="alignleft"&gt;
 &lt;img decoding="async" src="https://jelastic.com/blog/wp-content/uploads/2018/12/elastic-jvm-e1545213859238.png" alt="Automatic Vertical Memory Scaling" class="wp-image-31447"&gt;
&lt;/figure&gt;
&lt;p&gt;Nowadays, JVM-based applications can benefit from elasticity and density of container technology. However, there are still some issues that may prevent from unleashing the full potential of Java and containers &amp;ldquo;marriage.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;Releasing unused but committed Heap memory by the major JVM implementations based on OpenJDK, in most cases, is not performed automatically, or requires specific knowledge to be configured.&lt;/p&gt;
&lt;p&gt;To solve this problem and make &lt;a href="https://jelastic.com/blog/java-ram-usage-in-containers-top-5-tips-not-to-lose-your-memory/" target="_blank" rel="noopener noreferrer"&gt;Java RAM usage in containers&lt;/a&gt;
 more efficient, the Jelastic team collaborated with different experts involved in JVM development. We have periodically published articles highlighting this issue and motivating the community to help in finding a solution. As a result, attention to this topic has increased, and new improvements were introduced in different Garbage Collection implementations in order to make automatic vertical memory scaling possible.&lt;/p&gt;</description></item><item><title>Java Garbage Collection Types &amp; Settings Customization via Jelastic PaaS</title><link>https://foojayio.github.io/website/today/java-garbage-collection-types-and-settings-customization-via-jelastic-paas/</link><pubDate>Thu, 29 Apr 2021 07:54:20 +0000</pubDate><guid>https://foojayio.github.io/website/today/java-garbage-collection-types-and-settings-customization-via-jelastic-paas/</guid><description>&lt;figure class="alignleft is-resized"&gt;
 &lt;img decoding="async" src="https://jelastic.com/blog/wp-content/uploads/2019/08/java-gc.png" alt="java gc" class="wp-image-34173" width="250"&gt;
&lt;/figure&gt;
&lt;p&gt;Performance and price are two big considerations in application hosting that always matter. And, often, we question ourselves on how to decrease the spends, without affecting the performance of your apps at the same time. In this article, we&amp;rsquo;d like to address automatic memory management for Java applications hosted with Jelastic using garbage collection.&lt;/p&gt;
&lt;p&gt;Let&amp;rsquo;s clarify what garbage collection is, what it does for Java applications and how it works within Jelastic PaaS.&lt;/p&gt;</description></item><item><title>Building Microservices with Spring Boot Fat (Uber) Jar</title><link>https://foojayio.github.io/website/today/building-microservices-spring-boot-fat-uber-jar/</link><pubDate>Wed, 21 Apr 2021 09:28:43 +0000</pubDate><guid>https://foojayio.github.io/website/today/building-microservices-spring-boot-fat-uber-jar/</guid><description>&lt;p&gt;In most minds,&lt;em&gt;microservices&lt;/em&gt; is an approach to make a traditional monolithic system more structured, dividing it into logical components that correspond to different functional areas of application. Thus, acting as a microservice, each component becomes self-contained, easily scaled, maintained and even upgraded without affecting the overall system. Also, with &lt;em&gt;microservice&lt;/em&gt; architecture, you can use a software written in different programming languages, including Java. Such freedom attracts but may frighten at the same time.&lt;/p&gt;</description></item><item><title>Jenkins Cluster for Continuous Integration and Delivery in Jelastic PaaS</title><link>https://foojayio.github.io/website/today/jenkins-cluster-continuous-integration-delivery-in-jelastic-paas/</link><pubDate>Mon, 12 Apr 2021 12:44:50 +0000</pubDate><guid>https://foojayio.github.io/website/today/jenkins-cluster-continuous-integration-delivery-in-jelastic-paas/</guid><description>&lt;p&gt;Jenkins is an open-source continuous integration and delivery system designed to ensure build and deploy automation. It is well-suited to be installed in the cloud to run self-hosted pipelines.&lt;/p&gt;
&lt;p&gt;Jenkins supports clustering via master-slave mode. A build process can be delegated to several slave (worker) nodes. This allows serving multiple projects in a single Jenkins cluster setup.&lt;/p&gt;
&lt;p&gt;In this article, we&amp;rsquo;ll describe how to install Jenkins cluster with slave nodes auto-discovering and self-registering inside a master node. Jelastic PaaS implemented this solution in &lt;strong&gt;Jenkins DevOps Pack&lt;/strong&gt; that can be installed from the &lt;a href="https://docs.jelastic.com/marketplace/" target="_blank" rel="noopener noreferrer"&gt;Marketplace&lt;/a&gt;
 or through environment setup wizard as a &lt;strong&gt;New Environment&lt;/strong&gt;. In this tutorial we&amp;rsquo;ll cover both. Also, you will find out how to build a simple Java project hosted on GitHub using Jelastic Maven plugin.&lt;/p&gt;</description></item></channel></rss>