Join us for an insightful webinar with Lenny Primak & Luqman Saeed, where we'll demystify security for your Jakarta EE applications using Apache Shiro.

Simplifying Security for Your Jakarta EE Applications with Apache Shiro

Wednesday, the the 4th of September, 4pm BST

Register: https://www.crowdcast.io/c/security-with-jakarta-and-apache-shiro

In the latest episode of the Payara Podcast, we talk to Lenny Primak. Lenny is an experienced software architect and developer - he’s been contributing to various open source projects for many years, including Apache, Jakarta EE and Payara.

Last month, in June 2024 we held the Virtual Payara Conference, and that’s where Lenny joined us for the Open Source contributors roundtable. We had a really interesting conversation then, but had limited time to discuss various aspects of his work on open source, so we thought it’d be best to give Lenny some more time to share his journey and his experience during the Payara Podcast so here we are - we hope you will enjoy listening to this episode !

When dealing with complex distributed systems, decoupled, asynchronous communications may be more suited to support the exchange of information between different parts of a system, or even completely different systems. In effect, this decoupling makes it possible for different parts of a system to interact without being directly connected, enhancing scalability and fault tolerance. It is possible to set up such communications through a messaging platform like Apache Kafka and design highly scalable applications.

Our new eBook - available to download here - discusses how to use Apache Kafka for Jakarta EE Platforms that use Payara Server. 

This article provides a brief introduction to using Instaclustr’s managed PostgreSQL Database and Apache Kafka from Payara Cloud. It was created to assist entrants in the upcomingPayara Hackathon (you can still sign up!) spin-up and configure some potentially useful Instaclustr technologies forJakarta EEapplications.

Avanzando más nuestra serie de blogs de introducción, esta entrada mostrará como puedes escalar de forma dinámica tu cluster, y como Payara Server maneja la conmutación por fallas entre miembros del cluster.

See here for the original version in English language.

La conmutación por fallas es la habilidad de continuar proporcionando acceso a nuestro sitio web o aplicación en el caso de que un servidor falle. Es una parte importante de un servicio que goza de alta disponibilidad, cuyo objetivo es minimizar los tiempos de inactividad a lo largo de tu infraestructura de servicios.

In a previous blog of this series we set up Apache httpd to forward traffic to Payara Server. However, this only covers forwarding HTTP and not HTTPS. This blog will demonstrate how to secure Payara Server with Apache over HTTPS on Ubuntu.

Taking our introductory series onwards, this blog will look at how you set up a simple Payara Server cluster on Windows using the native remote control protocol, DCOM. We will set up two instances on Windows 10, controlled by a third Domain Administration Server (DAS) instance on Windows 7 via DCOM, and cluster them together using Hazelcast. Finally, we will deploy our trusty clusterjsp application to demonstrate how the data is being shared across our instances.

Further developing our introductory blog series, this post will look at how you can dynamically scale your cluster, and how Payara Server handles failover between cluster members.

Failover is the ability to continue to provide access to your website or application in the event of a server failing. It is an important part of high availability hosting, which aims to minimise downtime across your server infrastructure.

This article continues our introductory blog series on setting up a simple cluster with Payara Server, carrying straight on from our last blog where we set up load balancer on our cluster.

By clustering our Payara Servers together and balancing traffic between them with Apache Web Server we keep the benefits of having our application accessible from a single URL and gain the resilience and expansion prospects from having our application deployed across multiple instances.

Este artículo continúa nuestra serie de blogs de introducción para configurar un cluster con Payara Server, continuando desde nuestro último articulo donde configuramos un balanceador de carga para nuestro cluster.