This document discusses exactly once semantics in Apache Kafka 0.11. It provides an overview of how Kafka achieved exactly once delivery between producers and consumers. Key points include:
- Kafka 0.11 introduced exactly once semantics with changes to support transactions and deduplication.
- Producers can write in a transactional fashion and receive acknowledgments of committed writes from brokers.
- Brokers store commit markers to track the progress of transactions and ensure no data loss during failures.
- Consumers can read from brokers in a transactional mode and receive data only from committed transactions, guaranteeing no duplication of records.
- This allows reliable message delivery semantics between producers and consumers with Kafka acting as
Event-driven autoscaling through KEDA and Knative Integration | DevNation Tec...Red Hat Developers
?
This talk will teach you how to redesign an event-driven autoscaling architecture for cloud-native microservices by utilizing Apache Kafka, Knative, and KEDA infrastructure. You will also learn how to deploy serverless applications (Quarkus) using a Knative service. Finally, KEDA will enable you to autoscale Knative Eventing components (KafkaSource) through events consumption over standard resources (CPU, memory).
Red Hat OpenShift 4 allows for automated and customized deployments. The Full Stack Automation method fully automates installation and updates of both the OpenShift platform and Red Hat Enterprise Linux CoreOS host operating system. The Pre-existing Infrastructure method allows OpenShift to be deployed on user-managed infrastructure, where the customer provisions resources like load balancers and DNS. Both methods use the openshift-install tool to generate ignition configs and monitor the cluster deployment.
The document provides an introduction to JBoss Application Server, including its history, architecture, components, installation process, directory structure, and how to start and stop the server. It also discusses the JBoss Administration Console and JMX Console for managing and monitoring the application server.
20200422 AWS Black Belt Online Seminar Amazon Elastic Container Service (Amaz...Amazon Web Services Japan
?
This document provides an overview and agenda for an AWS webinar on Amazon Elastic Container Service (ECS). The webinar will cover the basics of ECS, its main components, container execution environments, key ECS features, task definitions, and container execution. It includes introductions to the presenter and notices about pricing and content details. The target audience is those considering using containers in production environments on AWS.
Event-driven autoscaling through KEDA and Knative Integration | DevNation Tec...Red Hat Developers
?
This talk will teach you how to redesign an event-driven autoscaling architecture for cloud-native microservices by utilizing Apache Kafka, Knative, and KEDA infrastructure. You will also learn how to deploy serverless applications (Quarkus) using a Knative service. Finally, KEDA will enable you to autoscale Knative Eventing components (KafkaSource) through events consumption over standard resources (CPU, memory).
Red Hat OpenShift 4 allows for automated and customized deployments. The Full Stack Automation method fully automates installation and updates of both the OpenShift platform and Red Hat Enterprise Linux CoreOS host operating system. The Pre-existing Infrastructure method allows OpenShift to be deployed on user-managed infrastructure, where the customer provisions resources like load balancers and DNS. Both methods use the openshift-install tool to generate ignition configs and monitor the cluster deployment.
The document provides an introduction to JBoss Application Server, including its history, architecture, components, installation process, directory structure, and how to start and stop the server. It also discusses the JBoss Administration Console and JMX Console for managing and monitoring the application server.
20200422 AWS Black Belt Online Seminar Amazon Elastic Container Service (Amaz...Amazon Web Services Japan
?
This document provides an overview and agenda for an AWS webinar on Amazon Elastic Container Service (ECS). The webinar will cover the basics of ECS, its main components, container execution environments, key ECS features, task definitions, and container execution. It includes introductions to the presenter and notices about pricing and content details. The target audience is those considering using containers in production environments on AWS.
1. 1
SoftwareGroup WebSphere
Confidential - Do Not Distribute
2017.
IBM Hybrid Cloud Technical Sales
??? ?? (JungWoon Lee, juwlee@kr.ibm.com)
? Copyright IBM Corporation 2017
Cloud, IBM Korea
IBM JVM ??
6. 6
SoftwareGroup WebSphere
Confidential - Do Not Distribute
IBM SDK for Java
? IBM SDK for Java ? Oracle Platform Java Standard Edition (Java SE) 8 application programming interfaces
(APIs) ??? ???? ?????.
? Generalized Target-Type Inference JEP 101
? Parallel Array Sorting JEP 103
? Annotations on Java Types JEP 104
? DocTree API JEP 105
? ´´
? Enhance the Certificate Revocation-Checking API JEP 124
? Lambda Expressions & Virtual Extension Methods JEP 126
? ´´
? PKCS#11 Crypto Provider for 64-bit Windows JEP 131
? Unicode 6.2 JEP 133
? Base64 Encoding & Decoding JEP 135
? Date & Time API JEP 150
? ´´
? Concurrency Updates JEP 155
? Prepare for Modularization JEP 162
? Leverage CPU Instructions for AES Cryptography JEP 164
? JDBC 4.2 JEP 170
? ´´
7. 7
SoftwareGroup WebSphere
Confidential - Do Not Distribute
Oracle ? IBM Java ? ?? ???
? IBM ? Oracle Java ? ?? Java Class Libraries ? ?? ?? ?? ???? ????? JVM ???? ??
?? ??? ???????.
? IBM and Oracle use the same reference implementation of Java Class Libraries (e.g. OpenJDK)
? Key differences to be aware of:
- Security: Standards do not impose strong separation of interest
- ORB: OMG CORBA standard rules
- XML: Xerces/Xalan used by both vendors as of Java 5, although different levels may be used.
? IBM uses the J9/TR runtime, Oracle uses Hotspot
? Different JIT/GC/VM tuning and controls
? Tooling is distinct (e.g. IBM¨s Health Center)
8. 8
SoftwareGroup WebSphere
Confidential - Do Not Distribute
IBM JVM
? IBM JVM ? J9 ? IBM ?? ???? ?? ???? ???, ????, ?? ??? ??? ???? ???
????.
? IBM¨s strategic virtual machine : J9
? Designed from the ground up by IBM
? Focused on high performance , high reliability and serviceability
? Scales from embedded and handheld devices to large SMPs
? Highly configurable with pluggable interfaces for alternative implementations of GC, JIT
? Composed of several key components
? Reconfigurable, portable virtual machine framework and interpreter called ^J9 ̄
? Type accurate garbage collection frameworks (Modron, Tarok, Metronome)
? Highly optimizing just-in-time (JIT) compiler ^Testarossa ̄
? Integrated RAS features to enhance problem determination
? Unique Features - SharedClasses, Dynamic AOT
9. 9
SoftwareGroup WebSphere
Confidential - Do Not Distribute
Java Adaptive Compilation : trade off effort and benefit
? IBM JVM ? ??? ??? ??? just-in-time (JIT) compiler ? ??? runtime profiling ????
bytecode ? ?? ???? ?????.
? Java's bytecodes are compiled as required, optimized based on runtime profiling
? Dynamic compilation determines the target machine capabilities and app demands
? Multiple phases, enable adaptive response to changing environment
cold
hot
scorching
profiling
interpreter
warm
? Methods start out running bytecode form directly
? After many invocations (or via sampling) code get compiled at `
cold¨ or `warm¨ level
? Low overhead sampling thread is used to identify hot methods
? Methods may get recompiled at `hot¨ or `scorching¨ levels (for m
ore optimizations)
? Transition to `scorching¨ goes through a temporary profiling step
Results can be stored for future runs and shared across invocations
10. 10
SoftwareGroup WebSphere
Confidential - Do Not Distribute
Shared Classes Cache
? IBM JVM ? Shared Classes Cache ? ???? ??? ?? ??? ????? ??? ?? ? ??? ??
?? ????.
? IBM JVMs use sharing to reduce memory and startup costs
? Ability to securely common Java class code across multiple JVM instances
? Reduces footprint due to sharing of read-only components (Java code)
? Reduces startup time by caching ^ready to run ̄ previously JITed code (Dynamic AOT)
? Dynamic AOT - reuse JIT code from multiple JVMs
? Reduce memory use by 20%, improve startup time 10-30 %
JVM
JVM
JVM
JVM
JVM
Shared Classes Cache
JVM
JVM
JVM
JVM
JVM
JVM
JVM
JVM
JVM
JVM
AOT C Ahead Of Time
(JIT code saved for next JVM)
Verified bytecodes
JVM shared index
^Compile once,
run manywhere ̄