3 ➔ Traditional long-running application architecture and its drawbacks. ➔ OpenShift Serverless Serving and creating functions. ➔ OpenShift Serverless Eventing and how it solves problems by: ◆ Reducing the coupling between services. ◆ Providing autoscale and scale-to-zero capabilities to the applications. ➔ Building blocks for eventing like source, channel, subscription, sink, and more. ➔ CloudEvents usage in an OpenShift Serverless Eventing architecture.
clans do bitmining in a daily basis. ➔ Sometimes no bitmining is done. ◆ No economical bitmining architecture ◆ Resources are used for nothing ➔ Code bases of miner apps are too complex. ◆ There are more than one technology as there are more than one clan. ◆ Harder development life-cycle. ➔ In case of failures in the miner clans, there is no retry mechanism. All processes are synchronous. ➔ Quakers miner clan face a lot of issues like these recently.
and run serverless containers ➔ Use any programming language or runtime ➔ Modernize existing applications to run serverless ➔ Powered by a rich ecosystem of event sources ➔ Manage serverless apps natively in Kubernetes ➔ Based on open source project Knative ➔ Run anywhere OpenShift runs OPENSHIFT OpenShift Serverless SERVING EVENTING Red Hat Enterprise Linux CoreOS Physical Virtual Private cloud Public cloud Applications Events F
that serves the container with your application and can "scale to zero". Common infrastructure for consuming and producing events that will stimulate applications. EVENTING ➔ Autoscaling with scale-to-zero ➔ Advanced networking ➔ Immutable revisions ➔ Traffic splitting ➔ Knative Service ➔ Functions ➔ Serverless workloads with event-driven architecture ➔ Source ◆ Kafka Source ➔ Channel ◆ Kafka Channel ➔ Subscription ➔ Broker ➔ Trigger