DevNexus 2020 - Jakarta Messaging 3.x, Redefining JMS

•

2 gefällt mir•88 views

The document discusses plans for Jakarta Messaging 3.x, which will serve as the basis for the JMS API in Jakarta EE 9 and beyond. It outlines the timeline of JMS specifications and their inclusion in Java EE and Jakarta EE. Ideas for Jakarta Messaging 3.x include incorporating unreleased features from JMS 2.1, improving support for CDI, adding property conversion and JSON-B message support, and developing a MessagingClient similar to MicroProfile Rest Client. The presentation encourages involvement in the Jakarta Messaging and sample code projects on GitHub.

Technologie

@dblevins @tomitribe
David Blevins
Java Message Service
Jakarta Messaging 3.x

@dblevins @tomitribe
AGENDA
● Death of JMS 2.1
● Jakarta EE 9 / Jakarta Messaging 3.0
● Possible directions for Messaging 3.x
● Get Involved

@dblevins @tomitribe
JMS Timeline
May 2013
JAVA EE 7
JMS 2.0
JCA 1.6
Sep 2019
JAKARTA EE 8
JMS 2.0
JCA 1.7
Aug 2017
JAVA EE 8
JMS 2.0
JCA 1.7
JMS 2.1
Proposed
Sep 2013
JAVA EE 7
JMS 2.1
Withdrawn
Nov 2016
JAVA EE 7

@dblevins @tomitribe
JMS Timeline
Sep 2020
JAKARTA EE 9
3.0
javax > jakarta
2021
JAKARTA EE 10
3.1
new features
2021?
3.2
new features
….
3.3
new features

@dblevins @tomitribe
JMS 2.0 in a Nutshell
The 2 minute perspective

@dblevins @tomitribe
JMS 2.0 in a Nutshell
The 5 minute perspective

@dblevins @tomitribe
JMS 2.0
Programmatic
New Builders
JMSContext
JMSProducer
JMSConsumer
Some increased CDI support
JMS 2.1
Declarative
New Annotations
@QueueListener
@TopicListener
@MessageSelector
Greater CDI support

@dblevins @tomitribe
Jakarta Messaging 3.x Ideas
● JMS 2.1
● CDI Consumers
● Property Conversion
● CDI Stereotypes #1 - In API
● CDI Stereotypes #2 - In your code
● JSON-B Messages
● MessagingClient

@dblevins @tomitribe
Jakarta Messaging 3.x Ideas
1. JMS 2.1
2. CDI Consumers
3. Property Conversion
4. CDI Stereotypes #1 - In API
5. CDI Stereotypes #2 - In your code
6. JSON-B Messages
7. MessagingClient

@dblevins @tomitribe
JMS 2.1 removed from Java EE 8
Now the basis of Jakarta Messaging 3.0

@dblevins @tomitribe
The Problem With MDBs
JMS 2.0 and before

@dblevins @tomitribe
LEARNING FROM JAX-RS
● No interfaces
● Fluid method signatures
● Annotation-based conﬁguration
● Strongly Typed
● Self-documenting
● Targeted: annotations can be on
○ Class, Method, Parameter, Field

@dblevins @tomitribe
Jakarta Messaging 3.0 Ideas
● JMS 2.1
● CDI Consumers
● Property Conversion
● CDI Stereotypes #1 - In API
● CDI Stereotypes #2 - In your code
● JSON-B Messages
● MessagingClient

@dblevins @tomitribe
Still not perfect...

@dblevins @tomitribe
MicroProﬁle REST Client
2 Minute Overview

@dblevins @tomitribe
Given this JAX-RS Resource

@dblevins @tomitribe
MicroProﬁle Rest Client
● JMS 2.1
● CDI Consumers
● Property Conversion
● CDI Stereotypes #1 - In API
● CDI Stereotypes #2 - In your code
● JSON-B Messages
● MessagingClient

@dblevins @tomitribe
Jakarta Messaging 3.x - All Together
● JMS 2.1
● CDI Consumers
● Property Conversion
● CDI Stereotypes #1 - In API
● CDI Stereotypes #2 - In your code
● JSON-B Messages
● MessagingClient

@dblevins @tomitribe
TO THIS Jakarta Messaging 3.x

@dblevins @tomitribe
Get Involved
Jakarta Messaging
- https://github.com/eclipse-ee4j/jms-api
- https://accounts.eclipse.org/mailing-list/jms-dev
This Code
- https://github.com/tomitribe/jms-proposals

@dblevins @tomitribe
Thank you
Contact us @TOMITRIBE

Weitere ähnliche Inhalte

Ähnlich wie DevNexus 2020 - Jakarta Messaging 3.x, Redefining JMS

