This document discusses achieving horizontal scaling for enterprise messaging using Fabric8. It provides an introduction to Fabric8 and enterprise messaging concepts. It then describes how Fabric8MQ, which is built on Vert.x, provides horizontal scaling and load balancing for ActiveMQ by implementing features like protocol conversion, Camel routing, API management, multiplexing, and destination sharding across Kubernetes pods and nodes. The document concludes with a demo of Fabric8MQ's capabilities.
Data Models and Consumer Idioms Using Apache Kafka for Continuous Data Stream...
The document discusses Urban Airship's use of Apache Kafka for processing continuous data streams. It describes how Urban Airship uses Kafka for analytics, operational data, and presence data. Producers write device data to Kafka topics, and consumers create indexes from the data in databases like HBase and write to operational data warehouses. The document also covers Kafka concepts, best use cases, limitations, and examples of data structures for storing device metadata in Kafka streams.
This presentation from the I Love APIs conference makes the case for why Node and Docker are great together for implementing Microservice architecture. It also provides an quick orientation for getting started with Docker Machine, Node, and Mongo with container linking and data volume containers.
My talk at ScaleConf 2017 in Cape Town on some tips and tactics for scaling WordPress, with reference to WordPress.com and the container-based VIP Go platform.
Video of my talk is here: https://www.youtube.com/watch?v=cs0DcY80spw
Protecting your data at rest with Apache Kafka by Confluent and Vormetric
This document discusses securing Apache Kafka deployments with Vormetric and Confluent Platform. It begins with an introduction to Apache Kafka and Confluent Platform. It then provides an overview of Vormetric's policy-driven security solution and how it can be used to encrypt Kafka data at rest. The document outlines the typical Confluent Platform deployment architecture and various security considerations, such as authentication, authorization, and data encryption. Finally, it provides steps for implementing secure deployments using SSL, Kerberos, and Vormetric encryption policies.
Nodeconf Barcelona 2015 presentation exploring several ways of building microservices in an asynchronous way. Presented the concept of a broker as an alternative to a multiple point-to-point architecture.
Moving Gigantic Files Into and Out of the Alfresco Repository
This talk is a technical case study showing show Metaversant solved a problem for one of their clients, Noble Research Institute. Researchers at Noble deal with very large files which are often difficult to move into and out of the Alfresco repository.
Reducing Microservice Complexity with Kafka and Reactive Streams
My talk from ScalaDays 2016 in New York on May 11, 2016:
Transitioning from a monolithic application to a set of microservices can help increase performance and scalability, but it can also drastically increase complexity. Layers of inter-service network calls for add latency and an increasing risk of failure where previously only local function calls existed. In this talk, I'll speak about how to tame this complexity using Apache Kafka and Reactive Streams to:
- Extract non-critical processing from the critical path of your application to reduce request latency
- Provide back-pressure to handle both slow and fast producers/consumers
- Maintain high availability, high performance, and reliable messaging
- Evolve message payloads while maintaining backwards and forwards compatibility.
Kafka's basic terminologies, its architecture, its protocol and how it works.
Kafka at scale, its caveats, guarantees and use cases offered by it.
How we use it @ZaprMediaLabs.
This document provides an introduction and overview of RESTful web services. It discusses REST principles such as resources, addressability, statelessness, uniform interface, and representations. It also covers designing RESTful APIs, including examples from Amazon S3. The document outlines an agenda to discuss introduction, principles, design, implementations, and implementation of RESTful APIs and web services.
Load Balancing for Containers and Cloud Native Architecture
This document discusses how load balancing needs have changed with the rise of containers and microservices. Traditional load balancers are not well-suited for dynamic container environments where services and topology frequently change. New approaches are needed like integrating load balancers with container orchestration platforms, using client-side load balancing, and leveraging load balancers for advanced patterns like zero-downtime deployments, circuit breaking, visibility and security segmentation. Load balancers are playing an increasingly important role in cloud native architectures.
The document discusses the REST (REpresentational State Transfer) architectural style and how it differs from traditional SOA (Service Oriented Architecture). It outlines the key principles of REST including addressing resources with URIs, using a uniform interface (HTTP methods), stateless communication, and hypermedia as the driver of application state. The document explains how the web exemplifies REST through the use of URLs, HTTP, and standard formats to access and transfer representations of resources.
This document discusses using Apache Kafka to build a message bus for aggregating activity information from various services and enabling communication between services. It outlines the challenges of needing a way to aggregate activity data and needing a messaging backbone. It then explains how Apache Kafka provides a scalable, durable, distributed solution as a publish-subscribe messaging system to address these needs. Key features of Kafka like speed, scalability, durability and distributed design are highlighted. An example setup and usage with Ruby is also briefly described.
This document discusses security features in Apache Kafka including SSL, SASL authentication using Kerberos or plaintext, and authorization controls. It provides an overview of how SSL and SASL authentication work in Kafka as well as how the Kafka authorizer controls access at a fine-grained level through ACLs defined on topics, operations, users and hosts. It also briefly mentions securing Zookeeper which stores Kafka metadata and ACLs.
Want to get your hands dirty and play around with the Middleware that is going to amaze you with the rich components provided within and made integration much easier pattern base framework. Stop reading and start playing!
Building Stream Infrastructure across Multiple Data Centers with Apache Kafka
To manage the ever-increasing volume and velocity of data within your company, you have successfully made the transition from single machines and one-off solutions to large distributed stream infrastructures in your data center, powered by Apache Kafka. But what if one data center is not enough? I will describe building resilient data pipelines with Apache Kafka that span multiple data centers and points of presence, and provide an overview of best practices and common patterns while covering key areas such as architecture guidelines, data replication, and mirroring as well as disaster scenarios and failure handling.
A la rencontre de Kafka, le log distribué par Florian GARCIA
Kafka c’est un peu la nouvelle star sur la scène des files de messages. Pourtant Kafka ne se présente pas en tant que tel, c’est un log distribué !
Alors qu’est ce que c’est ? Comment ça marche ? Et surtout comment et pourquoi je l’utilise ?
Dans cette session, on décortique la bête pour tout vous expliquer ! Au programme : des concepts, des cas d’usage, du streaming et un retour d’expérience !
microXchg 2017: "Microservices: The People and Organisational Impact"
The document discusses the organizational and people impacts of implementing microservices. It argues that many current problems stem from organizational and people issues rather than technical problems. Existing solutions around strategy, feedback, and defining responsibilities can help address these challenges. Technical leadership is important to promote shared understanding and manage risks. Feedback through visibility and learning is also vital. Responsibilities like DevOps roles need to be clearly defined.
OpenShift is Red Hat's container application platform that provides a full-stack platform for deploying and managing containerized applications. It is based on Docker and Kubernetes and provides additional capabilities for self-service, automation, multi-language support, and enterprise features like authentication, centralized logging, and integration with Red Hat's JBoss middleware. OpenShift handles building, deploying, and scaling applications in a clustered environment with capabilities for continuous integration/delivery, persistent storage, routing, and monitoring.
The document lists various geographic locations around Europe, Africa, and Asia including the Strait of Gibraltar, Swiss Alps, Iceland, Black Sea, and Red Sea. It expresses admiration for the beauty of the Earth even in darkness, repeating the sentiment multiple times.
Product Development Communications Executive Pat Scherschel 2011
The document provides an executive biography and resume for Patricia M. Scherschel, outlining her extensive experience over 20 years in product development, corporate communications, and public relations roles within the student loan and policy research industries. She has held leadership positions at Fortune 500 companies developing multi-billion dollar student loan programs and served as an executive editor for international business publications.
This document provides information about RK SWAMY BBDO, an Indian advertising agency that has been ranked in the top 10 in India. It joined the global BBDO network in 1986. The agency aims to help clients achieve their marketing goals through developing solutions and providing support. It provides services such as advertising, creative work, market research, and interactive services. Some of RK SWAMY BBDO's clients include Titan, Air India, Mercedes Benz, and Mars.
The document provides an overview of the rational treatment process and is intended to guide undergraduate medical students in developing good prescribing skills. It outlines the steps in treating a patient, from defining the problem and specifying the objective to monitoring treatment, using a case example of a taxi driver with a dry cough. The overview presented in this chapter lays the groundwork for more detailed discussion of each step in subsequent chapters.
The document provides guidance on cultural norms and business etiquette when conducting business in China. It lists 11 common faux pas that should be avoided, such as accepting business cards with one hand, eating or drinking before a host, discussing politics or Taiwan's independence, touching in public, and gifting items associated with death like clocks or black items. Conducting oneself respectfully and understanding cultural norms around seniority, meals, and greetings is important for success when working with Chinese business counterparts.
The document discusses file handling in C programming. It explains that files allow permanent storage of data that can be accessed quickly through library functions. There are two main types of files - sequential and random access. It also describes various functions used to open, read, write, close and manipulate files like fopen(), fread(), fwrite(), fclose() etc. It provides examples of reading from and writing to text and binary files as well as reading and writing structures and integers from files.
Encryption techniques are used to securely transmit data over networks. Pseudorandom noise adds statistical randomness to encrypted signals. Data encryption converts plaintext into unreadable ciphertext. Link encryption encrypts data as it is transmitted between network points. A virtual private network (VPN) uses encryption to create a secure connection over public lines like the internet and allow private network extension.
This document appears to be a study guide in Spanish for an English as a Second Language class. It contains exercises to test students' comprehension of basic English conversations and vocabulary related to community services. The exercises include choosing the correct response to complete a sample conversation about buying a DVD, identifying different types of community services from images, and matching community locations to their uses. The study guide provides context for learning English terms in a real-world setting.
The document discusses 3D chip stacking technologies and the advantages of using thermally conductive adhesives for applications such as smartphones. It notes that wire bonding has limitations and that flip chip cannot be used for chip stacking. 3D stacking with thermal interconnects is presented as an inevitable future technology for miniaturization and performance gains. Specific adhesives produced by MicroCoat Technologies are highlighted for their high thermal conductivity and suitability for applications requiring heat dissipation.
A Power Point Presentation of a motivational and inspirational story. Done by Bro. Oh Teik Bin, Lower Perak Buddhist association, Teluk Intan, Malaysia. Chinese Translation by Bro. Lau Bain Sin & Bro. Teh Kee Keang
This document discusses using microservices with Kafka. It describes how Kafka can be used to connect microservices for asynchronous communication. It outlines various features of Kafka like high throughput, replication, partitioning, and how it can provide reliability. Examples are given of how microservices could use Kafka for logging, filtering messages, and dispatching to different topics. Performance benefits of Kafka are highlighted like scalability and ability to handle high volumes of messages.
Kafka Summit SF 2017 - Best Practices for Running Kafka on Docker Containersconfluent
This document discusses best practices for running Apache Kafka on Docker containers. It describes how to design Kafka deployments using Docker to provide portability, elasticity, and multi-tenancy. Key considerations include allocating appropriate resources to different roles like brokers and Zookeepers, enabling auto-configuration, and providing security and network isolation. The document outlines an implementation using Dockerfiles, configurations, and orchestration to deploy multi-node Kafka clusters across multiple hosts.
This document provides an overview of lightweight messaging and remote procedure call (RPC) systems in distributed systems. It discusses messaging systems, typical peer-to-peer and broker-based messaging topologies, characteristics and features of messaging systems, main classes of messaging systems including enterprise service buses (ESBs), JMS implementations, AMQP implementations, and lightweight modern systems. It also covers RPC, serialization libraries, differences between messaging and RPC, examples of ZeroMQ for peer-to-peer messaging, Apache Kafka for broker-based messaging, and Twitter Finagle for scalable RPC.
Data Models and Consumer Idioms Using Apache Kafka for Continuous Data Stream...Erik Onnen
The document discusses Urban Airship's use of Apache Kafka for processing continuous data streams. It describes how Urban Airship uses Kafka for analytics, operational data, and presence data. Producers write device data to Kafka topics, and consumers create indexes from the data in databases like HBase and write to operational data warehouses. The document also covers Kafka concepts, best use cases, limitations, and examples of data structures for storing device metadata in Kafka streams.
This presentation from the I Love APIs conference makes the case for why Node and Docker are great together for implementing Microservice architecture. It also provides an quick orientation for getting started with Docker Machine, Node, and Mongo with container linking and data volume containers.
My talk at ScaleConf 2017 in Cape Town on some tips and tactics for scaling WordPress, with reference to WordPress.com and the container-based VIP Go platform.
Video of my talk is here: https://www.youtube.com/watch?v=cs0DcY80spw
Protecting your data at rest with Apache Kafka by Confluent and Vormetricconfluent
This document discusses securing Apache Kafka deployments with Vormetric and Confluent Platform. It begins with an introduction to Apache Kafka and Confluent Platform. It then provides an overview of Vormetric's policy-driven security solution and how it can be used to encrypt Kafka data at rest. The document outlines the typical Confluent Platform deployment architecture and various security considerations, such as authentication, authorization, and data encryption. Finally, it provides steps for implementing secure deployments using SSL, Kerberos, and Vormetric encryption policies.
Nodeconf Barcelona 2015 presentation exploring several ways of building microservices in an asynchronous way. Presented the concept of a broker as an alternative to a multiple point-to-point architecture.
Moving Gigantic Files Into and Out of the Alfresco RepositoryJeff Potts
This talk is a technical case study showing show Metaversant solved a problem for one of their clients, Noble Research Institute. Researchers at Noble deal with very large files which are often difficult to move into and out of the Alfresco repository.
Reducing Microservice Complexity with Kafka and Reactive Streamsjimriecken
My talk from ScalaDays 2016 in New York on May 11, 2016:
Transitioning from a monolithic application to a set of microservices can help increase performance and scalability, but it can also drastically increase complexity. Layers of inter-service network calls for add latency and an increasing risk of failure where previously only local function calls existed. In this talk, I'll speak about how to tame this complexity using Apache Kafka and Reactive Streams to:
- Extract non-critical processing from the critical path of your application to reduce request latency
- Provide back-pressure to handle both slow and fast producers/consumers
- Maintain high availability, high performance, and reliable messaging
- Evolve message payloads while maintaining backwards and forwards compatibility.
Kafka's basic terminologies, its architecture, its protocol and how it works.
Kafka at scale, its caveats, guarantees and use cases offered by it.
How we use it @ZaprMediaLabs.
This document provides an introduction and overview of RESTful web services. It discusses REST principles such as resources, addressability, statelessness, uniform interface, and representations. It also covers designing RESTful APIs, including examples from Amazon S3. The document outlines an agenda to discuss introduction, principles, design, implementations, and implementation of RESTful APIs and web services.
Load Balancing for Containers and Cloud Native ArchitectureChiradeep Vittal
This document discusses how load balancing needs have changed with the rise of containers and microservices. Traditional load balancers are not well-suited for dynamic container environments where services and topology frequently change. New approaches are needed like integrating load balancers with container orchestration platforms, using client-side load balancing, and leveraging load balancers for advanced patterns like zero-downtime deployments, circuit breaking, visibility and security segmentation. Load balancers are playing an increasingly important role in cloud native architectures.
The document discusses the REST (REpresentational State Transfer) architectural style and how it differs from traditional SOA (Service Oriented Architecture). It outlines the key principles of REST including addressing resources with URIs, using a uniform interface (HTTP methods), stateless communication, and hypermedia as the driver of application state. The document explains how the web exemplifies REST through the use of URLs, HTTP, and standard formats to access and transfer representations of resources.
This document discusses using Apache Kafka to build a message bus for aggregating activity information from various services and enabling communication between services. It outlines the challenges of needing a way to aggregate activity data and needing a messaging backbone. It then explains how Apache Kafka provides a scalable, durable, distributed solution as a publish-subscribe messaging system to address these needs. Key features of Kafka like speed, scalability, durability and distributed design are highlighted. An example setup and usage with Ruby is also briefly described.
This document discusses security features in Apache Kafka including SSL, SASL authentication using Kerberos or plaintext, and authorization controls. It provides an overview of how SSL and SASL authentication work in Kafka as well as how the Kafka authorizer controls access at a fine-grained level through ACLs defined on topics, operations, users and hosts. It also briefly mentions securing Zookeeper which stores Kafka metadata and ACLs.
Want to get your hands dirty and play around with the Middleware that is going to amaze you with the rich components provided within and made integration much easier pattern base framework. Stop reading and start playing!
Building Stream Infrastructure across Multiple Data Centers with Apache KafkaGuozhang Wang
To manage the ever-increasing volume and velocity of data within your company, you have successfully made the transition from single machines and one-off solutions to large distributed stream infrastructures in your data center, powered by Apache Kafka. But what if one data center is not enough? I will describe building resilient data pipelines with Apache Kafka that span multiple data centers and points of presence, and provide an overview of best practices and common patterns while covering key areas such as architecture guidelines, data replication, and mirroring as well as disaster scenarios and failure handling.
A la rencontre de Kafka, le log distribué par Florian GARCIALa Cuisine du Web
Kafka c’est un peu la nouvelle star sur la scène des files de messages. Pourtant Kafka ne se présente pas en tant que tel, c’est un log distribué !
Alors qu’est ce que c’est ? Comment ça marche ? Et surtout comment et pourquoi je l’utilise ?
Dans cette session, on décortique la bête pour tout vous expliquer ! Au programme : des concepts, des cas d’usage, du streaming et un retour d’expérience !
microXchg 2017: "Microservices: The People and Organisational Impact"Daniel Bryant
The document discusses the organizational and people impacts of implementing microservices. It argues that many current problems stem from organizational and people issues rather than technical problems. Existing solutions around strategy, feedback, and defining responsibilities can help address these challenges. Technical leadership is important to promote shared understanding and manage risks. Feedback through visibility and learning is also vital. Responsibilities like DevOps roles need to be clearly defined.
OpenShift is Red Hat's container application platform that provides a full-stack platform for deploying and managing containerized applications. It is based on Docker and Kubernetes and provides additional capabilities for self-service, automation, multi-language support, and enterprise features like authentication, centralized logging, and integration with Red Hat's JBoss middleware. OpenShift handles building, deploying, and scaling applications in a clustered environment with capabilities for continuous integration/delivery, persistent storage, routing, and monitoring.
The document lists various geographic locations around Europe, Africa, and Asia including the Strait of Gibraltar, Swiss Alps, Iceland, Black Sea, and Red Sea. It expresses admiration for the beauty of the Earth even in darkness, repeating the sentiment multiple times.
Product Development Communications Executive Pat Scherschel 2011patriciaindy2011
The document provides an executive biography and resume for Patricia M. Scherschel, outlining her extensive experience over 20 years in product development, corporate communications, and public relations roles within the student loan and policy research industries. She has held leadership positions at Fortune 500 companies developing multi-billion dollar student loan programs and served as an executive editor for international business publications.
This document provides information about RK SWAMY BBDO, an Indian advertising agency that has been ranked in the top 10 in India. It joined the global BBDO network in 1986. The agency aims to help clients achieve their marketing goals through developing solutions and providing support. It provides services such as advertising, creative work, market research, and interactive services. Some of RK SWAMY BBDO's clients include Titan, Air India, Mercedes Benz, and Mars.
The document provides an overview of the rational treatment process and is intended to guide undergraduate medical students in developing good prescribing skills. It outlines the steps in treating a patient, from defining the problem and specifying the objective to monitoring treatment, using a case example of a taxi driver with a dry cough. The overview presented in this chapter lays the groundwork for more detailed discussion of each step in subsequent chapters.
The document provides guidance on cultural norms and business etiquette when conducting business in China. It lists 11 common faux pas that should be avoided, such as accepting business cards with one hand, eating or drinking before a host, discussing politics or Taiwan's independence, touching in public, and gifting items associated with death like clocks or black items. Conducting oneself respectfully and understanding cultural norms around seniority, meals, and greetings is important for success when working with Chinese business counterparts.
The document discusses file handling in C programming. It explains that files allow permanent storage of data that can be accessed quickly through library functions. There are two main types of files - sequential and random access. It also describes various functions used to open, read, write, close and manipulate files like fopen(), fread(), fwrite(), fclose() etc. It provides examples of reading from and writing to text and binary files as well as reading and writing structures and integers from files.
Encryption techniques are used to securely transmit data over networks. Pseudorandom noise adds statistical randomness to encrypted signals. Data encryption converts plaintext into unreadable ciphertext. Link encryption encrypts data as it is transmitted between network points. A virtual private network (VPN) uses encryption to create a secure connection over public lines like the internet and allow private network extension.
This document appears to be a study guide in Spanish for an English as a Second Language class. It contains exercises to test students' comprehension of basic English conversations and vocabulary related to community services. The exercises include choosing the correct response to complete a sample conversation about buying a DVD, identifying different types of community services from images, and matching community locations to their uses. The study guide provides context for learning English terms in a real-world setting.
Thermal Management And Sd0802 C Presentationsforman1
The document discusses 3D chip stacking technologies and the advantages of using thermally conductive adhesives for applications such as smartphones. It notes that wire bonding has limitations and that flip chip cannot be used for chip stacking. 3D stacking with thermal interconnects is presented as an inevitable future technology for miniaturization and performance gains. Specific adhesives produced by MicroCoat Technologies are highlighted for their high thermal conductivity and suitability for applications requiring heat dissipation.
A Glass Of Milk ( in English & Chinese )OH TEIK BIN
A Power Point Presentation of a motivational and inspirational story. Done by Bro. Oh Teik Bin, Lower Perak Buddhist association, Teluk Intan, Malaysia. Chinese Translation by Bro. Lau Bain Sin & Bro. Teh Kee Keang
The document provides an overview of the Bible study for the second Sunday of Easter, including summaries and commentary on the readings. The first reading from Acts describes the early Christian community devoting themselves to teaching, communal life, breaking bread, and prayer. The second reading from 1 Peter discusses the new birth Christians receive through Christ's resurrection and finding joy even when suffering. The Gospel reading recounts Jesus' appearance to the disciples after his resurrection and their commissioning to forgive sins, as well as Thomas' later appearance and profession of faith.
This document provides step-by-step instructions for bleeding Avid Juicy Ultimate disc brakes using a SRAM bleed kit. It describes preparing the syringes, caliper, and lever, then bleeding the caliper, hose, lever, and master cylinder. Tips are included for ensuring no air is introduced and for resetting the pads. The process aims to improve brake feel and consistency by removing air from the system.
Advance Publications is a privately held media company estimated to have $6.78 billion in media revenue in 2012/13. It owns magazine publisher Condé Nast with titles like Vogue and The New Yorker, local newspapers across the US including The Plain Dealer, and a 31% stake in Discovery Communications. Advance also has interests in cable TV provider Bright House Networks and several websites connected to its print properties.
1. The document presents statistical analyses of the relationships between various variables including education, prestige, income, health status, HIV duration, quality of life, TV watching, cosmopolitanism, family planning, study time, dating, cleanliness, truancy, socioeconomic status, and criminal tendencies.
2. Correlation coefficients and coefficients of determination (R2 values) are reported to quantify the strength and direction of the relationships between the variables.
3. Regression equations are presented to model the relationships between dependent and independent variables.
Scale changes everything. Number of connections and destinations went from dozen to thousands, number of messages increased by order of magnitude. What once was quite adequate for enterprise messaging can't scale to support "Internet of Things". We need new protocols, patterns and architectures to support this new world. This session will start with basic introduction to the concept of Internet of things. Next it will discuss general technical challenges involved with the concept and explain why it is becoming mainstream now. Now we're ready to start talking about solutions. We will introduce some messaging patterns (like telemetry and command/control) and protocols (such as MQTT and AMQP) used in these scenarios. Finally we will see how Apache ActiveMQ is gearing up for this race. We will show tips for horizontal and vertical scaling of the broker, related projects that can help with deployments and what the future development road map looks like.
Velocity Conference '13: Asynchronous messaging for performance optimization,...Al Sargent
How do Google, Twitter, and Instagram ensure fast application performance at scale? One technique is asynchronous messaging using RabbitMQ to prevent application bottlenecks. In this session, we’ll cover common asynchronous messaging patterns and how to implement them in RabbitMQ, common pitfalls to avoid, and how to cluster RabbitMQ for increased scalability and reliability.
This document discusses various message queue technologies including RabbitMQ, ZeroMQ, cloud-based options like Azure Service Bus and Amazon SQS/SNS, and the lightweight NATS system. It provides overviews of each technology, highlighting key features, protocols, and use cases. Examples and code demos are shown for RabbitMQ and ZeroMQ. The document aims to help readers understand different message queue options and pick the most suitable one based on their distributed system and cloud hosting needs.
Au delà des brokers, un tour de l’environnement Kafka | Florent Ramièreconfluent
During the Confluent Streaming event in Paris, Florent Ramière, Technical Account Manager at Confluent, goes beyond brokers, introducing a whole new ecosystem with Kafka Streams, KSQL, Kafka Connect, Rest proxy, Schema Registry, MirrorMaker, etc.
Session on CloudStack, intended for new users to CloudStack, provides an overview to varied audience levels information on usages, use cases, deployment and its architecture.
London JBUG - Connecting Applications Everywhere with JBoss A-MQJBUG London
Presentation by Rob Davies (Red Hat) delivered at the London JBoss USer Group event on the 10th of July 2013.
See the video here: http://youtu.be/VrJyKLAXVTg
As part of the FuseSource acquisition, Red Hat now supports Apache ActiveMQ as the recently released Red Hat JBoss A-MQ product.
ActiveMQ is the most widely used message-oriented middleware that uses messaging to connect remote applications written in Java, C/C++, Python, Perl, Ruby, and many other languages. ActiveMQ is standards based and supports messaging protocols such as AMQP 1.0, WebSockets, Stomp, OpenWire, and MQTT.
In this session, Rob Davies will discuss the product’s features and functionality, and demonstrate connectivity from a microprocessor to web sockets using JBoss A-MQ.
IBM Message Hub service in Bluemix - Apache Kafka in a public cloudAndrew Schofield
This talk was presented at the Kafka Meetup London meeting on 20 January 2016. You can find more information about Message Hub here: http://ibm.biz/message-hub-bluemix-catalog
An introduction to SignalR
This deck was part of my presentation to Virtusa employees on an ASP.NET asynchronous, persistent signaling library known as SignalR
There is also a slide on how to use SignalR with SharePoint.
Date: August 2013
Follow / Tweet me: @ShehanPeruma
MQTT is a lightweight publish/subscribe messaging protocol that is ideal for constrained environments like sensors and mobile devices. It was invented in 1999 by IBM employees Dr. Andy Stanford-Clark and Arlen Nipper. MQTT uses a broker-based messaging model with a publish/subscribe pattern, and supports three qualities of service. It has been widely adopted in applications involving sensors, mobile devices, and the Internet of Things.
The presentation discusses iDirect's Evolution product line including the iDX 1.0 satellite router, X3 router, and line cards. Key features highlighted are DVB-S2/ACM technology for improved bandwidth efficiency, integration with the X3 satellite router, and software tools for monitoring and adjusting ACM performance. Benefits of iDirect's DVB-S2/ACM implementation include increased throughput and bandwidth savings while easing network configuration.
Matteo Merli, the tech lead for Cloud Messaging Service at Yahoo, went through their design decisions, how they reached that and how they leverage Apache BookKeeper to implement a multi-tenant messaging service.
ITB2019 Multi-language / multi-OS communication using RabbitMQ - Wil de BruinOrtus Solutions, Corp
Our web hosting company is using many different services for managing e-mail, spam-filters, DNS, domain registrations, SSL registrations, ticket systems and more. Some of these services have well defined Web API’s, others can only be managed by simple command line scripts.
In this session we will explain how we tried to automate the various workflows by using a messaging system such as RabbitMQ for communication between our cfml based customer control panel and these services.
Multi-language/multi-OS communication using RabbitMQWil de Bruin
This document discusses using RabbitMQ for multi-language and multi-OS communication. It provides an overview of messaging concepts in RabbitMQ, describes a use case for a web hosting panel that requires communication between different systems, and demonstrates setting up producers and consumers in ColdFusion and other languages to send and receive messages via RabbitMQ. While ColdFusion RabbitMQ producers are straightforward, consuming messages can be challenging due to limitations in ColdFusion.
Scale changes everything. What once was quite adequate for enterprise messaging can't scale to support "Internet of Things". We need new protocols, patterns and architectures to support this new world. This session will start with basic introduction to the concept of Internet of Things. Next it will discuss general technical challenges involved with the concept and explain why it is becoming mainstream now. Now we’re ready to start talking about solutions. We will introduce some messaging patterns (like telemetry and command/control) and protocols (such as MQTT and AMQP) used in these scenarios. Finally we will see how Apache ActiveMQ is gearing up for this race. We will show tips for horizontal and vertical scaling of the broker, related projects that can help with deployments and what the future development road map looks like.
Martyn Taylor is a senior software engineer at Red Hat, with over 7 years’ experience working on cloud, middleware and messaging software. Martyn currently works on the Apache ActiveMQ suite of projects.
The Overview of Microservices ArchitectureParia Heidari
This document discusses monolithic architecture and microservices architecture. It begins by defining monolithic architecture as having a single code base with multiple components/modules. It then lists advantages like being simple to develop, test, deploy and scale, as well as drawbacks like flexibility, maintenance, reliability, and scaling challenges.
Microservices architecture is presented as a solution to problems with monolithic architecture. Each microservice has a specific focus and functionality. Benefits include improved testability, loose coupling, and ability to develop, deploy and scale services independently. Challenges include increased complexity of developing, testing and operating distributed systems.
The document provides examples and discusses strategies for migrating a monolithic system to microservices, technologies
Overview for RabbitMQ with AMQP protocol and a discussion for the AMQP model with message properties and publish and consume message
types of exchange
main properties of the queue
Open Source Middleware for the Cloud: WSO2 StratosWSO2
Stratos is an open source middleware platform for the cloud that provides Platform as a Service (PaaS) capabilities. It is based on the WSO2 Carbon middleware platform and provides features such as self-service provisioning, multi-tenancy, elastic scaling, metering, and billing. Stratos offers a complete PaaS solution with services for application development, data, integration, identity, and logging in a cloud environment.
The presentation covers-
1. Red Hat JBoss Developer Program
2. Red Hat JBoss Fuse
3. Red Hat JBoss Data Virtualization
The workshop was recorded and we will provide a link once it has been posted.
Apache Camel journey with Microservices, lessons learned and utilisation of Fabric8 to make Docker, Kubernetes and OpenShift easy for developers to use
This document provides an overview of Red Hat JBoss Fuse, an open source integration platform. It discusses the history and components of JBoss Fuse, including Apache Camel, CXF, ActiveMQ, Karaf and Fabric8. It describes how JBoss Fuse can enable integration everywhere in a real-time enterprise by integrating applications, services, devices and partners through its lightweight footprint and deployment options both on-premise and in the cloud. The document also highlights key benefits of JBoss Fuse such as reducing costs, simplifying management and enabling new business opportunities through greater connectivity and data sharing.
Connecting Applications Everywhere with ActiveMQRob Davies
This document summarizes a presentation given by Rob Davies at the CamelOne 2013 conference in Boston, MA on June 10-11, 2013. The presentation introduced Apache ActiveMQ, an open-source message broker, and discussed its features including messaging protocols, management tools, high availability, and integration with Apache Camel. It also covered challenges of deploying and maintaining large ActiveMQ clusters and how Red Hat Fuse Fabric can help address these challenges.
OSGi made simple - Fuse Application BundlesRob Davies
FuseSource introduces Fabric Application Bundles (FABs) which make deploying applications in OSGi containers simpler. FABs allow developers to deploy Java applications packaged with Maven dependencies as single deployment units. When installed, FuseSource's Fuse ESB automatically installs all transitive dependencies of a FAB. This provides an easier deployment model than traditional OSGi bundles while still allowing developers to benefit from OSGi features like dynamic updates and versioning when needed. FABs also provide options for configuring shared dependencies across multiple applications to gain code sharing benefits of OSGi.
Enterprise Integration Patterns with ActiveMQRob Davies
This document discusses enterprise integration patterns and deployments using Apache ActiveMQ. It provides an overview of key integration concepts like message channels, routing, types of messages, push and pull integration models, request/reply patterns, and job processing. It also covers deployment patterns such as hub and spoke and failover between data centers. Finally, it introduces Apache Camel as a powerful integration framework that supports these patterns and can be used with ActiveMQ.
This document discusses open source software and the Apache Software Foundation (ASF). It provides an overview of the history of open source development including key events and projects. It then describes how individuals and organizations can contribute to Apache projects, the benefits of contributing, and the processes used within the ASF community. The document also explains how FuseSource works with Apache projects, including how FuseSource employees contribute to Apache and how FuseSource packages certified distributions of Apache projects.
Lots of bloggers are using Google AdSense now. It’s getting really popular. With AdSense, bloggers can make money by showing ads on their websites. Read this important article written by the experienced designers of the best website designing company in Delhi –
A Comparative Analysis of Functional and Non-Functional Testing.pdfkalichargn70th171
A robust software testing strategy encompassing functional and non-functional testing is fundamental for development teams. These twin pillars are essential for ensuring the success of your applications. But why are they so critical?
Functional testing rigorously examines the application's processes against predefined requirements, ensuring they align seamlessly. Conversely, non-functional testing evaluates performance and reliability under load, enhancing the end-user experience.
React Native vs Flutter - SSTech SystemSSTech System
Your project needs and long-term objectives will ultimately choose which of React Native and Flutter to use. For applications using JavaScript and current web technologies in particular, React Native is a mature and trustworthy choice. For projects that value performance and customizability across many platforms, Flutter, on the other hand, provides outstanding performance and a unified UI development experience.
Break data silos with real-time connectivity using Confluent Cloud Connectorsconfluent
Connectors integrate Apache Kafka® with external data systems, enabling you to move away from a brittle spaghetti architecture to one that is more streamlined, secure, and future-proof. However, if your team still spends multiple dev cycles building and managing connectors using just open source Kafka Connect, it’s time to consider a faster and cost-effective alternative.
Are you wondering how to migrate to the Cloud? At the ITB session, we addressed the challenge of managing multiple ColdFusion licenses and AWS EC2 instances. Discover how you can consolidate with just one EC2 instance capable of running over 50 apps using CommandBox ColdFusion. This solution supports both ColdFusion flavors and includes cb-websites, a GoLang binary for managing CommandBox websites.
introduction of Ansys software and basic and advance knowledge of modelling s...sachin chaurasia
Ansys Mechanical enables you to solve complex structural engineering problems and make better, faster design decisions. With the finite element analysis (FEA) solvers available in the suite, you can customize and automate solutions for your structural mechanics problems and parameterize them to analyze multiple design scenarios. Ansys Mechanical is a dynamic tool that has a complete range of analysis tools.
Responsibilities of Fleet Managers and How TrackoBit Can Assist.pdfTrackobit
What do fleet managers do? What are their duties, responsibilities, and challenges? And what makes a fleet manager effective and successful? This blog answers all these questions.
Sami provided a beginner-friendly introduction to Amazon Web Services (AWS), covering essential terms, products, and services for cloud deployment. Participants explored AWS' latest Gen AI offerings, making it accessible for those starting their cloud journey or integrating AI into coding practices.
Software development... for all? (keynote at ICSOFT'2024)miso_uam
Our world runs on software. It governs all major aspects of our life. It is an enabler for research and innovation, and is critical for business competitivity. Traditional software engineering techniques have achieved high effectiveness, but still may fall short on delivering software at the accelerated pace and with the increasing quality that future scenarios will require.
To attack this issue, some software paradigms raise the automation of software development via higher levels of abstraction through domain-specific languages (e.g., in model-driven engineering) and empowering non-professional developers with the possibility to build their own software (e.g., in low-code development approaches). In a software-demanding world, this is an attractive possibility, and perhaps -- paraphrasing Andy Warhol -- "in the future, everyone will be a developer for 15 minutes". However, to make this possible, methods are required to tweak languages to their context of use (crucial given the diversity of backgrounds and purposes), and the assistance to developers throughout the development process (especially critical for non-professionals).
In this keynote talk at ICSOFT'2024 I presented enabling techniques for this vision, supporting the creation of families of domain-specific languages, their adaptation to the usage context; and the augmentation of low-code environments with assistants and recommender systems to guide developers (professional or not) in the development process.
Discover the Power of ONEMONITAR: The Ultimate Mobile Spy App for Android Dev...onemonitarsoftware
Unlock the full potential of mobile monitoring with ONEMONITAR. Our advanced and discreet app offers a comprehensive suite of features, including hidden call recording, real-time GPS tracking, message monitoring, and much more.
Perfect for parents, employers, and anyone needing a reliable solution, ONEMONITAR ensures you stay informed and in control. Explore the key features of ONEMONITAR and see why it’s the trusted choice for Android device monitoring.
Share this infographic to spread the word about the ultimate mobile spy app!
Attendance Tracking From Paper To DigitalTask Tracker
If you are having trouble deciding which time tracker tool is best for you, try "Task Tracker" app. It has numerous features, including the ability to check daily attendance sheet, and other that make team management easier.
2. RED HAT | Fabric8 Rocks!2
Rob Davies
• Director, Engineering xPaaS
• Technical Director of Fuse
Engineering
• Over 20 years experience of
developing large scale solutions for
telcos and finance
• Creator of ActiveMQ and ServiceMix
• Committer on open source projects,
including Apache Camel …
3. RED HAT | Fabric8 Rocks!3
Agenda
• Introduction to Fabric8
• Enterprise messaging
• Fabric8MQ
• Demo
4. RED HAT | Fabric8 Rocks!4
Fabric8
• Open source, ASL 2.0 licensed project, built to provide
the management infrastructure for Microservices
deployments
• Management: console, logging, metrics, API
Management
• Continuous Delivery - workflow
• Integration Platform as a Service – Camel route
visualization, API registry, Messaging as a Service, …
• Tools – Kubernetes/OpenShift build integration,
Kubernetes component test support, CDI extensions
5. RED HAT | Fabric8 Rocks!5
Fabric8:
GCE AWS CoreOS Mesos vSphere Fedora VagrantAzure
Kubernetes
Centralized
Logging Metrics
Deep Application
Management
API
Registry
API
Man
Fabric8MQCamel
Fabric8
Java tools
socialSonaQubeGogsJenkins Nexus
6. RED HAT | Fabric8 Rocks!6
Agenda
• Introduction to Fabric8
• Enterprise messaging
• Fabric8MQ
• Demo
7. RED HAT | Fabric8 Rocks!7
Why use messaging ?
• Robustness to change
• Time independence
• Hide latency
• Event driven
• Platform and language
independence
Broker
Message in
Message out after
enrichment by Process B
Process C
Process B
Process A
Queue:Foo
Queue:Bar
8. RED HAT | Fabric8 Rocks!8
Enterprise Message brokers
• Designed to support many different messaging
patterns
• highly available
• Support clustering
• Support store and forward
• But – are usually very static in nature
9. RED HAT | Fabric8 Rocks!9
• Top Level Apache Software Foundation Project
• Wildly popular, high performance, reliable message broker
• Connects to nearly everything
• Native Java, C/C++, .Net,
• AMQP 1.0, MQTT 3.1, STOMP (1.0-1.2) and OpenWire
• STOMP enables Ruby, JS, Perl, Python, PHP, ActionScript
…
• Embedded and standalone deployment options
10. RED HAT | Fabric8 Rocks!10
Message Channels and Routing
• Message Channels
• Named communication between interested parties
• JMS calls them ‘Destinations’
• Can “tune-in” to multiple channels using wildcards
• Can fine-tune message consumption with selectors
• Can route a message based on content
11. RED HAT | Fabric8 Rocks!11
Message Channels = JMS Destinations
Broker Consumer
Consumer
Destination
WIDGET
Destination
ORDER
Producer
Consumer
12. RED HAT | Fabric8 Rocks!12
Message Routing: Selectors
Producer Destination
Consumer
Color = red
Consumer
Color = blue
14. RED HAT | Fabric8 Rocks!14
Message Groups
Producer
Consumer
Consumer
Consumer
Queue:Prices
Message message = session.createTextMessage(“hi JBCNConf”);
message.setStringProperty("JMSXGroupID", ”JavaRocks");
producer.send(message);
15. RED HAT | Fabric8 Rocks!15
High Availability clustering:
MasterClient Slave Slave
Only one broker is active (the master) at any one time.
1. send
3. receipt
2. store
16. RED HAT | Fabric8 Rocks!16
Network of Brokers:
Producer
Highly reliable, store and forward
Consumer
1. send
Broker1
2. store
Broker2
5. store
4. Network
send
6. Network
receipt
3. receipt
7. delete
6. Network
send
7. acknowledge
8. delete
17. RED HAT | Fabric8 Rocks!17
Networks of Brokers: some limitations
• Performance – messages are always stored by the
broker to disk before forwarding to another broker –
this can increase latency by at least a factor of 10
• Networks are chatty – routing information is passed
from broker to broker every time a consumer starts or
stops
• Networks are a bottleneck – networks are
implemented as one TCP/IP connection – this is
natural choke point for high throughput scenarios
• Messages can be orphaned – If a broker goes down,
locally stored messages won’t get delivered until the
broker is recovered
18. RED HAT | Fabric8 Rocks!18
Networks of Brokers: Worst bit …
Producer ConsumerBroker1 Broker2
This is
configured
differently to …
19. RED HAT | Fabric8 Rocks!19
Networks of Brokers: Worst bit …
Producer ConsumerBroker1 Broker2
To this
Broker3
20. RED HAT | Fabric8 Rocks!20
ActiveMQ is static:
21. RED HAT | Fabric8 Rocks!21
ActiveMQ Key Features
Fast Storage
Connections
A-MQ
Embedded Camel
OpenWire,
STOMP
MQTT
AMQP
WebSockets
Scaling Connections
A problem
KahaDB/LevelDB
Lots and Lots of
these
22. RED HAT | Fabric8 Rocks!22
To Scale A-MQ needs to focus …
Fast Storage
A-MQ
Remove all the
cruft – allow
ActiveMQ to focus
on message
routing …
23. RED HAT | Fabric8 Rocks!23
Messaging for cloud based deployments
• Needs to support many thousands of clients
• Flexible, brokers need to be spun up and down, based
on demand
• Client connections may need to be multiplexed, to
decrease the load on individual message brokers
• Popular messaging protocols support
• Flexible routing needs to be supported
24. RED HAT | Fabric8 Rocks!24
Agenda
• Introduction to Fabric8
• Enterprise messaging
• Fabric8MQ
• Demo
25. RED HAT | Fabric8 Rocks!25
Fabric8 MQ is built on Vert.x
• Lightweight, multi-reactive, application platform
• Inspired from Erlang/OTP
• Polygot
• High performance
• Asynchronous, non-blocking: – high level of
concurrency
26. RED HAT | Fabric8 Rocks!26
Vert.x is just fast …
27. RED HAT | Fabric8 Rocks!27
Fabric8 MQ Message Flow:
Protocol
Conversion
Camel
Routing
API
Management Multiplexer
Destination
Sharding
Broker
Control
28. RED HAT | Fabric8 Rocks!28
Fabric8 MQ Protocol Conversion
• We convert to ActiveMQ OpenWire. This saves
ActiveMQ doing this, allowing it to expend all its
resources to pushing messages in and out of Queues
• Protocols currently supported:
• OpenWire
• Stomp
• MQTT
• AMQP 1.0
29. RED HAT | Fabric8 Rocks!29
Camel Routing:
Camel is embedded to allow flexible routing:
Topic:Foo
MessageMessage Message
Queue:Foo
Channel
30. RED HAT | Fabric8 Rocks!30
API Management
• Fabric8 uses APIMan for its API Management – see
http://apiman.io
• Utilized within Fabric8 to provide:
• Central common place for managing all APIs (including
Message Queues)
• Control and Access policies
• Rate Limiting
• Metrics and Billing
31. RED HAT | Fabric8 Rocks!31
Multiplexing
• ActiveMQ performs better the lower
the number of connections – less
contention
• IoT applications have long lived
connections, but small amount of
traffic
• All configurable – you can decide
how fine or coarse grained you want
multiplexing
• Fabric8MQ scales up/down
multiplexers as required
32. RED HAT | Fabric8 Rocks!32
Destination Sharding: Benefits
• There is an overhead associated with a
Destination – restrict the number of
Destinations per Broker to improve
performance
• Co-locate producers and consumers of a
Destination to the same broker reduces latency
and improves overall performance
• Increased scalability for your messaging
solution
• This is done automatically by Fabric8 MQ
33. RED HAT | Fabric8 Rocks!33
Destination Sharding: Fabric8 MQ Internal Model
• Discover and track all allocated
brokers
• Fabric8 MQ regularly updates its
internal model by examining
internals of brokers running via
Jolokia allowing multiple
Fabric8-MQ instances to run
(co-operatively scalable)
• Scales up and down brokers –
moving destinations and clients
between brokers
• Can dynamically set limits on
number of brokers, and broker
limits
Broker1
Connections count
Depth
Consumers
Producers
Queue://foo.1
Depth
Consumers
Producers
Queue://foo.2
Depth
Consumers
Producers
Queue://foo.3
Broker2
Connections count
Depth
Consumers
Producers
Queue://bar.1
Depth
Consumers
Producers
Queue://bar.2
Depth
Consumers
Producers
Queue://bar.3
34. RED HAT | Fabric8 Rocks!34
Destination Sharding: Internal Rules
• Fired when state
changes
• Operates over the
internal Model
• Rules fired in priority
order
• Only one rule fired
per state change
Scale Up
• Connection limits
exceeded OR
• Destination Limits
Exceeded AND
• NO spare capacity
Broker
Control
Scale
Down
• At least ONE
broker AND
• Total load across
all brokers less
than 50%
Distribute
Load
• Broker limits are
Exceeded AND
• Spare capacity
Ask to move clients
and destinations from
most loaded to least
loaded
Distribute clients and
destinations off least
loaded and remove
broker
Request a new Broker
Broker Control is
done via
Kubernetes
35. RED HAT | Fabric8 Rocks!35
ActiveMQ hates
unexpected
Acks…
36. RED HAT | Fabric8 Rocks!36
Fabric8MQ has to
1. Work out which destinations to migrate
2. Stop dispatching to consumers
3. Wait until the all in flight messages are acked
4. Do the migration
5. Update the internal destination map
6. Then resume processing
37. RED HAT | Fabric8 Rocks!37
Kubernetes
• Created by Google from
experience with GCE
• Lightweight, simple and
accessible orchestration
system for Docker
containers
• Schedules onto nodes in a
compute cluster and
actively manages
workloads to ensure state
is “correct”
• Provides easy
management and
Discovery
Kubernetes
Master
Node Node Node
User containers
Scheduled and packed dynamically onto nodes
38. RED HAT | Fabric8 Rocks!38
Kubernetes Model
• Pods – collection of one or more
Docker containers – the minimum
deployment unit in Kubernetes
• Replication Controllers – stored
on Kubernetes Master, they
determine how many replicas of
Pods should be running
• Service – abstraction that defines a
logical set of pods, and defines a
way of exposing their ports on a
unique IP address
• Namespaces – Pods, Services,
Replication Controllers, Label
Selector – all exist within a defined
Namespace. This allows for multiple
environments to be supported by
the same compute cloud – or
multitenancy
Kubernetes
Master
Node
Container
PodContainer
Pod
Node
Container
PodContainer
Pod
Replication
Controller
Fabric8-MQ-Service
39. RED HAT | Fabric8 Rocks!39
Fabric8 MQ Broker Control:
• Fabric8 MQ controls a
headless Replication
Controller to spin up and
down ActiveMQ Brokers
• Monitors the state of
running ActiveMQ
brokers via Jolokia – and
fires changes to the
internal rules engine.
• Communicates with the
Replication Controller to
spin up – or delete Pods
containing ActiveMQ
Brokers
Node
Pod
ActiveMQ
Broker
AMQ
Replication
Controller
Node
Pod
ActiveMQ
Broker
Node
Pod
ActiveMQ
Broker
40. RED HAT | Fabric8 Rocks!40
Fabric8 MQ – not a message broker – but a
scalable messaging system
Many concurrent
connections, one out
Connections
Vert.x
Core
Embedded Camel,
Integration with APIMan
OpenWire,
STOMP
MQTT
AMQP
WebSockets – all done
asynchronously
Scaling Connections
NOT a problem
Destination
Sharding
41. RED HAT | Fabric8 Rocks!41
Fabric8 MQ Independently scalable:
Node
Pod
ActiveMQ
Broker
AMQ
Replication
Controller
Node
Pod
ActiveMQ
Broker
Node
Pod
ActiveMQ
Broker
Fabric8MQ
Replication
Controller
Vert.x
Vert.x
Vert.x
Multiplexer
Multiplexer
Multiplexer
Fabric8MQ
Vert.x
Vert.x
Vert.x
Multiplexer
Multiplexer
Multiplexer
Fabric8MQ
Vert.x
Vert.x
Vert.x
Multiplexer
Multiplexer
Multiplexer
Fabric8MQ
43. RED HAT | Fabric8 Rocks!43
What I’m gonna try and attempt to do ...
Fabric8MQ
MQTT
Device
MQTT
DeviceMQTT
DeviceMQTT
Device
MQTT
DeviceMQTT
Device
MQTT
DeviceMQTT
DeviceMQTT
Device
44. RED HAT | Fabric8 Rocks!44
Destination Sharding: Internal Rules
Limits are set low:
5 Destinations per
Broker
Scale Up
• Connection limits
exceeded OR
• Destination Limits
Exceeded AND
• NO spare capacity
Broker
Control
Scale
Down
• At least ONE
broker AND
• Total load across
all brokers less
than 50%
Distribute
Load
• Broker limits are
Exceeded AND
• Spare capacity
Ask to move clients
and destinations from
most loaded to least
loaded
Distribute clients and
destinations off least
loaded and remove
broker
Request a new Broker
Broker Control is
done via
Kubernetes
45. RED HAT | Fabric8 Rocks!45
Client code
final String host =
System.getenv("FABRIC8MQ_SERVICE_HOST");
final String portStr =
System.getenv("FABRIC8MQ_SERVICE_PORT");
Kubernetes injects
services as Environment
variables
46. RED HAT | Fabric8 Rocks!46
Questions
and
Discussion