Your enterprise can become truly intelligent
-------------------------------------------
Get there with Red Hat’s JBoss® Enterprise Business Rules Management System (BRMS), a key component of our vision for the intelligent, integrated enterprise. It delivers the power of business rules, complex event processing, and business process management in a single open source distribution—all accessible from a common set of authoring tools.
JBoss Enterprise BRMS supports a broad range of decision-management and process-driven applications with a unique combination of open source technologies:
- jBPM5 business process management
- Drools business rules
- Drools Fusion complex event processing
Build rule, event, and process-driven applications that scale across the enterprise
-------------------------------------------
Discover best practices for constructing BRMS applications that support large numbers of rules operating on big data. We’ll illustrate common use cases with real-world case studies and give you practical tips for estimating computing resource requirements.
Scaling MySQL: Benefits of Automatic Data DistributionScaleBase
In this webinar, we cover how ScaleBase provides transparent data distribution to its clients, overcoming caveats, hiding the complexity involved in data distribution, and making it transparent to the application.
DB2 for z/OS Update Data Warehousing On System ZSurekha Parekh
Abstract:
Data Warehouses delivers the floor in most Business analytics solution. Recent analysis reveals that the demand for near-real-time data, as well as integration between day-to-day business applications increases.
IBM will share insight on today’s business environment and its impact on an IT organization’s ability to deliver a competitive Business Analytics and Data Warehousing strategy. You will learn how DB2 for z/OS combined with other InfoSphere data movement offerings from IBM can help enable information on demand – user demands.
Datamine provides data-intensive information technology solutions & services for Telecoms, Banking & Retail industry. Our offering answers the needs of modern management for analytics, process insight, business & market intelligence.
TeleManagement Forum OSSera Case Study - AIS Thailand Service Manager Present...Mingxia Zhang, Ph.D.
Tuesday, February 7th, 5:30 - 5:50 PM
Using Frameworx in Implementing a Unified Service Management Tool –Improving Organizational Collaboration and Communication
Examining the drivers for developing a Unified Service Management Tool to improve business processes at the service level in the Strategy, Infrastructure, and Product (SIP) area as well as Operations.
Outlining the development of an enterprise-wide Service Management application, which enabled solidification of the Service Development and Management processes in the SIP area and Service Management and Operation processes
Quantifying the benefits in terms of information sharing, process unification/implementation, cost saving and revenue increasing in service management
Them's the Rules - Using a Rules Engine to Wrangle ComplexityMicah Breedlove
With ever-growing software occasionally developers will find themselves amid a befuddlement built on complicated and poorly organized conditional logic. Chaos such as this is nearly unmaintainable, even by the original developer. A rules engine allows you to simplify that logic and provide more self-documenting, maintainable code.
This explores the use case for a Rules Engines and highlights the existing PHP Rules Engine, Ruler.
Talk given to Nashville PHP Meetup 09/09/2014
Scaling MySQL: Benefits of Automatic Data DistributionScaleBase
In this webinar, we cover how ScaleBase provides transparent data distribution to its clients, overcoming caveats, hiding the complexity involved in data distribution, and making it transparent to the application.
DB2 for z/OS Update Data Warehousing On System ZSurekha Parekh
Abstract:
Data Warehouses delivers the floor in most Business analytics solution. Recent analysis reveals that the demand for near-real-time data, as well as integration between day-to-day business applications increases.
IBM will share insight on today’s business environment and its impact on an IT organization’s ability to deliver a competitive Business Analytics and Data Warehousing strategy. You will learn how DB2 for z/OS combined with other InfoSphere data movement offerings from IBM can help enable information on demand – user demands.
Datamine provides data-intensive information technology solutions & services for Telecoms, Banking & Retail industry. Our offering answers the needs of modern management for analytics, process insight, business & market intelligence.
TeleManagement Forum OSSera Case Study - AIS Thailand Service Manager Present...Mingxia Zhang, Ph.D.
Tuesday, February 7th, 5:30 - 5:50 PM
Using Frameworx in Implementing a Unified Service Management Tool –Improving Organizational Collaboration and Communication
Examining the drivers for developing a Unified Service Management Tool to improve business processes at the service level in the Strategy, Infrastructure, and Product (SIP) area as well as Operations.
Outlining the development of an enterprise-wide Service Management application, which enabled solidification of the Service Development and Management processes in the SIP area and Service Management and Operation processes
Quantifying the benefits in terms of information sharing, process unification/implementation, cost saving and revenue increasing in service management
Them's the Rules - Using a Rules Engine to Wrangle ComplexityMicah Breedlove
With ever-growing software occasionally developers will find themselves amid a befuddlement built on complicated and poorly organized conditional logic. Chaos such as this is nearly unmaintainable, even by the original developer. A rules engine allows you to simplify that logic and provide more self-documenting, maintainable code.
This explores the use case for a Rules Engines and highlights the existing PHP Rules Engine, Ruler.
Talk given to Nashville PHP Meetup 09/09/2014
How a major industrial group automated its purchase order processesAlain Bezançon
A major industrial group with 40,000 employees across 90 countries needed to automate complex purchase order processes. Hundreds of business rules managed in a third-party
database dynamically applied at process runtime.
Obey The Rules: Implementing a Rules Engine in FlexRJ Owen
A presentation I gave with Drew McLean at 360|Flex 2010 in San Jose. The presentation covers how to develop a client-side rules engine using Adobe Flex. We discuss rules engine theory and give three sample implementations. I apologize that I cannot upload source files here - please contact us for more information.
Developing Configurable and High Performance Apps in Drools Ajay Mahajan
Rules Engine are being increasingly used in the enterprise applications to write complex business processing tasks in configurable manner without sacrificing performance. This session will focus on sharing experiences of using Open source Drools rules engine to write business logic for some banking applications. The session will also explore ways to write DSLs to make business rules very end user friendly and use of decision tables for users to give rules in excel
JBoss Business Rules Management System (BRMS) PrimerEric D. Schabell
This session will get you started with JBoss BRMS. It will walk you through some of the capabilities, components and basic concepts that one needs to understand to start building process and rule-driven applications. Join us for an hour or two of Business Process Management (BPM) concepts, explanations of how to capture your enterprises logic in business rules and a demonstration or two from real live processes that bring these concepts to life.
Programming the Physical World with Device Shadows and Rules EngineAmazon Web Services
Learn more about how to use AWS IoT's Device Shadows and Rules Engine to build powerful IoT applications. With Device Shadows, you can build applications that interact with your devices by providing always available REST APIs. By taking advantage of AWS IoT's topic-based rules and built-in integrations, you can build IoT applications that gather, process, analyze, and act on data generated by connected devices at global scale, without having to manage any infrastructure.
Business rules are widely used by enterprises in order to apply logic to their constantly growing data sets. There are many business rule management systems (BRMS) that facilitate this process, however they take a long time in order to process large scale datasets. Today, with information volumes measured in terabytes, standalone business rule engines are simply cannot keep up. With the advent of distributed computing technologies, such as Hadoop, performing jobs in parallel has become a much simpler and less stressful task. Many business rules are ?embarrassingly parallel?, which makes them perfect candidates for running in a parallel computing environment. This is due to the property of most rules to rely simply on a single record to execute and enrich that specific record. Even the business rules that do not have this property can be adapted to run in a parallel environment. In this presentation, I will use the Drools BRMS to show how to utilize Hadoop and the MapReduce paradigm in order to scale business rules to massive datasets.
JBoss BRMS sneak peak, the future is now for your Business ProcessesEric D. Schabell
A Business Process Management System (BPMS) offers you the capabilities to better manage and streamline your business processes. JBoss continues expanding its vision in this area by offering a lightweight process engine for executing business processes, combined with the necessary services and tooling to support business processes in their entire life-cycles.
This allows not only developers but also business users to manage your business processes more efficiently. A lot has happened in the BPM area over the last few years, with the introduction of the BPMN 2.0 standard, the increasing interest in more dynamic and adaptive processes, integration with business rules and event processing, case management, etc. In this session, we will show you how JBoss BRMS leverages the jBPM project to tackle these challenge and give you an overview of its most important BPMS features.
CASE STUDY: How SCA Hygiene Leveraged SAP NetWeaver for Global ConsolidationSEEBURGER
When SCA Hygiene, a multinational enterprise who produces personal care and tissue products in over 100 countries, found that they were no longer capable of fulfilling their day-to-day operations it became clear that the outdated technology needed to be replaced in order to better satisfy business demands and position themselves for future market demands.
They turned to SAP to gain greater control and flexibility over their organization and SEEBURGER to enable the communication to their business partners by uniting under a single platform and resulted in streamlined, more efficient operations with a lower Total Cost of Ownership (TCO).
Find out not only what enhancements are coming with the SAP NetWeaver product line, but also how SCA Hygiene is leveraging SAP NetWeaver and SEEBURGER to consolidate their businesses globally and give them better control over their business partner trading processes.
Learn:
• The advancements to the SAP NetWeaver product line and future product roadmap
• How SCA Hygiene leveraged their SAP investment to satisfy all business demands from a single platform
• Learn how to configure a successful global consolidation project or SAP NetWeaver implementation
Description of the ]po[ data-model suitable for report developers and integration engineers. These slides introduce step-by-step into the most important tables and concepts of ]project-open[.
Power Up with Podman - Cloud Native + K8s MeetupEric D. Schabell
Curious about containers beyond Docker? There’s a new generation of containers on the scene, Podman! Supporting secure, rootless containers for Kubernetes microservices, it was designed and built with the cloud in mind. Benefitting from the lessons learned out in the open from Docker, this next generation of containers will quickly become a trusted daily driver in your dev workflow.
Covering what you need to know as an end-user from the UI to the backend, sharing a real world use case leveraging Podman for open source observability workshops https://o11y-workshops.gitlab.io. Paige will share how Podman and the adorable seal mascots Caitlín, Maighréad and Róisín have transformed her local development!
Choose Your Own Adventure - Cloud Native Observability PitfallsEric D. Schabell
Are you looking at your organization's efforts to enter or expand into the cloud native landscape and feeling a bit daunted by the vast expanse of information surrounding cloud native observability? When you're moving so fast with agile practices across your DevOps, SRE's, and platform engineering teams, it's no wonder this can seem a bit confusing. Unfortunately, the choices being made have a great impact on both your business, your budgets, and the ultimate success of your cloud native initiatives. That hasty decision up front leads to big headaches very quickly down the road. In this talk, I'll introduce the problem facing everyone with cloud native observability followed by 3 common mistakes that I'm seeing organizations make and how you can avoid them!
Key takeaways - This session is never the same twice as you the audience / attendees choose from a list of cloud native observability pitfalls that DevOps have to contend with in their daily cloud native lives! Super engaging and fun to tour the challenges that interest you most!
OpenShift Commons Paris - Choose Your Own Observability AdventureEric D. Schabell
Great observability begins with great instrumentation! We know it's hard to decide where to start your observability journey, so we've come up with a perfect introduction to observability workshop collection getting you hands-on with the best open source cloud native observability projects available. Attendees can pick their own cloud native observability learning path (https://o11y-workshops.gitlab.io) in this session from the following workshops:
OpenTelemetry (traces) - Learn how to adopt OpenTelemetry by instrumenting a sample application with spans and metrics. You’ll leave with an understanding of how telemetry travels and be ready to bring OpenTelemetry to your project. The workshop is self-paced and available online, so attendees can continue to explore after the event: https://o11y-workshops.gitlab.io/workshop-opentelemetry
Prometheus (metrics) - During the workshop, you will install Prometheus, collect metrics, and learn how to effectively run it in your observability stack. The workshop is self-paced and available online, so attendees can continue to explore after the event: https://o11y-workshops.gitlab.io/workshop-prometheus
Fluent Bit (pipelines) - This workshop will guide you through the open source project Fluent Bit, what it is, a basic installation, and setting up a first cloud native observability pipeline project. The workshop is self-paced and available online, so attendees can continue to explore after the event: https://o11y-workshops.gitlab.io/workshop-fluentbit
Perses (visualization) - Great observability is impossible without great visualization! Learn how to adopt truly open visualization by installing Perses, exploring the provided tooling, tinkering with its API, and then get your hands dirty building your first dashboard in no time! The workshop is self-paced and available online, so attendees can continue to explore after the event: https://o11y-workshops.gitlab.io/workshop-perses
Checking the pulse of your cloud native architectureEric D. Schabell
The daily choices you make as an engineer when shipping code contributes to the feedback loop. In cloud native environments a surprising amount of data is generated from the application layer down to infrastructure and along the delivery path. Regulatory and compliance pressures force us to store audit and observability data. Understanding the pressures on our engineering teams around the collection, storage, and maintenance of your cloud data can mean the difference between successful teams and burnout. Let us take you on a journey, looking closely at the current state of observability based on a recent research conducted with 500 cloud native engineers and find out what it’s like to be in the trenches.
3 Pitfalls Everyone Should Avoid with Cloud DataEric D. Schabell
The daily hype is all around you. From cloud native, multicloud, to hybrid cloud, this is the path to your digital future. The choices you make as a developer does not preclude the daily work of enhancing your customer's experience and agile delivery of your applications. With all this delivery and infrastructure, there is a lot of data generated when engaging with any cloud experience. Regulatory and compliance pressures force us to store audit and observability data. Understanding the pitfalls around the collection, storage, and maintenance of your cloud data can mean the difference between bankruptcy and success with our cloud native strategy. Let us take you on a journey, looking closely at the decisions you are making as a developer delivering and dealing with monitoring your applications. Join us for an hour of power, where real customer experiences are used to highlight the three top lessons learned as their developers transitioned their data needs into cloud native environments.
Key Takeaways: Attendees to this session will gain insights into the data explosion that is part of the large scale cloud native world. Real customer experiences are used to highlight the three top lessons learned as their developers transitioned their data needs into cloud native environments.
Observability For You and Me with OpenTelemetry (with demo)Eric D. Schabell
Are you interested in dipping your toes in the cloud native observability waters, but as an engineer you are not sure where to get started with tracing problems through your microservices and application landscapes on Kubernetes? Then this is the session for you, where we take you on your first steps in an active open-source project that offers a buffet of languages, challenges, and opportunities for getting started with telemetry data.
The project is called openTelemetry, but before diving into the specifics, we’ll start with de-mystifying key concepts and terms such as observability, telemetry, instrumentation, cardinality, percentile to lay a foundation. After understanding the nuts and bolts of observability and distributed traces, we’ll explore the openTelemetry community; its Special Interest Groups (SIGs), repositories, and how to become not only an end-user, but possibly a contributor.We will wrap up with an overview of the components in this project, such as the Collector, the OpenTelemetry protocol (OTLP), its APIs, and its SDKs.
Attendees will leave with an understanding of key observability concepts, become grounded in distributed tracing terminology, be aware of the components of openTelemetry, and know how to take their first steps to an open-source contribution!
Key Takeaways: Open source, vendor neutral instrumentation is an exciting new reality as the industry standardizes on openTelemetry for observability. OpenTelemetry is on a mission to enable effective observability by making high-quality, portable telemetry ubiquitous. The world of observability and monitoring today has a steep learning curve and in order to achieve ubiquity, the project would benefit from growing our contributor community. (includes demo)
3 Pitfalls Everyone Should Avoid with Cloud Native ObservabilityEric D. Schabell
Are you looking at your organization's efforts to enter or expand into the cloud native landscape and feeling a bit daunted by the vast expanse of information surrounding cloud native observability? When you're moving so fast with agile practices across your DevOps, SRE's, and platform engineering teams, it's no wonder this can seem a bit confusing. Unfortunately, the choices being made have a great impact on both your business, your budgets, and the ultimate success of your cloud native initiatives. That hasty decision up front leads to big headaches very quickly down the road. In this talk, I'll introduce the problem facing everyone with cloud native observability followed by 3 common mistakes that I'm seeing organizations make and how you can avoid them!
Are you interested in dipping your toes in the cloud native observability waters, but as an engineer you are not sure where to get started with tracing your microservices and applications on Kubernetes? Then this is the session for you, where we take you on your first steps in an active open-source project that offers a buffet of opportunities for getting started with telemetry data. The project, openTelemetry (OTEL), is where we start with de-mystifying key concepts and terms such as observability, telemetry, instrumentation to lay a foundation. Then we’ll explore the OTEL community and how to become not only an end-user, but possibly a contributor.We will wrap up with an overview of the components in this project, such as the Collector, the OTEL protocol (OTLP), its APIs, and its SDKs. Attendees will leave with an understanding of key observability concepts in distributed tracing!
Key takeaways: Open source, vendor neutral instrumentation is an exciting new reality as the industry standardizes on openTelemetry for observability. OpenTelemetry is on a mission to enable effective observability by making high-quality, portable telemetry ubiquitous. The world of observability and monitoring today has a steep learning curve and in order to achieve ubiquity, the project would benefit from growing our contributor community.
The CNCF Ambassador program is designed for individuals who are passionate about cloud native technologies and want to contribute to the community. Becoming an ambassador is a great opportunity to enhance your knowledge, gain visibility within the industry, and help drive the adoption of cloud-native technologies. The road to becoming an ambassador might seem intimidating, scary, or just impossible, but it does not have to be. We've put together a roadmap that leads you to the title of CNCF Ambassador. In this session a current ambassador and the community manager share the stage to bring you insights into achieving the title of CNCF Ambassador. Whether you are a developer, student, or seasoned professional, this talk provides attendees with 5 actionable insights needed to take your cloud-native skills to the next level and become a CNCF Ambassador. Join us to learn how you can contribute to the community and advance your career by taking the road to the CNCF Ambassador community.
Cloud Native Bedtime Stories - Terrifying Execs into ActionEric D. Schabell
Anyone embedded in the cloud native teams in any organization can voice their frustrations at not being taken seriously by their executive decision makers. This leads to way too much on-call stress, frustrations, and eventual burnout. With research showing us DevOps spending over 10 hrs a week on issues in their environments, we could all use quick action by our executives when we find ways to fix our cloud native issues. The trick is to tell the tales we accumulate in such a way as to engage, inspire, and effect change in our organizations. This session provides attendees with ample cloud native bedtime stories, tricks that make your tales land within the executive human mind, and actionable insights to head home with immediate results. Join me for a half hour of power where you are empowered to tell better cloud native stories for better executive decision outcomes.
Key takeaways - Attendees to this session will be given a small yet powerful set of examples to help them effectively tell their cloud native observability tales to motivate their executives into action. Humans listen to stories (tales) more than they pay attention to pages of charts, dashboards, and data. Learn how to tell your tales, terrifying and educational, with tips and tricks to engage your executives into believing your need for organization’s observability improvements.
SRECon EU 2023 - Three Phases to Better Observability OutcomesEric D. Schabell
We all want to have better business outcomes for our organizations solutions, such as faster remediation of problems, easier problem detection, greater revenue generation, happier customers, and engineering teams that can remain focused on delivering more business value. The problem with the popular three pillars (metrics, logs, tracing) is that you are talking about technology aspects and not about solutions. It's like talking about the tools in a mechanics toolbox used to make your convertible run again, instead of focusing on the blue smoke coming out of the exhaust, the rising engine temperature, and using that data to quickly remediate the problem by replacing the seals to prevent oil leaking in the engine. Let’s quickly tour the phases that lead to better outcomes and get our focus back on effective observability goals.
Key takeaways - Modern cloud native observability needs three guiding phases to provide better outcomes, not tooling.
Based on article: https://www.schabell.org/2022/09/o11y-guide-cloud-native-observability-needs-phases.html
Are you collecting just about every metric under the sun and the kitchen sink too? Understanding the cost of collecting metrics and the usefulness of those metrics is the only way to scale in a cloud native world. You can’t get away with just collecting everything as you grow. Your observability teams need to make decisions about what to collect, what to drop, what to aggregate, and still be able to alert, triage, remediate, and do their root cause analysis on a daily basis. Gain immediate insights into high cost data (DPPS), when to drop time series data, and how to determine when the value of that data is at its lowest. Session includes a recorded demo video of it in action.
Engaging Your Execs - Telling Great Observability Tales Inspiring ActionEric D. Schabell
Anyone embedded in the cloud native observability teams in any organization can voice their frustrations at not being taken seriously by their executive decision makers. This leads to way too much on-call stress, frustrations, and eventual burnout. With research showing us DevOps spending over 10 hrs a week on issues in their environments, we could all use quick action by our executives when we find ways to fix our cloud native issues. The trick is to tell the tales we accumulate in such a way as to engage, inspire, and effect change in our organizations. This session provides attendees with ample cloud native bedtime stories, tricks that make your tales land within the executive human mind, and actionable insights to head home with immediate results. Join me for a half hour of power where you are empowered to tell better observability stories for better executive decision outcomes.
WTF is SRE - Telling Effective Tales about ProductionEric D. Schabell
Storytelling is as old as time itself…. Since the beginning of humankind, we share our experiences, we teach, we inspire, we relate to stories as told all around us. How can we learn to use this powerful mechanism to tell effective tales about our production environments when dealing with our management teams?
Learn how humans listen to stories (tales) more than they pay attention to pages of charts, dashboards, and data. If you want to learn how to make sure your message lands and how to effectively manage upwards in your organization, this is the session for you. Attendees will depart with a small yet powerful set of actionable examples that almost ensure your stories will capture your management's attention. One thing is certain, stories are being told, but what are your production stories and how can you become adept at telling them?
Are you collecting just about every metric under the sun and the kitchen sink too? Understanding the cost of collecting metrics and the usefulness of those metrics is the only way to scale in a cloud native world. You can’t get away with just collecting everything as you grow. Your observability teams need to make decisions about what to collect, what to drop, what to aggregate, and still be able to alert, triage, remediate, and do their root cause analysis on a daily basis. Gain immediate insights into high cost data (DPPS), when to drop time series data, and how to determine when the value of that data is at its lowest. Session includes a recorded demo video of it in action.
Are you interested in dipping your toes in the cloud native observability waters, but as an engineer you are not sure where to get started with tracing problems through your microservices and application landscapes on Kubernetes? Then this is the session for you, where we take you on your first steps in an active open-source project that offers a buffet of languages, challenges, and opportunities for getting started with telemetry data.
The project is called openTelemetry, but before diving into the specifics, we’ll start with de-mystifying key concepts and terms such as observability, telemetry, instrumentation, cardinality, percentile to lay a foundation. After understanding the nuts and bolts of observability and distributed traces, we’ll explore the openTelemetry community; its Special Interest Groups (SIGs), repositories, and how to become not only an end-user, but possibly a contributor.We will wrap up with an overview of the components in this project, such as the Collector, the OpenTelemetry protocol (OTLP), its APIs, and its SDKs.
Attendees will leave with an understanding of key observability concepts, become grounded in distributed tracing terminology, be aware of the components of openTelemetry, and know how to take their first steps to an open-source contribution!
Key Takeaways: Open source, vendor neutral instrumentation is an exciting new reality as the industry standardizes on openTelemetry for observability. OpenTelemetry is on a mission to enable effective observability by making high-quality, portable telemetry ubiquitous. The world of observability and monitoring today has a steep learning curve and in order to achieve ubiquity, the project would benefit from growing our contributor community.
Open Source 101 - Observability For You and Me with OpenTelemetryEric D. Schabell
Are you interested in dipping your toes in the cloud native observability waters, but as an engineer you are not sure where to get started with tracing problems through your microservices and application landscapes on Kubernetes? Then this is the session for you, where we take you on your first steps in an active open-source project that offers a buffet of languages, challenges, and opportunities for getting started with telemetry data.
The project is called openTelemetry, but before diving into the specifics, we’ll start with de-mystifying key concepts and terms such as observability, telemetry, instrumentation, cardinality, percentile to lay a foundation. After understanding the nuts and bolts of observability and distributed traces, we’ll explore the openTelemetry community; its Special Interest Groups (SIGs), repositories, and how to become not only an end-user, but possibly a contributor.We will wrap up with an overview of the components in this project, such as the Collector, the OpenTelemetry protocol (OTLP), its APIs, and its SDKs.
Attendees will leave with an understanding of key observability concepts, become grounded in distributed tracing terminology, be aware of the components of openTelemetry, and know how to take their first steps to an open-source contribution!
Key Takeaways: Open source, vendor neutral instrumentation is an exciting new reality as the industry standardizes on openTelemetry for observability. OpenTelemetry is on a mission to enable effective observability by making high-quality, portable telemetry ubiquitous. The world of observability and monitoring today has a steep learning curve and in order to achieve ubiquity, the project would benefit from growing our contributor community.
3 Pitfalls Everyone Should Avoid with Cloud DataEric D. Schabell
The daily hype is all around you. From cloud native, multicloud, to hybrid cloud, this is the path to your digital future. The choices you make as a developer does not preclude the daily work of enhancing your customer's experience and agile delivery of your applications. With all this delivery and infrastructure, there is a lot of data generated when engaging with any cloud experience. Regulatory and compliance pressures force us to store audit and observability data. Understanding the pitfalls around the collection, storage, and maintenance of your cloud data can mean the difference between bankruptcy and success with our cloud native strategy. Let us take you on a journey, looking closely at the decisions you are making as a developer delivering and dealing with monitoring your applications. Join us for an hour of power, where real customer experiences are used to highlight the three top lessons learned as their developers transitioned their data needs into cloud native environments.
Key Takeaways: Attendees to this session will gain insights into the data explosion that is part of the large scale cloud native world. Real customer experiences are used to highlight the three top lessons learned as their developers transitioned their data needs into cloud native environments.
3 Pitfalls Everyone Should Avoid with Cloud Native DataEric D. Schabell
The daily hype is all around you. From cloud native, multicloud, to hybrid cloud, this is the path to your digital future. The choices you make as a developer does not preclude the daily work of enhancing your customer's experience and agile delivery of your applications. With all this delivery and infrastructure, there is a lot of data generated when engaging with any cloud experience. Regulatory and compliance pressures force us to store audit and observability data. Understanding the pitfalls around the collection, storage, and maintenance of your cloud data can mean the difference between bankruptcy and success with our cloud native strategy. Let us take you on a journey, looking closely at the decisions you are making as a developer delivering and dealing with monitoring your applications. Join us for an hour of power, where real customer experiences are used to highlight the three top lessons learned as their developers transitioned their data needs into cloud native environments.
Key Takeaways: Attendees to this session will gain insights into the data explosion that is part of the large scale cloud native world. Real customer experiences are used to highlight the three top lessons learned as their developers transitioned their data needs into cloud native environments.
Whether you’re an enterprise migrating to cloud-native or born in the cloud, most of today’s APM and Observability tools don’t support how your engineers and DevOps teams need to develop, deploy, and support their software. Observability needs to shift left and reflect the modern way companies organize their development teams and their vital interdependencies.
Chronosphere is the only vendor addressing the unique requirements for observability in a cloud-native world.
Join this webinar to learn:
• What cloud native observability is and how it is different from the promises made by traditional cloud APM and observability vendors
• How to use cloud-native observability to do more “Dev” and less “Ops” so you can dramatically improve developer and engineer workflows and productivity
• How to make on-call shifts less stressful so that your engineers aren’t getting burned out
1. JBoss Enterprise BRMS
The Road to Large Scale Enterprise Solutions
Phil Simpson, Product Marketing Manager
Eric Schabell, JBoss Technology Evangelist
1
3. JBoss Enterprise BRMS
Business
Events
Interacts
Web-based Decision with... Enterprise
development tools Service Application
Business Analysts Web
Event Processor
Repository Service
Deploy Business Process
Business Business
Process Rule & Manager
Definitions Event
Definitions
Java Code
Rule Engine
JBDS, with BRMS r
plugins i to
on
M
&
ge
ana
M
Business
Developers
Users
Management Business
Console Data
Operations
3
4. JBoss Enterprise BRMS
Business
Events
Interacts
Web-based Decision with... Enterprise
development tools Service Application
Business Analysts Web
Event Processor
Repository Service
Deploy Business Process
Business Business
Process Rule & Manager
Definitions Event
Definitions
Java Code
Rule Engine
JBDS, with BRMS r
plugins i to
on
M
&
ge
ana
M
Business
Developers
Users
Management Business
Console Data
Operations
4
5. JBoss Enterprise BRMS
Business
Events
Interacts
Web-based Decision with... Enterprise
development tools Service Application
Business Analysts Web
Event Processor
Repository Service
Deploy Business Process
Business Business
Process Rule & Manager
Definitions Event
Definitions
Java Code
Rule Engine
JBDS, with BRMS r
plugins i to
on
M
&
ge
ana
M
Business
Developers
Users
Management Business
Console Data
Operations
5
6. JBoss Enterprise BRMS
Business
Events
Interacts
Web-based with...
development tools Decision Enterprise
(Guvnor) Service Application
Business Analysts Web
Event Processor
Repository Service
Deploy Business Process
Business Business
Process Rule & Manager
Definitions Event
Definitions
Java Code
Rule Engine
JBDS, with BRMS r
plugins i to
on
M
&
ge
ana
M
Business
Developers
Users
Management Business
Console Data
Operations
6
7. JBoss Enterprise BRMS
Business
Events
Interacts
Web-based Decision with... Enterprise
development tools Service Application
Business Analysts Web
Event Processor
Repository Service
Deploy Business Process
Business Business
Process Rule & Manager
Definitions Event
Definitions
Java Code
Rule Engine
JBDS, with BRMS r
plugins i to
on
M
&
ge
ana
M
Business
Developers
Users
Management Business
Console Data
Operations
7
8. Best Practices
Developing BRMS Applications that Scale
● BRMS Adoption Goals
● Under the Hood
● Best Practices
● BPM
● Architecture
● Rules Authoring
8
10. Goal #1: Decision Automation
Conclusion: Time is Money!
Business Event
Value Loss
Business Value
Reaction
Time
Time Loss
Adapted from a presentation by James Taylor, Sep/2011
10
11. Goal #2: Expressiveness and Visibility
rule “Send shipment pick-up SMS alert”
rule “Send shipment pick-up SMS alert”
when
when
There is a shipment order
There is a shipment order
There is a route assigned to
There is a route assigned to the
order
the
order
There is a truck GPS reading
There is a truck GPS reading and
the truck is 15 minutes
and
the truck is 15 minutes
away from the pick-up location
away from the pick-up location
then
then
Send SMS to customer: “Arriving in 15 minutes”
Send SMS to customer: “Arriving in 15 minutes”
end
end
Focus on “what to do” instead of “how to do it”
11
12. Goal #3: Performance and Scalability
● Real time, online, systems
● Millisecond response times
● Hundreds of thousands of rules
● JBoss BRMS: 700k+ rules
● Millions of data instances (facts)
● Incremental (re-)evaluation
● Changes in data can't reset reasoning
12
13. Goal #4..#6: other technical goals
● Logic, Data and Tasks split
● Centralization of Knowledge
● Consistency
● Testing / Simulation
Knowledge Knowledge
● Auditing Base
(rules/events/
Inference Session
Engine (data)
processes)
● Explanation Facility
Tasks
13
16. JBoss BRMS – some optimizations
● Support to POJOs as facts
● no mapping/data copy necessary
● Full split between Knowledge Base and Session
● lightweight session creation
● knowledge base sharing
● Completely Dynamic Knowledge Base
● Hot addition/removal/updates of rules/queries/processes
● Full support to First Order Logic and Set operations
● JIT compilation for constraints and data access
16
17. JBoss BRMS – More optimizations
Data
Alpha Hashing
Customer Order
Node Sharing
Gold Silver < $1000 >=$1000
Data Indexing
Lazy Matching
Discount: 15% Discount: 5% Discount: 10%
17
19. Best Practices – BPM Architecture
Interaction Layer
EJB / POJO ESB Web Services Human Tasks
Process Implementation Layer JBPM Console
Reporting,
BAM Dashboards
Process Repository
Queues
Process
Initialization
Layer BPMN2 Authoring for BPMN2 Authoring for
Business Users Developers
Developer
19
Customer
20. Best Practices – Process Initialization EJB MDB
● How do you start your process? Queues
● web services, EJB's, API call, RESTful
● what about prioritization of processes Process
Initialization
Layer
● use message queues
● other complex ideas to start processes
● Centralize startProcess in single location
● minimizes change effects in this layer
Customer
20
21. Process Implementation Layer
Best Practices –
Process Implementation
● Java nodes
● do you keep it clean?
● single unit of action per process step
● human task / admin interfaces
● Centralize you jBPM API access
● single WS / DAO / BOM / RESTful
● Domain specific nodes
● extensions via work item handlers
● Design process for reuse
● smallest unit of work
21
22. Best Practices – Process Interaction
● Processes interact with your Enterprise
● Web Services, EJB, GUI, POJO, Exceptions, Bean
Script, Rules...
● jBPM API & jBPM History DB & RESTful
● history / tasks / reporting
● single DAO
● single Web Service
● JBoss ESB + jBPM
● externalize rules calls in Decision Service (WS)
Interaction Layer
22 Human Tasks
EJB / POJO ESB Web Services
23. Best Practices – Always good BPM practices...
● Simplify everything (KISS)
● apply OO to process design
● methods == sub-process + context in/out
● encapsulate == sub-process
● reuse == process repo (maven potential)
● unit testing == per node, sub-process, process
● exception handling (Exception Framework)
23
24. Best Practices – Rule Architecture
● Partition your Knowledge Bases properly
● Subject matter
● Transaction / Service / Unit of Work
● Business Entity
● Avoid monolithic Knowledge Bases
● Avoid fine grained Knowledge Bases
Knowledge Inference Knowledge
Base Engine Session
Tasks
24
25. Best Practices – Rule Architecture
● Batch data loads
● Load 1000 facts and fire the rules faster than fire rules after
each loaded fact
● Partition the data into multiple sessions
● Transaction / Service / Unit of work
● Creating a new session is cheap
● Cheaper than removing facts Knowledge Knowledge
Inference
Base Engine Session
Tasks
25
26. Best Practices – Rule Architecture
● Quality of the data/fact model is directly proportional to the
performance and maintainability of the rules using it
● Think about the DBMS analogy
● Flatter models improve performance
● Smaller classes help avoiding recursions
Knowledge Inference Knowledge
Base Engine Session
Tasks
26
27. JBoss BRMS – Best Practices in Rules Authoring
27
28. Best Practices – Rules Authoring
● Don't try to micro-control rules execution
● Use the Conflict Resolution Strategies instead
● Salience
● Agenda groups
● Ruleflow / Processes
● Dynamic Enablement
Knowledge Inference Knowledge
Base Engine Session
Tasks
28
29. Best Practices – Rules Authoring
● Don't overload rules
● Each rule should describe one and only one
scenario→action mapping
● The engine will optimize shared conditions
● The engine supports inference
Knowledge Inference Knowledge
Base Engine Session
Tasks
29
30. Best Bad Practices – Rules Authoring
rule “1 – Teenagers and Elders get Discount”
rule “1 – Teenagers and Elders get Discount”
when
when
Person age is between 16 and 18 or Person age is greater or equal to 65
Person age is between 16 and 18 or Person age is greater or equal to 65
then
then
Assign 25% ticket discount
Assign 25% ticket discount
end
end
rule “2 – Elders can buy tickets in area A”
rule “2 – Elders can buy tickets in area A”
when
when
Person age is greater or equal to 65
Person age is greater or equal to 65
then
then
Allow sales of area A tickets
Allow sales of area A tickets
end
end
Rules are being overloaded with multiple concepts, increasing maintenance
and testing costs.
30
31. Best Practices – Rules Authoring
rule “0.a – Teenagers are 16-18”
rule “0.a – Teenagers are 16-18” rule “0.b – Elders are older than 65”
rule “0.b – Elders are older than 65”
when
when when
when
Person age is between 16 and 18
Person age is between 16 and 18 Person is older than 65
Person is older than 65
then
then then
then
Assert: the person is a Teenager
Assert: the person is a Teenager Assert: the person is an Elder
Assert: the person is an Elder
end
end end
end
rule “1 – Teenagers and Elders get discount”
rule “1 – Teenagers and Elders get discount” rule “2 – Elders can buy tickets in area A”
rule “2 – Elders can buy tickets in area A”
when
when when
when
Teenager or Elder
Teenager or Elder Elder
Elder
then
then then
then
Assign 25% ticket discount
Assign 25% ticket discount Allow sales of area A tickets
Allow sales of area A tickets
end
end end
end
31
32. Best Practices – Rules Authoring
● One calculation (accumulate) per rule
● Accumulates have O(n) performance
●
Sequences of accumulates have O(nm) performance
● n = number of matching facts
● m = number of accumulates
rule “Sum debits”
rule “Sum debits”
when
when
rule “Sum debits and credits”
rule “Sum debits and credits”
accumulate( Debit( $d : amount ),
accumulate( Debit( $d : amount ),
when
when
$debits: sum( $d ) )
$debits: sum( $d ) )
accumulate( Debit( $d : amount ),
accumulate( Debit( $d : amount ),
then ...
then ...
$debits: sum( $d ) )
$debits: sum( $d ) )
accumulate( Credit( $c : amount),
accumulate( Credit( $c : amount), rule “Sum credits”
rule “Sum credits”
$credits: sum( $c ) )
$credits: sum( $c ) ) when
when
then ...
then ... accumulate( Credit( $c : amount ),
accumulate( Credit( $c : amount ),
$credits: sum( $c ) )
$credits: sum( $c ) )
then ...
then ...
32
33. Best Practices – Rules Authoring
● Rules vs Queries
Rules Queries
Control Invoked by the engine Invoked by the application
Parameters Don't support parameters Support parameters
Results Execute actions Return results
rule “Approve VIP customers”
rule “Approve VIP customers” query “Get customers by type”( $type )
query “Get customers by type”( $type )
when
when when
when
$c : Customer( type == “VIP” )
$c : Customer( type == “VIP” ) $c : Customer( type == $type )
$c : Customer( type == $type )
then
then end
end
insert( new Approved( $c ) );
insert( new Approved( $c ) );
end
end
“Use the right tool for the right job!”
33
34. Best Practices – Rules Authoring
● Declared Types
● Facts used only by the rules
● Facts that change frequently with the rules
● POJOs
● Facts shared by both rules and application
● No data copy – very efficient
● Easier to integrate, easier to test
● When in doubt, use POJOs
“Use the right tool for the right job!”
34