Creando microservicios con Java y Microprofile - Nicaragua JUG

César Hernández

Hybrid Cloud Application Development without vendor lockin

EmilyJiang23

DDD in Pixel Federation volume 2

Pixel Federation

Welcome to React & Flux !

Ritesh Kumar

CDI 2.0 is coming

Antoine Sabot-Durand

Jonas Barochia_Java Developer

Jonas Barochia

By Daniel Ehrenberg. Have you ever found yourself with a disappointing rounding error due to how Numb ers work, or using awkward workarounds to avoid thinking about decimals? It's a shame that JavaScript chose binary floating point as its basic numeric type when it causes all of these problems. What can we do about it? (c) Node.TLV 2020 https://www.nodetlv.com/ https://www.youtube.com/watch?v=G3Q4vWf8Peo

BigDecimal: Avoid rounding errors on decimals in JavaScript (Node.TLV 2020)

Igalia

Jakarta EE and MicroProfile - EclipseCon 2020

Josh Juneau

Understanding the Performance Impact of Generated JavaScript.pptx

Shana Matthews

This presentation was delivered at SUGCON ANZ 2022 by Sean Holmesby and James Barrow from the Sitecore Professional Services team. 'So you're on XP, and it's not performing the way you want it to. What can you do about it? In this session we'll go over the common pitfalls and issues that the Sitecore Professional Services team have come across in XP implementations, and how to fix them. Poor site performance? Struggling xDB analytics? Log error messages that don't make any sense? We've seen it all.... now let's help you fix them up.'

Professional Services Insights into Improving Sitecore XP

SeanHolmesby1

State of GeoServer provides an update on our community and reviews the new and noteworthy features for the Project. The community keeps an aggressive six month release cycle with GeoServer 2.11 and 2.12 being released this year. Each releases bring together exciting new features. This year a lot of work has been done on startup times, large catalogs, REST configuration upgrades, styling languages, styling interface, security,just to name a few. We will also take a look at community research into satellite imagery search and delivery, multi-resolution raster support and more. Attend this talk for a cheerful update on what is happening with this popular OSGeo project. Whether you are an expert user, a developer, or simply curious what these projects can do for you, this talk is for you.

State of GeoServer 2.12

GeoSolutions

Resume

Abhijit Ghosh

At Greentube business is booming. However, for the last few years they have faced increasing problems scaling their product and headcount. Like many orgs, Greentube has a complicated SQL Server backend which supports many apps. In 2016, despite best efforts, the database was not in source control, deployments were manual and the production database schemas were out of sync. The core database team was struggling to keep up with the business’s rapid growth because so much time was wasted firefighting unexpected issues. The business recognised that the database was a bottleneck on the company’s growth. And that was an expensive problem. Come and learn from Manoj Lona, the DB Team Lead at Greentube, and Alex Yates, a DLM Consultant from DLM Consultants, about how last year they made the necessary technical and organisational changes that today enable GreenTube to deploy their database at the click of a button - allowing them to scale their product and headcount to meet business demand.

Adopting DLM at Greentube

Alex Yates

Microsoft Exchange Server is an email solution widely deployed within government and enterprises, and it is an integral part of both their daily operations and security. Needless to say, vulnerabilities in Exchange have long been the Holy Grail for attackers, hence our security research on Exchange. Surprisingly, we've found not only critical vulnerabilities such as ProxyLogon, but a whole new attack surface of Exchange. This new attack surface is based on a significant change in Exchange Server 2013, where the fundamental protocol handler, Client Access Service (CAS), splits into frontend and backend. In this fundamental change of architecture, quite an amount of design debt was incurred, and, even worse, it introduced inconsistencies between contexts, leading us to discover this new attack surface. To unveil the beauty of this attack surface and our novel exploitation, we'll start by analyzing this architecture, followed by 7 vulnerabilities that consist of server-side bugs, client-side bugs, and crypto bugs found via this attack surface. In the end, these vulnerabilities are chained into 3 attack vectors that shine in different attack scenarios: ProxyLogon, ProxyShell, and ProxyOracle. These attack vectors enable any unauthenticated attacker to uncover plaintext passwords and even execute arbitrary code on Microsoft Exchange Servers through port 443, which is exposed to the Internet by ~400K Exchange Servers. This attack surface has its unparalleled impact for a reason: security researchers tend to find vulnerabilities from a certain perspective, such as digging for memory bugs, injections, or logic flaws, but we took a different approach by looking at Exchange from a high-level architectural view and captured this architecture-level attack surface, which yielded multiple vulnerabilities. We hope this brings a new paradigm to vulnerability research and inspires more security researchers to look into Exchange Server. Last but not least, we'll provide hardening actions to mitigate such types of 0days in Exchange.

