As part of Closed Beta testing, we offeredJakarta EEexpert, Java Champion,bloggerand podcaster,Adam Biena trial of our next-generation cloud-native application runtime,  Payara Cloud. 

He went on to discuss Payara Cloud as an alternative to HelidonandQuarkus; a 'serverless server'. He included it in hisMid-Year 2021 Observations and Reflectionsand created a video with hisinitial thoughts. Read our previous blog, rounding up his comments so far,here.

At theJ4Kconference this year, he went into further detail. He told viewers:“I really like the idea [of Payara Cloud]. Why? Because it is the opposite of where everyone is going with smaller and smaller runtimes, you can go that route or another route.” You can now view the video of this talk to watch him demonstrate Payara Cloud live and see how he reached this conclusion.  

Adam Bien is a well-known expert in the world ofJakarta EE. He is a freelancer, author, Java Champion andblogger, providing resources and training materials, and is host of theAirHacks.FM podcast - where he regularly talks to the leading experts in the Java and Jakarta EE community, with recent guests including PayaransLenny PrimakandRudy De Busscher. 

As a long time user of the Payara Platform - regularlyrecommending it as a solution to GlassFish problems - we were keen to offer him a trial ofPayara Cloud, our next generation of cloud-native application runtime. Payara Cloud offers an easier way to run Jakarta EE apps on the cloud, allowing you to simply select your war, click deploy, and watch your apps run - automatically, like magic!

As part of our Payara Cloud Closed Beta testing, we offered him a trial of the software. He created a concise video showing his experience using serverless MicroProfile and Jakarta EE on Payara Cloud. Watch it now to find out what his first thoughts were in his own words.  

There is a lot of interest in the server-side Java community around using ahead of time (AOT) native compilation provided by Graal Substrate VM to drive down memory usage and cold start times of Java microservices. While these frameworks are technically interesting, the claim is if you spend time rewriting your Jakarta EE applications to utilise these new frameworks, then you will substantially reduce your cloud operational costs. First, by enabling the adoption of a serverless deployment model and second by reducing your containers' memory usage. 

What happens when an application designed for a small user base needs to be scaled up and moved to the cloud?

It needs to live in a distributed environment: responding to an appropriate number of concurrent user requests per second and ensuring users find the application reliable. 

Though Jakarta EE and Eclipse MicroProfile can help with reliable clustering, there is no standard API in Jakarta EE that defines how clustering should work currently. This might change in the future, but in the meantime, this gap must be filled by DevOps engineers.

In this blog, we will cover 10 technical strategies to deal with clustering challenges when developing Jakarta EE and MicroProfile for cloud environments.

Microservices architecture allows developers to apply best practices for larger systems learned over time with containerized Jakarta EE (Java EE) application deployments in any environment: on premise, in the cloud, or hybrid.  Using Payara Micro in the cloud offers benefits ranging from reduced expenses, seamless integration with cloud platforms and tools for management and automation, to automatic and elastic clustering. 

All companies are software companies, and businesses will always experience the challenge of keeping integrations between users and applications scalable, productive, fast, and of high quality. To combat this, cloud, microservices, and other modern solutions come up more and more in architectural decisions.

Here is the question: Is Java prepared to deal with these diverse concepts in a corporate environment?

Yes, and to demonstrate how Jakarta EE and Eclipse MicroProfile work very well and in the cloud, the Payara and Platform.sh will work together on this webinar. Watch and make your conclusions.

All companies are software companies, and businesses will always experience the challenge of keeping integrations between users and applications scalable, productive, fast, and of high quality. To combat this, cloud, microservices, and other modern solutions come up more and more in architectural decisions. Here is the question: Is Java prepared to deal with these diverse concepts in a corporate environment?

This blog aims to give you a short overview of Hybrid Cloud, its benefits and limitations, how to tackle these limitations and finally - why the Payara Platform is the right choice if you are thinking about migrating your business to Hybrid Cloud.

An increasing number of organisations have moved, or are planning to move, to cloud-based hosting and are developing their applications to run in the cloud. However, once it's decided that your next application is going to run in the cloud, there are still a lot of architectural choices ahead of you. Besides obvious benefits like cost reduction, scalability and easier administration, cloud environments bring their own disadvantages and potential risks. In this blog, I'll share with you some tips on how to take care of the most important disadvantages and risks when you decide to build your applications for the cloud.

We will look at the various options for running your application:

Whilst cost is an important consideration when choosing a cloud provider, there are other things that you need to take into consideration before making your decision. To help, here are the top 5 tips for choosing the right cloud provider for projects based on Payara Server or Payara Micro and your business needs.