Payara Micro vs./or Payara Server Full

An airhacks.fm conversation with Steve Millidge (@l33tj4v4) about:
60-70% growth every year, customer base is growing quickly, 30
employees, great team with great vision, Payara is self-founded by
commercial support fees, there are a lot of "traditional"
applications in production, not every application needs Kubernetes,
Payara clients are running their software on bare metal and on
containerized platforms, it doesn't take much to support
Kubernetes, Docker and Kubernetes are infrastructure and not a
programming model, Java EE programming model is productive and can
be taken to Docker and Kubernetes infrastructure, config
externalization is the major task for Kubernetes support, Payara
clustering discovery service uses Kubernetes for lookup, Payara
Admin server is able to manage Payara Docker nodes, Payara Admin
could replace the Kubernetes scheduler, scalability based on
business metrics, the JavaONE GlassFish 3 cloud demo, aggregating
metrics in a cluster, Payara Clustering brings data closer to
processing, Payara Cluster is a distributed cache aka data grid,
smart proxies with JAX-RS, CORBA was replaced by JAX-RS, load
balancing with JAX-RS, in Payara 5 deployment groups and data grid
comprise a cluster, Payara Server and Payara Micro support both
MicroProfile and Java EE 8, application server as managed runtime,
Payara comes with request tracing, database monitoring, upcoming
releases will expose more metrics. you should not need an APM tool
to monitor an application server, Canadian government contributes
to LightFish, guidance for Maven bloat prevention, Payara Source To
Image (S2I) https://github.com/AdamBien/s2i-payara and Payara Micro
Source To Image (S2I) https://github.com/AdamBien/s2i-payara-micro,
Payara Server supports more APIs than Payara Micro, Payara Server
is capable to manage multiple instances and comes with admin
console, Payara Micro runs on its own and is designed to run within
docker containers, clouds and kubernetes, you could start with
Payara Server and migrate to Payara Micro later, Payara Server and
Payara Micro runtimes are similar, Payara Micro does not support
OSGi - what is a feature, the only runtime difference between
Payara Full and Micro is OSGi, Payara Micro doesn't have to be
installed, the core development happens on Payara Server, Payara
Micro is just repackaging of Payara Server, Payara Micro uses
hardcoded classpath, the javax Jakarta EE namespace issue, Java EE
backward compatibility is great feature and also a weakness,
Jakarta EE is boring, MicroProfile iterates more quickly, Jakarta
EE release cadence could be once every 2 year, MicroProfile
releases 4 times a year, Jakarta EE and MicroProfile are popular in
Europe, managing satellites with GlassFish, kubernetes
anti-pattern, running OpenShfit cluster organization-wide

Steve Millidge on twitter: @l33tj4v4, Steve's company:
https://payara.fish