[CB21] ProxyLogon is Just the Tip of the Iceberg, A New Attack Surface on Mic...

CODE BLUE

Sukumar Resume

Sukumar Reddy

Slides by Matt Brasier, Principal Consultant at C2B2, from the Hands on Lab delivered at the JavaOne 2014 conference. ABOUT HOL: This session will demonstrate the depth and breadth of the information available via the JMX API. We will tools that come with the JDK to peer deep into the workings of the JVM and understand how to identify and solve common performance bottlenecks or other problems. Attendees will get examples of using tools like VisualVM and Jstat to interrogate the JVM, and how to interpret the data returned, and learn how to add JMX instrumentation to their own applications and expose this to monitoring tools. This will be a session that allows attendees to understand the power available to them in some of the overlooked core JVM features The session will use a combination of slides and examples that the attendees can code-along with on their own laptops, and will focus on what JMX is, how it works, and also how you can expose your own application MBeans and use these to monitor the application. In my work as a Java performance consultant, I have found that JMX and the basic JVM tooling that uses it, is not understood by developers, so this session is about raising awareness of these tools and allowing developers to get inside the JVM and their application to understand how it works (and write better code). In my experience, once developers understand the power of JMX and VisualVM, they find it very interesting, and often the best way to demonstrate it is by allowing people to work with it. The fact that the base JDK is all that is required to demonstrate this means that there are few pre-requisites for this session, and because it is based on a low level technology, it is of interest to people working on all aspects of Java. I think this could make popular talk which will help developers understand the magic and power behind the Java Virtual Machine.

Through the JMX Window

C2B2 Consulting

Dive deep into the world of CAD-GIS integration with our expert-led webinar. Discover how to seamlessly transfer data between Bentley MicroStation and leading GIS platforms, such as Esri ArcGIS. This session goes beyond mere CAD/GIS conversion, showcasing techniques to precisely transform MicroStation elements including cells, text, lines, and symbology. We’ll walk you through tags versus item types, and understanding how to leverage both. You’ll also learn how to reproject to any coordinate system. Finally, explore cutting-edge automated methods for managing database links, and delve into innovative strategies for enabling self-serve data collection and validation services. Join us to overcome the common hurdles in CAD and GIS integration and enhance the efficiency of your workflows. This session is perfect for professionals, both new to FME and seasoned users, seeking to streamline their processes and leverage the full potential of their CAD and GIS systems.

Mastering MicroStation DGN: How to Integrate CAD and GIS

Safe Software

State of GeoServer provides an update on our community and reviews the new and noteworthy features for the Project. The community has a lot to cover in 2.12 and the recently released 2.13. Each release provides exciting new features. This talk covers our work on supporting Java 9 and diverse improvements across GeoServer. Attend this talk for a cheerful update on what is happening with this popular OSGeo project. Whether you are an expert user, a developer, or simply curious what GeoServer can do for you.

State of GeoServer 2.13

Jody Garnett

In this talk, we will delve into the complexities of managing data in enterprise Java applications. Effective data management is crucial for maintaining the integrity, availability, and security of enterprise systems. Attendees will gain a deep understanding of various aspects related to data management, including data modeling, persistence frameworks, caching strategies, scalability, and data synchronization. Through real-world examples and best practices, this session aims to equip developers with the knowledge and tools necessary to efficiently handle data in their Java applications.

Managing Data in Jakarta EE Applications

Buhake Sindi

The days of EJB’s being the center of the Java EE universe are coming to an end. CDI is increasingly becoming the de facto component framework, due to its flexibility and lack of legacy. Starting in Java EE 7 and continuing in 8, the Java EE platform is migrating to enable all of EJB’s best features to be usable in the CDI world. In this session, you’ll learn implementation-level details on how they relate to each other, where we are in the EJB/CDI alignment story, what trade-offs you might need to make, and what you have to gain from making the transition. You will walk out with runnable examples and vendor-level insights. This is the perfect session for heavy EJB users looking to keep up with Java EE’s transition to CDI.

2015 JavaOne EJB/CDI Alignment

David Blevins

Ähnlich wie DevNexus 2020 - Jakarta Messaging 3.x, Redefining JMS (20)

Creando microservicios con Java y Microprofile - Nicaragua JUG

Hybrid Cloud Application Development without vendor lockin

DDD in Pixel Federation volume 2

Welcome to React & Flux !

CDI 2.0 is coming

Jonas Barochia_Java Developer

BigDecimal: Avoid rounding errors on decimals in JavaScript (Node.TLV 2020)

Jakarta EE and MicroProfile - EclipseCon 2020

Understanding the Performance Impact of Generated JavaScript.pptx

Professional Services Insights into Improving Sitecore XP

State of GeoServer 2.12

