How does one choose to architect a system that has a Microservice / REST API endpoints?  There are many solutions out there.  Some are better than others.  Should state be held in a server side component?  Generally we are told this is a bad practice, but is it?  It’s unclear and this confusion may lead to poor technology stack choices that are impossible or extremely hard to change later on as your system evolves in terms of demand and performance.

We learn from the experience of others.  Choosing who to follow is hard and this topic will help you the developer or technical decision maker to meet your company’s I.T. demands in the modern world.  We will explore into a tried and true, enterprise-grade, Java Open Source stack - Open Liberty in Kubernetes - which exercises and promises to fulfill the expectations of a modern server solution that epitomizes all the elements needed to build, run and deploy an efficient production system today.

We will examine and demonstrate the fundamentals of such a system that’s built with Open Liberty in Kubernetes:

• Microservices/REST API –  Options to use when running your apps in the JVM
• Concurrency – how to take advantage of multi-core CPUs and clustered distributed systems
• Stateful vs Stateless - while stateless apps are easier to implement, the bulk of the apps in production are stateful which involve a higher level of complexity and risk, especially when data would need to travel across multiple machine and network boundaries
• Deployment – how about containerization and orchestration using Kubernetes?