Resume

Adopting DLM at Greentube

[CB21] ProxyLogon is Just the Tip of the Iceberg, A New Attack Surface on Mic...

Sukumar Resume

Through the JMX Window

Mastering MicroStation DGN: How to Integrate CAD and GIS

State of GeoServer 2.13

Managing Data in Jakarta EE Applications

2015 JavaOne EJB/CDI Alignment

Mehr von David Blevins

In this presentation we'll deep dive into MicroProfile JWT, which offers a clean Java API and standard configuration for consuming JWTs in Java Microservices. Code and demo focused, we'll see a complete MicroProfile JWT, TomEE and AngularJS app that issues JWTs with custom backend-data, performs server-side verification and injection of claims, and client-side login and refresh. All code in Github, you'll leave ready to bootstrap your next truly secure full-stack project.

2019 JJUG CCC Stateless Microservice Security with MicroProfile JWT

David Blevins

The learning curve for security is severe and unforgiving. Specifications promise infinite flexibility, habitually give old concepts new names, are riddled with extensions, and almost seem designed to deliberately confuse. For a back-end REST developer, choking all this down for the first time is mission impossible. With an aggressive distaste for fancy terminology, this session delves into OAuth 2.0 as it pertains to REST and shows how it falls into two camps: stateful and stateless. We then detail a competing Amazon-style approach called HTTP Signatures, ideal for B2B scenarios and similar to what is use to secure all Amazon AWS API calls. Each approach will be explored analyzing the architectural differences, with a heavy focus on the wire, showing actual HTTP messages and enough detail to have you thinking, "I could write this myself." As a bonus at the end, well peak into a new IETF Internet Draft launched this year that combines JWT and HTTP Signatures into the perfect two-factor system that could provide a one-stop shop for business as well as mobile REST scenarios. Come to this session if you want to go from novice to expert with a bit of humor, a big picture perspective and wire-level detail.

2018 jPrime Deconstructing and Evolving REST Security

David Blevins

2018 Denver JUG Deconstructing and Evolving REST Security

David Blevins

2018 Boulder JUG Deconstructing and Evolving REST Security

David Blevins

2018 JavaLand Deconstructing and Evolving REST Security

David Blevins

The learning curve for security is severe and unforgiving. Specifications promise infinite flexibility, habitually give old concepts new names, offer endless extensions, and almost seem designed to deliberately confuse. With an eye on architecturual impact, actual HTTP messages, and aggressive distaste for fancy terminology, this session delves into OAuth 2.0 as it pertains to REST and shows how it falls into two camps: stateful and stateless. It then explores a competing Amazon-style approach called HTTP Signatures, ideal for B2B APIs. Finally, it discusses a new internet draft launched this year that combines them both into the perfect two-factor system that could provide a one-stop shop for business as well as mobile REST scenarios.

2018 IterateConf Deconstructing and Evolving REST Security

David Blevins

2018 SDJUG Deconstructing and Evolving REST Security

David Blevins

2017 Devoxx MA Deconstructing and Evolving REST Security

David Blevins

2017 JavaOne Deconstructing and Evolving REST Security

David Blevins

2017 JCP EC: Configuration JSR

David Blevins

2017 dev nexus_deconstructing_rest_security

David Blevins

2016 JavaOne Deconstructing REST Security

David Blevins

Having made its Java EE 6 Web Profile certification debut at JavaOne 2011 and having won a JavaOne Rock Star award in 2012, Apache TomEE combines the simplicity of Tomcat with the power of Java EE. This updated presentation traverses the world of TomEE and shows how Tomcat applications leveraging Java EE technologies can become simpler and lighter with a Java EE–certified solution built right on Tomcat. The first part jumps right into action and gives a coding tour of TomEE, including quickly bootstrapping projects, doing proper testing with Arquillian, and setting up environments. The second part gives insight into how TomEE was created and explores the budding TomEE ecosystem of tools, platforms, and the latest community advancements.

JavaOne 2013 - Apache TomEE, Java EE Web Profile {and more} on Tomcat

David Blevins

2011 JavaOne EJB with Meta Annotations

David Blevins

2011 JavaOne Apache TomEE Java EE 6 Web Profile

David Blevins

2011 JavaOne Fun with EJB 3.1 and OpenEJB

David Blevins

Mehr von David Blevins (16)

2019 JJUG CCC Stateless Microservice Security with MicroProfile JWT

2018 jPrime Deconstructing and Evolving REST Security

2018 Denver JUG Deconstructing and Evolving REST Security

2018 Boulder JUG Deconstructing and Evolving REST Security

2018 JavaLand Deconstructing and Evolving REST Security

2018 IterateConf Deconstructing and Evolving REST Security

2018 SDJUG Deconstructing and Evolving REST Security

2017 Devoxx MA Deconstructing and Evolving REST Security

2017 JavaOne Deconstructing and Evolving REST Security

2017 JCP EC: Configuration JSR

2017 dev nexus_deconstructing_rest_security

2016 JavaOne Deconstructing REST Security

JavaOne 2013 - Apache TomEE, Java EE Web Profile {and more} on Tomcat

2011 JavaOne EJB with Meta Annotations

2011 JavaOne Apache TomEE Java EE 6 Web Profile

2011 JavaOne Fun with EJB 3.1 and OpenEJB

Kürzlich hochgeladen

This our Twelfth semiannual report on the global Cryptocurrency mining industry. Bitcoin is the world’s largest special purpose supercomputer. And it is globally decentralized. Millions of nodes all run the same open-source code to secure the Bitcoin network, create value, and put new transactions onto the distributed ledger. The latest Top500 list has just been announced at the ISC 2024 conference in Hamburg, and once again the Frontier supercomputer with 1.2 Exaflops peak performance is number one on the list. If assigned to SHA-256 hashing, Frontier would provide only the equivalent hash rate of about three cabinets of the latest high-end Bitcoin mining systems, costing less than 0.1% of Frontier’s cost. Michael Saylor, Chairman of MicroStrategy, has pointed out that GPUs are two orders of magnitude slower than the 5-nanometer technology of custom ASICs used for Bitcoin mining today. He makes the point that the Bitcoin network is unassailable by all of the hyperscale computing resources combined in AWS, Google, and Microsoft Azure cloud data centers today.

TopCryptoSupers 12thReport OrionX May2024

Stephen Perrenod

Join me in this session where I'll share our journey of building a fully serverless application that flawlessly managed check-ins for an event with a staggering 80 thousand registrations. We'll dive into three key strategies that made this possible. Firstly, by harnessing DynamoDB global tables, we ensured global service availability and data replication across regions, boosting performance and disaster recovery. Next, we'll explore how we seamlessly integrated real-time updates into the app using Appsync subscriptions, making the experience dynamic and engaging for users. Finally, I'll discuss how provisioned concurrency not only improved performance but also kept costs in check, highlighting the cost-effectiveness of serverless architectures. Through these strategies and the inherent scalability of serverless technology, our application effortlessly handled massive user loads without manual intervention. This session is a real world example to the power and efficiency of modern cloud-based solutions in enabling seamless scalability and robust performance with Serverless

How we scaled to 80K users by doing nothing!.pdf

Srushith Repakula

Choosing the Right FDO Deployment Model for Your Application _ Geoffrey at In...

FIDO Alliance

Delivered by Sreenath Gopalakrishna, Director of Software Engineering at BT, and Dr Jim Webber, Chief Scientist at Neo4j, at Gartner Data & Analytics Summit London 2024 this presentation examines how knowledge graphs and GenAI combine in real-world solutions. BT Group has used the Neo4j Graph Database to enable impressive digital transformation programs over the last 6 years. By re-imagining their operational support systems to adopt self-serve and data lead principles they have substantially reduced the number of applications and complexity of their operations. The result has been a substantial reduction in risk and costs while improving time to value, innovation, and process automation. Future innovation plans include the exploration of uses of EKG + Generative AI.

BT & Neo4j _ How Knowledge Graphs help BT deliver Digital Transformation.pptx

Neo4j

AI mind or machine power point presentation

yogeshlabana357357

Syngulon’s technology expands the capacity for selection of microorganisms. The ability to select individual microbes with a behavior of interest is essential, whether for simple cloning at the bench, or for industry-scale production. Synthetic biology uses the concept of “bioengineering” to improve or modify existing genetic systems to create microbes with desired behaviors, and Syngulon uses this approach to develop its selection technologies. This selection technology is based on bacteriocins, ribosomally-produced peptides naturally made by most bacteria to kill competitive microbial species. These bacteriocins can have a limited or wide target range against other microbial species. This technology offers advantageous over antibiotic selection for several reasons: it avoids the use of antibiotics in the first place, helping to reduce the spread of antibiotic resistant microbes. The technology also increases product yield; as bacteriocins are generally smaller peptides, they do not impose a heavy metabolic burden on the producing cell. They can have a wide target specificity, helping to avoid genetic drift. Finally, our system is 100% plasmid-based (e.g. without chromosomal mutations), making it applicable for use in any E. coli strains.

Syngulon - Selection technology May 2024.pdf

Syngulon

This talk focuses on the practical aspects of integrating various telephony systems with Salesforce, drawing on examples from implementations in the Czech scene. It aims to inform attendees about the spectrum of telephony solutions available, from small to large scale, and their compatibility with Salesforce. The presentation will highlight key considerations for selecting a telephony provider that integrates smoothly with Salesforce, including important questions to support the decision-making process. It will also discuss methods for integrating existing telephony systems with Salesforce, aimed at companies contemplating or in the process of adopting this CRM platform. The discussion is designed to provide a straightforward overview of the steps and considerations involved in telephony and Salesforce integration, with an emphasis on functionality, compatibility, and the practical experiences of Czech companies.

Integrating Telephony Systems with Salesforce: Insights and Considerations, B...

CzechDreamin

Secure Zero Touch enabled Edge compute with Dell NativeEdge via FDO _ Brad at...

FIDO Alliance

Overview of Hyperledger Foundation

Hyperleger Tokyo Meetup

Are you wondering why everyone is talking about the Flutterwave scandal? You’re not alone! It’s been in the news a lot. We’re going to tell you all about the Flutterwave Scandal in a way that’s easy to get. Keep reading, because we’re going to share the whole story with you. The company Flutterwave is headquartered in San Francisco, California, United States. In 2016, Iyinoluwa Aboyeji, Olugbenga Agboola, and Adeleke Adekoya established Flutterwave. It offers a payment infrastructure to international merchants and payment service providers throughout Africa. The company operates in various African countries including Nigeria, Kenya, Uganda, Ghana, South Africa, and others. They focus on digital payments, helping businesses accept and process payments on various channels like the web, mobile, ATM, and POS. Recently, they’ve been in the news due to allegations of misconduct within the company, which has affected their reputation and value. Flutterwave is an essential player in the African fintech landscape, aiming to drive growth for banks and businesses through digital payment solutions. The Flutterwave scandal involves allegations of misconduct and inappropriate behaviour towards female employees by the company’s co-founder and CEO, Olugbenga Agboola. Reports have surfaced from both current and former employees about bullying, intimidation, and sexual harassment at work. The allegations of inappropriate behaviour towards female employees at Flutterwave, specifically involving the CEO Olugbenga Agboola, were brought to public attention in April 2022.This was when Clara Wanjiku Odero, an ex-employee and current CEO of Credrails, published a Medium post and a series of tweets on April 4, 2022, accusing Flutterwave and Agboola of bullying. These allegations were part of a broader range of misconduct claims that surfaced around the same time The reasons behind the scandal are rooted in accusations of unethical behavior within the company. The allegations suggest a workplace culture that allowed for misconduct and failed to protect employees from harassment and intimidation. Specifically, the Flutterwave scandal refers to the series of events where the CEO was accused of engaging in improper conduct with female colleagues. This led to a broader investigation into the company’s practices and raised serious concerns about the fintech’s corporate governance. The scandal had significant repercussions, including a drop in the company’s stock price and a loss of trust among customers and partners. The trust that customers and investors had in Flutterwave was greatly damaged. People started to doubt the company’s integrity and whether their money and personal information were safe. Market Impact The scandal shook the entire fintech market. Flutterwave’s competitors saw this as an opportunity and started to attract customers who were leaving Flutterwave.

Breaking Down the Flutterwave Scandal What You Need to Know.pdf

UK Journal

Microsoft CSP Briefing Pre-Engagement - Questionnaire

Exakis Nelite

Where to Learn More About FDO _ Richard at FIDO Alliance.pdf

FIDO Alliance

Delivered by Michael Down at Gartner Data & Analytics Summit London 2024 - Your enemies use GenAI too: Staying ahead of fraud with Neo4j. Fraudsters exploit the latest technologies like generative AI to stay undetected. Static applications can’t adapt quickly enough. Learn why you should build flexible fraud detection apps on Neo4j’s native graph database combined with advanced data science algorithms. Uncover complex fraud patterns in real-time and shut down schemes before they cause damage.

Your enemies use GenAI too - staying ahead of fraud with Neo4j

Neo4j

Portal Kombat : extension du réseau de propagande russe

中央社

FDO for Camera, Sensor and Networking Device – Commercial Solutions from VinC...

FIDO Alliance

The presentation underscores the strategic advantage of treating design systems not just as technical assets but as vital business components that require thoughtful management, robust planning, and strategic alignment with organizational goals. Key Points Covered: - Understanding Design Systems as Business Entities: Conceptualizing design systems as internal business entities can streamline their integration and evolution within a company. - Adoption and Expansion: Elaborating on the importance of tactical adoption across organizational structures, enhancing product suites to cater to user needs and broadening scope to mobile and content authoring solutions. - Data-Driven Development: Utilizing data insights for component development ensures that resources are allocated to create valuable, widely used features. - Financial Modeling for Design Systems: Developing sustainable funding models is crucial for long-term support and success of design systems. - Promoting Internal Buy-In: Stressing on strategies for promoting design systems within the organization to increase engagement and investment from internal stakeholders.

A Business-Centric Approach to Design System Strategy

UXDXConf

TEST BANK For, Information Technology Project Management 9th Edition Kathy Sc...

marcuskenyatta275

ASRock Industrial FDO Solutions in Action for Industrial Edge AI _ Kenny at A...

FIDO Alliance

Linux Foundation Edge _ Overview of FDO Software Components _ Randy at Intel.pdf

FIDO Alliance

Working together SRE & Platform Engineering

Marcus Vechiato

Kürzlich hochgeladen (20)

TopCryptoSupers 12thReport OrionX May2024

How we scaled to 80K users by doing nothing!.pdf

Choosing the Right FDO Deployment Model for Your Application _ Geoffrey at In...

BT & Neo4j _ How Knowledge Graphs help BT deliver Digital Transformation.pptx

AI mind or machine power point presentation

Syngulon - Selection technology May 2024.pdf

Integrating Telephony Systems with Salesforce: Insights and Considerations, B...

Secure Zero Touch enabled Edge compute with Dell NativeEdge via FDO _ Brad at...

Overview of Hyperledger Foundation

Breaking Down the Flutterwave Scandal What You Need to Know.pdf

Microsoft CSP Briefing Pre-Engagement - Questionnaire

Where to Learn More About FDO _ Richard at FIDO Alliance.pdf

Your enemies use GenAI too - staying ahead of fraud with Neo4j

Portal Kombat : extension du réseau de propagande russe

FDO for Camera, Sensor and Networking Device – Commercial Solutions from VinC...

A Business-Centric Approach to Design System Strategy

TEST BANK For, Information Technology Project Management 9th Edition Kathy Sc...

ASRock Industrial FDO Solutions in Action for Industrial Edge AI _ Kenny at A...

Linux Foundation Edge _ Overview of FDO Software Components _ Randy at Intel.pdf

Working together SRE & Platform Engineering

DevNexus 2020 - Jakarta Messaging 3.x, Redefining JMS

1. @dblevins @tomitribe David Blevins Java Message Service Jakarta Messaging 3.x

2. @dblevins @tomitribe AGENDA ● Death of JMS 2.1 ● Jakarta EE 9 / Jakarta Messaging 3.0 ● Possible directions for Messaging 3.x ● Get Involved

3. @dblevins @tomitribe JMS Timeline May 2013 JAVA EE 7 JMS 2.0 JCA 1.6 Sep 2019 JAKARTA EE 8 JMS 2.0 JCA 1.7 Aug 2017 JAVA EE 8 JMS 2.0 JCA 1.7 JMS 2.1 Proposed Sep 2013 JAVA EE 7 JMS 2.1 Withdrawn Nov 2016 JAVA EE 7

4. @dblevins @tomitribe JMS Timeline Sep 2020 JAKARTA EE 9 3.0 javax > jakarta 2021 JAKARTA EE 10 3.1 new features 2021? 3.2 new features …. 3.3 new features

5. @dblevins @tomitribe JMS Timeline Sep 2020 JAKARTA EE 9 3.0 javax > jakarta 2021 JAKARTA EE 10 3.1 new features 2021? 3.2 new features …. 3.3 new features

6. @dblevins @tomitribe JMS 2.0 in a Nutshell The 2 minute perspective

7. @dblevins @tomitribe JMS 1.1

8. @dblevins @tomitribe JMS 2.0

9. @dblevins @tomitribe BUILDER API

10. @dblevins @tomitribe Text Message

11. @dblevins @tomitribe JMS 2.0 in a Nutshell The 5 minute perspective

12. @dblevins @tomitribe JMS 2.0 Programmatic New Builders JMSContext JMSProducer JMSConsumer Some increased CDI support JMS 2.1 Declarative New Annotations @QueueListener @TopicListener @MessageSelector Greater CDI support

13. @dblevins @tomitribe Jakarta Messaging 3.x Ideas ● JMS 2.1 ● CDI Consumers ● Property Conversion ● CDI Stereotypes #1 - In API ● CDI Stereotypes #2 - In your code ● JSON-B Messages ● MessagingClient

14. @dblevins @tomitribe Jakarta Messaging 3.x Ideas 1. JMS 2.1 2. CDI Consumers 3. Property Conversion 4. CDI Stereotypes #1 - In API 5. CDI Stereotypes #2 - In your code 6. JSON-B Messages 7. MessagingClient

15. @dblevins @tomitribe JMS 2.0 in a Nutshell The 5 minute perspective

16. @dblevins @tomitribe JMS 2.1 removed from Java EE 8 Now the basis of Jakarta Messaging 3.0

17. @dblevins @tomitribe The Problem With MDBs JMS 2.0 and before

18. @dblevins @tomitribe

19. @dblevins @tomitribe

20. @dblevins @tomitribe

21. @dblevins @tomitribe

22. @dblevins @tomitribe SO 2004….

23. @dblevins @tomitribe LEARNING FROM JAX-RS ● No interfaces ● Fluid method signatures ● Annotation-based conﬁguration ● Strongly Typed ● Self-documenting ● Targeted: annotations can be on ○ Class, Method, Parameter, Field

24. @dblevins @tomitribe OH YEAH

25. @dblevins @tomitribe Jakarta Messaging 3.0 Ideas ● JMS 2.1 ● CDI Consumers ● Property Conversion ● CDI Stereotypes #1 - In API ● CDI Stereotypes #2 - In your code ● JSON-B Messages ● MessagingClient

26. @dblevins @tomitribe Still not perfect...

27. @dblevins @tomitribe Jakarta Messaging 3.x Ideas ● JMS 2.1 ● CDI Consumers ● Property Conversion ● CDI Stereotypes #1 - In API ● CDI Stereotypes #2 - In your code ● JSON-B Messages ● MessagingClient

28. @dblevins @tomitribe Still not perfect...

29. @dblevins @tomitribe Jakarta Messaging 3.x Ideas ● JMS 2.1 ● CDI Consumers ● Property Conversion ● CDI Stereotypes #1 - In API ● CDI Stereotypes #2 - In your code ● JSON-B Messages ● MessagingClient

30. @dblevins @tomitribe Still not perfect...

31. @dblevins @tomitribe Jakarta Messaging 3.x Ideas ● JMS 2.1 ● CDI Consumers ● Property Conversion ● CDI Stereotypes #1 - In API ● CDI Stereotypes #2 - In your code ● JSON-B Messages ● MessagingClient

32. @dblevins @tomitribe Still not perfect...

33. @dblevins @tomitribe Jakarta Messaging 3.x Ideas ● JMS 2.1 ● CDI Consumers ● Property Conversion ● CDI Stereotypes #1 - In API ● CDI Stereotypes #2 - In your code ● JSON-B Messages ● MessagingClient

34. @dblevins @tomitribe Still not perfect...

35. @dblevins @tomitribe Jakarta Messaging 3.x Ideas ● JMS 2.1 ● CDI Consumers ● Property Conversion ● CDI Stereotypes #1 - In API ● CDI Stereotypes #2 - In your code ● JSON-B Messages ● MessagingClient

36. @dblevins @tomitribe Still not perfect...

37. @dblevins @tomitribe Jakarta Messaging 3.x Ideas ● JMS 2.1 ● CDI Consumers ● Property Conversion ● CDI Stereotypes #1 - In API ● CDI Stereotypes #2 - In your code ● JSON-B Messages ● MessagingClient

38. @dblevins @tomitribe MicroProﬁle REST Client 2 Minute Overview

39. @dblevins @tomitribe Given this JAX-RS Resource

40. @dblevins @tomitribe Client Interface

41. @dblevins @tomitribe Client Builder

42. @dblevins @tomitribe MicroProﬁle Rest Client ● JMS 2.1 ● CDI Consumers ● Property Conversion ● CDI Stereotypes #1 - In API ● CDI Stereotypes #2 - In your code ● JSON-B Messages ● MessagingClient

43. @dblevins @tomitribe Jakarta Messaging 3.x - All Together ● JMS 2.1 ● CDI Consumers ● Property Conversion ● CDI Stereotypes #1 - In API ● CDI Stereotypes #2 - In your code ● JSON-B Messages ● MessagingClient

44. @dblevins @tomitribe FROM THIS… JMS 2.1

45. @dblevins @tomitribe FROM THIS… JMS 2.1

46. @dblevins @tomitribe FROM THIS… JMS 2.1

47. @dblevins @tomitribe TO THIS Jakarta Messaging 3.x

48. @dblevins @tomitribe Get Involved Jakarta Messaging - https://github.com/eclipse-ee4j/jms-api - https://accounts.eclipse.org/mailing-list/jms-dev This Code - https://github.com/tomitribe/jms-proposals

49. @dblevins @tomitribe Thank you Contact us @TOMITRIBE

DevNexus 2020 - Jakarta Messaging 3.x, Redefining JMS

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Ähnlich wie DevNexus 2020 - Jakarta Messaging 3.x, Redefining JMS

Ähnlich wie DevNexus 2020 - Jakarta Messaging 3.x, Redefining JMS (20)

Mehr von David Blevins

Mehr von David Blevins (16)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

DevNexus 2020 - Jakarta Messaging 3.x, Redefining JMS