�ݺ�ߣshows by User: rdebusscher

�ݺ�ߣshows by User: rdebusscher / http://www.slideshare.net/images/logo.gif �ݺ�ߣshows by User: rdebusscher / Wed, 19 Apr 2023 17:32:11 GMT �ݺ�ߣShare feed for �ݺ�ߣshows by User: rdebusscher jakarta-integration-testing.pdf /slideshow/jakartaintegrationtestingpdf/257475646 jakarta-integration-testing-230419173212-a86fcea7
Integration testing is difficult as you need additional systems, like a database, with a predefined set of data to have repeatable tests. With the availability of the Testcontainers framework, developers can test the real application by deploying it in a container using the runtime that will be used in production and dependencies available in other containers. In this session, we explore a few scenarios of how you can use the Testcontainers framework to test your Jakarta EE application, including a remote debug session of your code.]]>
Integration testing is difficult as you need additional systems, like a database, with a predefined set of data to have repeatable tests. With the availability of the Testcontainers framework, developers can test the real application by deploying it in a container using the runtime that will be used in production and dependencies available in other containers. In this session, we explore a few scenarios of how you can use the Testcontainers framework to test your Jakarta EE application, including a remote debug session of your code.]]> Wed, 19 Apr 2023 17:32:11 GMT /slideshow/jakartaintegrationtestingpdf/257475646 rdebusscher@slideshare.net(rdebusscher) jakarta-integration-testing.pdf rdebusscher Integration testing is difficult as you need additional systems, like a database, with a predefined set of data to have repeatable tests. With the availability of the Testcontainers framework, developers can test the real application by deploying it in a container using the runtime that will be used in production and dependencies available in other containers. In this session, we explore a few scenarios of how you can use the Testcontainers framework to test your Jakarta EE application, including a remote debug session of your code. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/jakarta-integration-testing-230419173212-a86fcea7-thumbnail.jpg?width=120&height=120&fit=bounds" /> Integration testing is difficult as you need additional systems, like a database, with a predefined set of data to have repeatable tests. With the availability of the Testcontainers framework, developers can test the real application by deploying it in a container using the runtime that will be used in production and dependencies available in other containers. In this session, we explore a few scenarios of how you can use the Testcontainers framework to test your Jakarta EE application, including a remote debug session of your code.

jakarta-integration-testing.pdf from Rudy De Busscher

]]> 35 0 https://cdn.slidesharecdn.com/ss_thumbnails/jakarta-integration-testing-230419173212-a86fcea7-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 core-profile_jakartaOne2022.pdf /slideshow/coreprofilejakartaone2022pdf/254776814 core-profilejakartaone2022-221206115205-f72c1cc3
Exploring the new Jakarta EE Core Profile. Going into details about CDI lite, the new Bootstrap API for Java SE of Jakarta REST and some modularization approaches with different products.]]>
Exploring the new Jakarta EE Core Profile. Going into details about CDI lite, the new Bootstrap API for Java SE of Jakarta REST and some modularization approaches with different products.]]> Tue, 06 Dec 2022 11:52:05 GMT /slideshow/coreprofilejakartaone2022pdf/254776814 rdebusscher@slideshare.net(rdebusscher) core-profile_jakartaOne2022.pdf rdebusscher Exploring the new Jakarta EE Core Profile. Going into details about CDI lite, the new Bootstrap API for Java SE of Jakarta REST and some modularization approaches with different products. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/core-profilejakartaone2022-221206115205-f72c1cc3-thumbnail.jpg?width=120&height=120&fit=bounds" /> Exploring the new Jakarta EE Core Profile. Going into details about CDI lite, the new Bootstrap API for Java SE of Jakarta REST and some modularization approaches with different products.

core-profile_jakartaOne2022.pdf from Rudy De Busscher

]]> 535 0 https://cdn.slidesharecdn.com/ss_thumbnails/core-profilejakartaone2022-221206115205-f72c1cc3-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 MicroStream-WithoutDatabase.pdf /slideshow/microstreamwithoutdatabasepdf/253065475 microstream-withoutdatabase-220920150402-f9516bac
Microservices are used more and more but many of them need to access data. Using a database is well established but also slow as data need to be retrieved from an external system in another format and structure and thus requires a mapping. With MicroStream, you can realise ultra-fast data processing since it uses just your POJOs in memory. Microsecond query time, low-latency data access and gigantic data throughput are realised very simple. The Java instances that make up your data are serialised to external system fast and secure. This presentation gives you an introduction to the framework.]]>
Microservices are used more and more but many of them need to access data. Using a database is well established but also slow as data need to be retrieved from an external system in another format and structure and thus requires a mapping. With MicroStream, you can realise ultra-fast data processing since it uses just your POJOs in memory. Microsecond query time, low-latency data access and gigantic data throughput are realised very simple. The Java instances that make up your data are serialised to external system fast and secure. This presentation gives you an introduction to the framework.]]> Tue, 20 Sep 2022 15:04:02 GMT /slideshow/microstreamwithoutdatabasepdf/253065475 rdebusscher@slideshare.net(rdebusscher) MicroStream-WithoutDatabase.pdf rdebusscher Microservices are used more and more but many of them need to access data. Using a database is well established but also slow as data need to be retrieved from an external system in another format and structure and thus requires a mapping. With MicroStream, you can realise ultra-fast data processing since it uses just your POJOs in memory. Microsecond query time, low-latency data access and gigantic data throughput are realised very simple. The Java instances that make up your data are serialised to external system fast and secure. This presentation gives you an introduction to the framework. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/microstream-withoutdatabase-220920150402-f9516bac-thumbnail.jpg?width=120&height=120&fit=bounds" /> Microservices are used more and more but many of them need to access data. Using a database is well established but also slow as data need to be retrieved from an external system in another format and structure and thus requires a mapping. With MicroStream, you can realise ultra-fast data processing since it uses just your POJOs in memory. Microsecond query time, low-latency data access and gigantic data throughput are realised very simple. The Java instances that make up your data are serialised to external system fast and secure. This presentation gives you an introduction to the framework.

MicroStream-WithoutDatabase.pdf from Rudy De Busscher

]]> 72 0 https://cdn.slidesharecdn.com/ss_thumbnails/microstream-withoutdatabase-220920150402-f9516bac-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Jakarta EE 8 on JDK17 /slideshow/jakarta-ee-8-on-jdk17/250502245 jakarta-jdk17-211022075707
JDK 17, the next LTS version of Java, is available and it contains not only new language constructs but also there are many operational improvements like higher performance. We have a look at what a Jakarta EE developer will find interesting, even if you are using Jakarta EE 8. Learn about these features and improvements including Records, Text blocks, Garbage collection improvements, and monitoring through Flight Recorder in several live demos with Payara Micro. After this session you will be able to use all new shiny features of JDK 17 in your next Java Enterprise application.]]>
JDK 17, the next LTS version of Java, is available and it contains not only new language constructs but also there are many operational improvements like higher performance. We have a look at what a Jakarta EE developer will find interesting, even if you are using Jakarta EE 8. Learn about these features and improvements including Records, Text blocks, Garbage collection improvements, and monitoring through Flight Recorder in several live demos with Payara Micro. After this session you will be able to use all new shiny features of JDK 17 in your next Java Enterprise application.]]> Fri, 22 Oct 2021 07:57:07 GMT /slideshow/jakarta-ee-8-on-jdk17/250502245 rdebusscher@slideshare.net(rdebusscher) Jakarta EE 8 on JDK17 rdebusscher JDK 17, the next LTS version of Java, is available and it contains not only new language constructs but also there are many operational improvements like higher performance. We have a look at what a Jakarta EE developer will find interesting, even if you are using Jakarta EE 8. Learn about these features and improvements including Records, Text blocks, Garbage collection improvements, and monitoring through Flight Recorder in several live demos with Payara Micro. After this session you will be able to use all new shiny features of JDK 17 in your next Java Enterprise application. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/jakarta-jdk17-211022075707-thumbnail.jpg?width=120&height=120&fit=bounds" /> JDK 17, the next LTS version of Java, is available and it contains not only new language constructs but also there are many operational improvements like higher performance. We have a look at what a Jakarta EE developer will find interesting, even if you are using Jakarta EE 8. Learn about these features and improvements including Records, Text blocks, Garbage collection improvements, and monitoring through Flight Recorder in several live demos with Payara Micro. After this session you will be able to use all new shiny features of JDK 17 in your next Java Enterprise application.

Jakarta EE 8 on JDK17 from Rudy De Busscher

]]> 502 0 https://cdn.slidesharecdn.com/ss_thumbnails/jakarta-jdk17-211022075707-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 How Class Data Sharing Can Speed up Your Jakarta EE Application Startup /slideshow/how-class-data-sharing-can-speed-up-your-jakarta-ee-application-startup/239851825 jakartacds-201207192307
Java Byte code is OS independent, which means that your application's startup takes more time than a native image. Using the Class Data Sharing functionality introduced in more recent versions of the JVM, you can prepare your application so that it will load very fast. In this presentation, I'll go into more detail what Class Data Sharing is and the differences between the OpenJDK and OpenJ9 versions. With some Jakarta EE demo applications, you will see gains that you can achieve and reduce memory footprint a lot in Docker containers by sharing memory.]]>
Java Byte code is OS independent, which means that your application's startup takes more time than a native image. Using the Class Data Sharing functionality introduced in more recent versions of the JVM, you can prepare your application so that it will load very fast. In this presentation, I'll go into more detail what Class Data Sharing is and the differences between the OpenJDK and OpenJ9 versions. With some Jakarta EE demo applications, you will see gains that you can achieve and reduce memory footprint a lot in Docker containers by sharing memory.]]> Mon, 07 Dec 2020 19:23:07 GMT /slideshow/how-class-data-sharing-can-speed-up-your-jakarta-ee-application-startup/239851825 rdebusscher@slideshare.net(rdebusscher) How Class Data Sharing Can Speed up Your Jakarta EE Application Startup rdebusscher Java Byte code is OS independent, which means that your application's startup takes more time than a native image. Using the Class Data Sharing functionality introduced in more recent versions of the JVM, you can prepare your application so that it will load very fast. In this presentation, I'll go into more detail what Class Data Sharing is and the differences between the OpenJDK and OpenJ9 versions. With some Jakarta EE demo applications, you will see gains that you can achieve and reduce memory footprint a lot in Docker containers by sharing memory. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/jakartacds-201207192307-thumbnail.jpg?width=120&height=120&fit=bounds" /> Java Byte code is OS independent, which means that your application's startup takes more time than a native image. Using the Class Data Sharing functionality introduced in more recent versions of the JVM, you can prepare your application so that it will load very fast. In this presentation, I'll go into more detail what Class Data Sharing is and the differences between the OpenJDK and OpenJ9 versions. With some Jakarta EE demo applications, you will see gains that you can achieve and reduce memory footprint a lot in Docker containers by sharing memory.

How Class Data Sharing Can Speed up Your Jakarta EE Application Startup from Rudy De Busscher

]]> 244 0 https://cdn.slidesharecdn.com/ss_thumbnails/jakartacds-201207192307-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Creating a Kubernetes Operator in Java /slideshow/creating-a-kubernetes-operator-in-java/239051046 kubernetesoperatorjava-201102100928
Kubernetes is much more than a runtime platform for Docker containers. Through its API not only can you create custom clients, but you can also extend Kubernetes. Those custom Controllers are called Operators and work with application-specific custom resource definitions. Not only can you write those Kubernetes operators in Go, but you can also do this in Java. Within this talk, you will be guided through setting up and your first explorations of the Kubernetes API within a plain Java program. We explore the concepts of resource listeners, programmatic creation of deployments and services and how this can be used for your custom requirements.]]>
Kubernetes is much more than a runtime platform for Docker containers. Through its API not only can you create custom clients, but you can also extend Kubernetes. Those custom Controllers are called Operators and work with application-specific custom resource definitions. Not only can you write those Kubernetes operators in Go, but you can also do this in Java. Within this talk, you will be guided through setting up and your first explorations of the Kubernetes API within a plain Java program. We explore the concepts of resource listeners, programmatic creation of deployments and services and how this can be used for your custom requirements.]]> Mon, 02 Nov 2020 10:09:28 GMT /slideshow/creating-a-kubernetes-operator-in-java/239051046 rdebusscher@slideshare.net(rdebusscher) Creating a Kubernetes Operator in Java rdebusscher Kubernetes is much more than a runtime platform for Docker containers. Through its API not only can you create custom clients, but you can also extend Kubernetes. Those custom Controllers are called Operators and work with application-specific custom resource definitions. Not only can you write those Kubernetes operators in Go, but you can also do this in Java. Within this talk, you will be guided through setting up and your first explorations of the Kubernetes API within a plain Java program. We explore the concepts of resource listeners, programmatic creation of deployments and services and how this can be used for your custom requirements. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/kubernetesoperatorjava-201102100928-thumbnail.jpg?width=120&height=120&fit=bounds" /> Kubernetes is much more than a runtime platform for Docker containers. Through its API not only can you create custom clients, but you can also extend Kubernetes. Those custom Controllers are called Operators and work with application-specific custom resource definitions. Not only can you write those Kubernetes operators in Go, but you can also do this in Java. Within this talk, you will be guided through setting up and your first explorations of the Kubernetes API within a plain Java program. We explore the concepts of resource listeners, programmatic creation of deployments and services and how this can be used for your custom requirements.

Creating a Kubernetes Operator in Java from Rudy De Busscher

]]> 182 0 https://cdn.slidesharecdn.com/ss_thumbnails/kubernetesoperatorjava-201102100928-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Finally, easy integration testing with Testcontainers /slideshow/finally-easy-integration-testing-with-testcontainers/204452245 testcontainers-191211141558
Integration testing is always a difficult area. You need to make sure that all system are connected, data is correctly initialised for each run and test runs do not interfere with each other. You can do integration testing today, but sometimes these tests are flaky for various reasons or they cannot cover all the cases that you would like to test. With the Testcontainers project, this issue can be a thing of the past. It allows you to create reliable integration tests covering a wide range of scenarios like database usages, micro services interaction and GUI testing. One of the important factors for the success of this framework is the usage of Docker containers to create a reproducible environment for the test. ]]>
Integration testing is always a difficult area. You need to make sure that all system are connected, data is correctly initialised for each run and test runs do not interfere with each other. You can do integration testing today, but sometimes these tests are flaky for various reasons or they cannot cover all the cases that you would like to test. With the Testcontainers project, this issue can be a thing of the past. It allows you to create reliable integration tests covering a wide range of scenarios like database usages, micro services interaction and GUI testing. One of the important factors for the success of this framework is the usage of Docker containers to create a reproducible environment for the test. ]]> Wed, 11 Dec 2019 14:15:57 GMT /slideshow/finally-easy-integration-testing-with-testcontainers/204452245 rdebusscher@slideshare.net(rdebusscher) Finally, easy integration testing with Testcontainers rdebusscher Integration testing is always a difficult area. You need to make sure that all system are connected, data is correctly initialised for each run and test runs do not interfere with each other. You can do integration testing today, but sometimes these tests are flaky for various reasons or they cannot cover all the cases that you would like to test. With the Testcontainers project, this issue can be a thing of the past. It allows you to create reliable integration tests covering a wide range of scenarios like database usages, micro services interaction and GUI testing. One of the important factors for the success of this framework is the usage of Docker containers to create a reproducible environment for the test. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/testcontainers-191211141558-thumbnail.jpg?width=120&height=120&fit=bounds" /> Integration testing is always a difficult area. You need to make sure that all system are connected, data is correctly initialised for each run and test runs do not interfere with each other. You can do integration testing today, but sometimes these tests are flaky for various reasons or they cannot cover all the cases that you would like to test. With the Testcontainers project, this issue can be a thing of the past. It allows you to create reliable integration tests covering a wide range of scenarios like database usages, micro services interaction and GUI testing. One of the important factors for the success of this framework is the usage of Docker containers to create a reproducible environment for the test.

Finally, easy integration testing with Testcontainers from Rudy De Busscher

]]> 1133 3 https://cdn.slidesharecdn.com/ss_thumbnails/testcontainers-191211141558-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Control and monitor_microservices_with_microprofile /slideshow/control-and-monitormicroserviceswithmicroprofile/175935528 controlandmonitormicroserviceswithmicroprofile-190925100818
Microservices architecture has many benefits. But it comes at a cost. Running microservices and monitoring what’s going on is tedious. That’s why MicroProfile adopts monitoring as a first-class concept. In this session, learn how MicroProfile runtimes collect metrics and how to seamlessly collect them with tools like Prometheus and Grafana. Learn how MicroProfile makes it easy to connect information about interrelated service calls, how to gather the information and analyze system bottlenecks, how to deploy and scale MicroProfile applications with Kubernetes and how to react to their health status to detect and automatically recover from failures.]]>
Microservices architecture has many benefits. But it comes at a cost. Running microservices and monitoring what’s going on is tedious. That’s why MicroProfile adopts monitoring as a first-class concept. In this session, learn how MicroProfile runtimes collect metrics and how to seamlessly collect them with tools like Prometheus and Grafana. Learn how MicroProfile makes it easy to connect information about interrelated service calls, how to gather the information and analyze system bottlenecks, how to deploy and scale MicroProfile applications with Kubernetes and how to react to their health status to detect and automatically recover from failures.]]> Wed, 25 Sep 2019 10:08:18 GMT /slideshow/control-and-monitormicroserviceswithmicroprofile/175935528 rdebusscher@slideshare.net(rdebusscher) Control and monitor_microservices_with_microprofile rdebusscher Microservices architecture has many benefits. But it comes at a cost. Running microservices and monitoring what’s going on is tedious. That’s why MicroProfile adopts monitoring as a first-class concept. In this session, learn how MicroProfile runtimes collect metrics and how to seamlessly collect them with tools like Prometheus and Grafana. Learn how MicroProfile makes it easy to connect information about interrelated service calls, how to gather the information and analyze system bottlenecks, how to deploy and scale MicroProfile applications with Kubernetes and how to react to their health status to detect and automatically recover from failures. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/controlandmonitormicroserviceswithmicroprofile-190925100818-thumbnail.jpg?width=120&height=120&fit=bounds" /> Microservices architecture has many benefits. But it comes at a cost. Running microservices and monitoring what’s going on is tedious. That’s why MicroProfile adopts monitoring as a first-class concept. In this session, learn how MicroProfile runtimes collect metrics and how to seamlessly collect them with tools like Prometheus and Grafana. Learn how MicroProfile makes it easy to connect information about interrelated service calls, how to gather the information and analyze system bottlenecks, how to deploy and scale MicroProfile applications with Kubernetes and how to react to their health status to detect and automatically recover from failures.

Control and monitor_microservices_with_microprofile from Rudy De Busscher

]]> 158 0 https://cdn.slidesharecdn.com/ss_thumbnails/controlandmonitormicroserviceswithmicroprofile-190925100818-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Transactions in micro-services (fall 2019) /slideshow/transactions-in-microservices-fall-2019/171439445 transactions-inmicroservices-fall2019-190913052056
How can you make different pieces of your unit of work consistent in the distributed setup of your micro-service application? You associate the term transaction probably with a database, but the data source can be anything including a database in the micro-service world. The MicroProfile Long Running Actions specification is based on sagas and the OASIS LRA transaction model specification. It defines the framework to guarantee the eventual consistency requirement using compensating actions for example. This session will explain you the challenges and concepts of the MP LRA framework.]]>
How can you make different pieces of your unit of work consistent in the distributed setup of your micro-service application? You associate the term transaction probably with a database, but the data source can be anything including a database in the micro-service world. The MicroProfile Long Running Actions specification is based on sagas and the OASIS LRA transaction model specification. It defines the framework to guarantee the eventual consistency requirement using compensating actions for example. This session will explain you the challenges and concepts of the MP LRA framework.]]> Fri, 13 Sep 2019 05:20:56 GMT /slideshow/transactions-in-microservices-fall-2019/171439445 rdebusscher@slideshare.net(rdebusscher) Transactions in micro-services (fall 2019) rdebusscher How can you make different pieces of your unit of work consistent in the distributed setup of your micro-service application? You associate the term transaction probably with a database, but the data source can be anything including a database in the micro-service world. The MicroProfile Long Running Actions specification is based on sagas and the OASIS LRA transaction model specification. It defines the framework to guarantee the eventual consistency requirement using compensating actions for example. This session will explain you the challenges and concepts of the MP LRA framework. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/transactions-inmicroservices-fall2019-190913052056-thumbnail.jpg?width=120&height=120&fit=bounds" /> How can you make different pieces of your unit of work consistent in the distributed setup of your micro-service application? You associate the term transaction probably with a database, but the data source can be anything including a database in the micro-service world. The MicroProfile Long Running Actions specification is based on sagas and the OASIS LRA transaction model specification. It defines the framework to guarantee the eventual consistency requirement using compensating actions for example. This session will explain you the challenges and concepts of the MP LRA framework.

Transactions in micro-services (fall 2019) from Rudy De Busscher

]]> 541 2 https://cdn.slidesharecdn.com/ss_thumbnails/transactions-inmicroservices-fall2019-190913052056-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Transactions in micro-services (summer 2019) /slideshow/transactions-in-microservices/151077018 transactions-in-microservices-190621103618
How can you make different pieces of your unit of work consistent in the distributed setup of your micro-service application? You associate the term transaction probably with a database, but the data source can be anything including a database in the micro-service world. The MicroProfile Long Running Actions specification is based on sagas and the OASIS LRA transaction model specification. It defines the framework to guarantee the eventual consistency requirement using compensating actions for example. This session will explain you the challenges and concepts of the MP LRA framework.]]>
How can you make different pieces of your unit of work consistent in the distributed setup of your micro-service application? You associate the term transaction probably with a database, but the data source can be anything including a database in the micro-service world. The MicroProfile Long Running Actions specification is based on sagas and the OASIS LRA transaction model specification. It defines the framework to guarantee the eventual consistency requirement using compensating actions for example. This session will explain you the challenges and concepts of the MP LRA framework.]]> Fri, 21 Jun 2019 10:36:18 GMT /slideshow/transactions-in-microservices/151077018 rdebusscher@slideshare.net(rdebusscher) Transactions in micro-services (summer 2019) rdebusscher How can you make different pieces of your unit of work consistent in the distributed setup of your micro-service application? You associate the term transaction probably with a database, but the data source can be anything including a database in the micro-service world. The MicroProfile Long Running Actions specification is based on sagas and the OASIS LRA transaction model specification. It defines the framework to guarantee the eventual consistency requirement using compensating actions for example. This session will explain you the challenges and concepts of the MP LRA framework. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/transactions-in-microservices-190621103618-thumbnail.jpg?width=120&height=120&fit=bounds" /> How can you make different pieces of your unit of work consistent in the distributed setup of your micro-service application? You associate the term transaction probably with a database, but the data source can be anything including a database in the micro-service world. The MicroProfile Long Running Actions specification is based on sagas and the OASIS LRA transaction model specification. It defines the framework to guarantee the eventual consistency requirement using compensating actions for example. This session will explain you the challenges and concepts of the MP LRA framework.

Transactions in micro-services (summer 2019) from Rudy De Busscher

]]> 563 1 https://cdn.slidesharecdn.com/ss_thumbnails/transactions-in-microservices-190621103618-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Monitor Micro-service with MicroProfile metrics /slideshow/monitor-microservice-with-microprofile-metrics/122113430 metrics-181106134515
Microservices architecture has many benefits. But it comes at a cost. Running microservices and monitoring what’s going on is tedious. That’s why MicroProfile adopts monitoring as a first-class concept. In this session, learn how MicroProfile runtimes collect metrics and how to seamlessly collect them with tools like Prometheus and Grafana. Learn how MicroProfile makes it easy to connect information about interrelated service calls, how to gather the information and analyze system bottlenecks, how to deploy and scale MicroProfile applications with Kubernetes and how to react to their health status to detect and automatically recover from failures.]]>
Microservices architecture has many benefits. But it comes at a cost. Running microservices and monitoring what’s going on is tedious. That’s why MicroProfile adopts monitoring as a first-class concept. In this session, learn how MicroProfile runtimes collect metrics and how to seamlessly collect them with tools like Prometheus and Grafana. Learn how MicroProfile makes it easy to connect information about interrelated service calls, how to gather the information and analyze system bottlenecks, how to deploy and scale MicroProfile applications with Kubernetes and how to react to their health status to detect and automatically recover from failures.]]> Tue, 06 Nov 2018 13:45:15 GMT /slideshow/monitor-microservice-with-microprofile-metrics/122113430 rdebusscher@slideshare.net(rdebusscher) Monitor Micro-service with MicroProfile metrics rdebusscher Microservices architecture has many benefits. But it comes at a cost. Running microservices and monitoring what’s going on is tedious. That’s why MicroProfile adopts monitoring as a first-class concept. In this session, learn how MicroProfile runtimes collect metrics and how to seamlessly collect them with tools like Prometheus and Grafana. Learn how MicroProfile makes it easy to connect information about interrelated service calls, how to gather the information and analyze system bottlenecks, how to deploy and scale MicroProfile applications with Kubernetes and how to react to their health status to detect and automatically recover from failures. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/metrics-181106134515-thumbnail.jpg?width=120&height=120&fit=bounds" /> Microservices architecture has many benefits. But it comes at a cost. Running microservices and monitoring what’s going on is tedious. That’s why MicroProfile adopts monitoring as a first-class concept. In this session, learn how MicroProfile runtimes collect metrics and how to seamlessly collect them with tools like Prometheus and Grafana. Learn how MicroProfile makes it easy to connect information about interrelated service calls, how to gather the information and analyze system bottlenecks, how to deploy and scale MicroProfile applications with Kubernetes and how to react to their health status to detect and automatically recover from failures.

Monitor Micro-service with MicroProfile metrics from Rudy De Busscher

]]> 496 2 https://cdn.slidesharecdn.com/ss_thumbnails/metrics-181106134515-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Gradual migration to MicroProfile /slideshow/gradual-migration-to-microprofile/120554666 gradualmigrationtomicroprofile-181024113841
The goal of MicroProfile is to optimise Java EE for a micro-service architecture. It is based on some of the Java EE specifications and standardise a few technologies from the micro-services space. However, some of the MicroProfile implementations are completely different 'servers', like the KumuluzEE server. So how can you migrate easily from your favorite Java EE server to a MicroProfile implementation? This session shows you an overview of what MicroProfile.IO is and how it relates to Java EE. It then demonstrates with a few examples how you can adjust your Java EE application to incorporate some of the MicroProfile.IO specifications and how you can transform your Java EE application to a MicroProfile.IO one using Thorntail, Payara Micro, and KumuluzEE.]]>
The goal of MicroProfile is to optimise Java EE for a micro-service architecture. It is based on some of the Java EE specifications and standardise a few technologies from the micro-services space. However, some of the MicroProfile implementations are completely different 'servers', like the KumuluzEE server. So how can you migrate easily from your favorite Java EE server to a MicroProfile implementation? This session shows you an overview of what MicroProfile.IO is and how it relates to Java EE. It then demonstrates with a few examples how you can adjust your Java EE application to incorporate some of the MicroProfile.IO specifications and how you can transform your Java EE application to a MicroProfile.IO one using Thorntail, Payara Micro, and KumuluzEE.]]> Wed, 24 Oct 2018 11:38:41 GMT /slideshow/gradual-migration-to-microprofile/120554666 rdebusscher@slideshare.net(rdebusscher) Gradual migration to MicroProfile rdebusscher The goal of MicroProfile is to optimise Java EE for a micro-service architecture. It is based on some of the Java EE specifications and standardise a few technologies from the micro-services space. However, some of the MicroProfile implementations are completely different 'servers', like the KumuluzEE server. So how can you migrate easily from your favorite Java EE server to a MicroProfile implementation? This session shows you an overview of what MicroProfile.IO is and how it relates to Java EE. It then demonstrates with a few examples how you can adjust your Java EE application to incorporate some of the MicroProfile.IO specifications and how you can transform your Java EE application to a MicroProfile.IO one using Thorntail, Payara Micro, and KumuluzEE. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/gradualmigrationtomicroprofile-181024113841-thumbnail.jpg?width=120&height=120&fit=bounds" /> The goal of MicroProfile is to optimise Java EE for a micro-service architecture. It is based on some of the Java EE specifications and standardise a few technologies from the micro-services space. However, some of the MicroProfile implementations are completely different 'servers', like the KumuluzEE server. So how can you migrate easily from your favorite Java EE server to a MicroProfile implementation? This session shows you an overview of what MicroProfile.IO is and how it relates to Java EE. It then demonstrates with a few examples how you can adjust your Java EE application to incorporate some of the MicroProfile.IO specifications and how you can transform your Java EE application to a MicroProfile.IO one using Thorntail, Payara Micro, and KumuluzEE.

Gradual migration to MicroProfile from Rudy De Busscher

]]> 260 2 https://cdn.slidesharecdn.com/ss_thumbnails/gradualmigrationtomicroprofile-181024113841-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Secure JAX-RS /slideshow/secure-jaxrs/94252902 securerest-180418180006
With the rise of micro-services, REST communication is more popular than ever. But the communication between the different parts must also be performed in a secure way. First, we need to know if the user or system is allowed to call the JAX-RS endpoint. For this authentication part, self-contained tokens are the best option to not overload any of our services in the system. JWT which contains the authentication but also can contain the authorization info is ideal for this use-case. And secondly, we need guarantees that the message isn't altered, that we can have message integrity. For that part, we can use signatures like specified in the HTTP signature draft specification.]]>
With the rise of micro-services, REST communication is more popular than ever. But the communication between the different parts must also be performed in a secure way. First, we need to know if the user or system is allowed to call the JAX-RS endpoint. For this authentication part, self-contained tokens are the best option to not overload any of our services in the system. JWT which contains the authentication but also can contain the authorization info is ideal for this use-case. And secondly, we need guarantees that the message isn't altered, that we can have message integrity. For that part, we can use signatures like specified in the HTTP signature draft specification.]]> Wed, 18 Apr 2018 18:00:05 GMT /slideshow/secure-jaxrs/94252902 rdebusscher@slideshare.net(rdebusscher) Secure JAX-RS rdebusscher With the rise of micro-services, REST communication is more popular than ever. But the communication between the different parts must also be performed in a secure way. First, we need to know if the user or system is allowed to call the JAX-RS endpoint. For this authentication part, self-contained tokens are the best option to not overload any of our services in the system. JWT which contains the authentication but also can contain the authorization info is ideal for this use-case. And secondly, we need guarantees that the message isn't altered, that we can have message integrity. For that part, we can use signatures like specified in the HTTP signature draft specification. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/securerest-180418180006-thumbnail.jpg?width=120&height=120&fit=bounds" /> With the rise of micro-services, REST communication is more popular than ever. But the communication between the different parts must also be performed in a secure way. First, we need to know if the user or system is allowed to call the JAX-RS endpoint. For this authentication part, self-contained tokens are the best option to not overload any of our services in the system. JWT which contains the authentication but also can contain the authorization info is ideal for this use-case. And secondly, we need guarantees that the message isn't altered, that we can have message integrity. For that part, we can use signatures like specified in the HTTP signature draft specification.

Secure JAX-RS from Rudy De Busscher

]]> 443 2 https://cdn.slidesharecdn.com/ss_thumbnails/securerest-180418180006-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 From Monolith to micro-services and back : The Self Contained Systems /slideshow/from-monolith-to-microservices-and-back-the-self-contained-systems/81810847 scs-171109155301
Monoliths aren't bad in all situations, but in larger projects, it is desirable to work in a more modular way. But microservices bring a lot of complexity which is maybe not always desired or needed. Self-contained Systems, which are autonomous web applications, are an ideal way to make your large application manageable by multiple teams. This session will make a comparison between the 3 architectural styles, monoliths, micro-services and Self-Contained Systems highlighting their strengths and their weaknesses. ]]>
Monoliths aren't bad in all situations, but in larger projects, it is desirable to work in a more modular way. But microservices bring a lot of complexity which is maybe not always desired or needed. Self-contained Systems, which are autonomous web applications, are an ideal way to make your large application manageable by multiple teams. This session will make a comparison between the 3 architectural styles, monoliths, micro-services and Self-Contained Systems highlighting their strengths and their weaknesses. ]]> Thu, 09 Nov 2017 15:53:01 GMT /slideshow/from-monolith-to-microservices-and-back-the-self-contained-systems/81810847 rdebusscher@slideshare.net(rdebusscher) From Monolith to micro-services and back : The Self Contained Systems rdebusscher Monoliths aren't bad in all situations, but in larger projects, it is desirable to work in a more modular way. But microservices bring a lot of complexity which is maybe not always desired or needed. Self-contained Systems, which are autonomous web applications, are an ideal way to make your large application manageable by multiple teams. This session will make a comparison between the 3 architectural styles, monoliths, micro-services and Self-Contained Systems highlighting their strengths and their weaknesses. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/scs-171109155301-thumbnail.jpg?width=120&height=120&fit=bounds" /> Monoliths aren't bad in all situations, but in larger projects, it is desirable to work in a more modular way. But microservices bring a lot of complexity which is maybe not always desired or needed. Self-contained Systems, which are autonomous web applications, are an ideal way to make your large application manageable by multiple teams. This session will make a comparison between the 3 architectural styles, monoliths, micro-services and Self-Contained Systems highlighting their strengths and their weaknesses.

From Monolith to micro-services and back : The Self Contained Systems from Rudy De Busscher

]]> 607 1 https://cdn.slidesharecdn.com/ss_thumbnails/scs-171109155301-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Java EE Security API - JSR375: Getting Started /rdebusscher/java-ee-security-api-jsr375-getting-started jsr375-170619125643
The Java EE Security API (JSR-375) wants to simplify the implementation of security-related features in your Java EE application. Application server specific configuration changes will be no longer needed and things will be much more app developer friendly. Aligning security with the ease of development we saw in the recent version of Java EE. We will show you the basic goals and concepts behind Java EE Security API. And of course, demos with the current version of the RI, named Soteria, how you can do Authentication and Authorization.]]>
The Java EE Security API (JSR-375) wants to simplify the implementation of security-related features in your Java EE application. Application server specific configuration changes will be no longer needed and things will be much more app developer friendly. Aligning security with the ease of development we saw in the recent version of Java EE. We will show you the basic goals and concepts behind Java EE Security API. And of course, demos with the current version of the RI, named Soteria, how you can do Authentication and Authorization.]]> Mon, 19 Jun 2017 12:56:43 GMT /rdebusscher/java-ee-security-api-jsr375-getting-started rdebusscher@slideshare.net(rdebusscher) Java EE Security API - JSR375: Getting Started rdebusscher The Java EE Security API (JSR-375) wants to simplify the implementation of security-related features in your Java EE application. Application server specific configuration changes will be no longer needed and things will be much more app developer friendly. Aligning security with the ease of development we saw in the recent version of Java EE. We will show you the basic goals and concepts behind Java EE Security API. And of course, demos with the current version of the RI, named Soteria, how you can do Authentication and Authorization. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/jsr375-170619125643-thumbnail.jpg?width=120&height=120&fit=bounds" /> The Java EE Security API (JSR-375) wants to simplify the implementation of security-related features in your Java EE application. Application server specific configuration changes will be no longer needed and things will be much more app developer friendly. Aligning security with the ease of development we saw in the recent version of Java EE. We will show you the basic goals and concepts behind Java EE Security API. And of course, demos with the current version of the RI, named Soteria, how you can do Authentication and Authorization.

Java EE Security API - JSR375: Getting Started from Rudy De Busscher

]]> 2211 7 https://cdn.slidesharecdn.com/ss_thumbnails/jsr375-170619125643-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 What is tackled in the Java EE Security API (Java EE 8) /slideshow/what-is-tackled-in-the-java-ee-security-api-java-ee-8/69005284 statusjsr375-161115151721
The Java EE Security API (JSR-375) wants to simplify the implementation of security-related features in your Java EE application. Application server specific configuration changes will be no longer needed and things will be much more app developer friendly. Aligning security with the ease of development we saw in the recent version of Java EE. We will show you the basic goals and concepts behind Java EE Security API. And of course, demos with the current version of the RI, named Soteria, how you can do Authentication and Authorization.]]>
The Java EE Security API (JSR-375) wants to simplify the implementation of security-related features in your Java EE application. Application server specific configuration changes will be no longer needed and things will be much more app developer friendly. Aligning security with the ease of development we saw in the recent version of Java EE. We will show you the basic goals and concepts behind Java EE Security API. And of course, demos with the current version of the RI, named Soteria, how you can do Authentication and Authorization.]]> Tue, 15 Nov 2016 15:17:21 GMT /slideshow/what-is-tackled-in-the-java-ee-security-api-java-ee-8/69005284 rdebusscher@slideshare.net(rdebusscher) What is tackled in the Java EE Security API (Java EE 8) rdebusscher The Java EE Security API (JSR-375) wants to simplify the implementation of security-related features in your Java EE application. Application server specific configuration changes will be no longer needed and things will be much more app developer friendly. Aligning security with the ease of development we saw in the recent version of Java EE. We will show you the basic goals and concepts behind Java EE Security API. And of course, demos with the current version of the RI, named Soteria, how you can do Authentication and Authorization. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/statusjsr375-161115151721-thumbnail.jpg?width=120&height=120&fit=bounds" /> The Java EE Security API (JSR-375) wants to simplify the implementation of security-related features in your Java EE application. Application server specific configuration changes will be no longer needed and things will be much more app developer friendly. Aligning security with the ease of development we saw in the recent version of Java EE. We will show you the basic goals and concepts behind Java EE Security API. And of course, demos with the current version of the RI, named Soteria, how you can do Authentication and Authorization.

What is tackled in the Java EE Security API (Java EE 8) from Rudy De Busscher

]]> 18846 5 https://cdn.slidesharecdn.com/ss_thumbnails/statusjsr375-161115151721-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Java ee 8 + security overview /slideshow/java-ee-8-security-overview/52963520 javaee8security-150919124200-lva1-app6892
Java EE 8 Overview (Sept 2015). A lot of work is already done by the Expert Groups so lets have a brief look for what we can expect in the some areas. - Servlet 4 will embrace the new HTTP/2 protocol. - JSON-B will bring the same high level features of JAXB to the JSON data format. - Server-Sent Events(SSE) is the WebSocket variant where you only send data from the server to the client. - MVC will be the Action based MVC complement of the Component based MVC of JSF. - Some major restructuring of CDI so that we can use it standardised in Java SE to mention one thing. The Java EE security API will be covered in more detail. Security related things became old and dusty and needs to move away from proprietary configuration to be able to make the transition to the cloud. An introduction to JSR 375 is given, which promotes self-contained application portability across Java EE servers, and promotes the use of modern programming concepts such as Expression Language, and CDI. It will holistically attempt to simplify, standardize, and modernize the Security API across the platform in areas identified by the community. ]]>
Java EE 8 Overview (Sept 2015). A lot of work is already done by the Expert Groups so lets have a brief look for what we can expect in the some areas. - Servlet 4 will embrace the new HTTP/2 protocol. - JSON-B will bring the same high level features of JAXB to the JSON data format. - Server-Sent Events(SSE) is the WebSocket variant where you only send data from the server to the client. - MVC will be the Action based MVC complement of the Component based MVC of JSF. - Some major restructuring of CDI so that we can use it standardised in Java SE to mention one thing. The Java EE security API will be covered in more detail. Security related things became old and dusty and needs to move away from proprietary configuration to be able to make the transition to the cloud. An introduction to JSR 375 is given, which promotes self-contained application portability across Java EE servers, and promotes the use of modern programming concepts such as Expression Language, and CDI. It will holistically attempt to simplify, standardize, and modernize the Security API across the platform in areas identified by the community. ]]> Sat, 19 Sep 2015 12:42:00 GMT /slideshow/java-ee-8-security-overview/52963520 rdebusscher@slideshare.net(rdebusscher) Java ee 8 + security overview rdebusscher Java EE 8 Overview (Sept 2015). A lot of work is already done by the Expert Groups so lets have a brief look for what we can expect in the some areas. - Servlet 4 will embrace the new HTTP/2 protocol. - JSON-B will bring the same high level features of JAXB to the JSON data format. - Server-Sent Events(SSE) is the WebSocket variant where you only send data from the server to the client. - MVC will be the Action based MVC complement of the Component based MVC of JSF. - Some major restructuring of CDI so that we can use it standardised in Java SE to mention one thing. The Java EE security API will be covered in more detail. Security related things became old and dusty and needs to move away from proprietary configuration to be able to make the transition to the cloud. An introduction to JSR 375 is given, which promotes self-contained application portability across Java EE servers, and promotes the use of modern programming concepts such as Expression Language, and CDI. It will holistically attempt to simplify, standardize, and modernize the Security API across the platform in areas identified by the community. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/javaee8security-150919124200-lva1-app6892-thumbnail.jpg?width=120&height=120&fit=bounds" /> Java EE 8 Overview (Sept 2015). A lot of work is already done by the Expert Groups so lets have a brief look for what we can expect in the some areas. - Servlet 4 will embrace the new HTTP/2 protocol. - JSON-B will bring the same high level features of JAXB to the JSON data format. - Server-Sent Events(SSE) is the WebSocket variant where you only send data from the server to the client. - MVC will be the Action based MVC complement of the Component based MVC of JSF. - Some major restructuring of CDI so that we can use it standardised in Java SE to mention one thing. The Java EE security API will be covered in more detail. Security related things became old and dusty and needs to move away from proprietary configuration to be able to make the transition to the cloud. An introduction to JSR 375 is given, which promotes self-contained application portability across Java EE servers, and promotes the use of modern programming concepts such as Expression Language, and CDI. It will holistically attempt to simplify, standardize, and modernize the Security API across the platform in areas identified by the community.

Java ee 8 + security overview from Rudy De Busscher

]]> 3792 10 https://cdn.slidesharecdn.com/ss_thumbnails/javaee8security-150919124200-lva1-app6892-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Extending Arquillian graphene /rdebusscher/extending-arquillian-graphene extendinggraphene-150414052133-conversion-gate01
See also http://statelessprime.blogspot.co.at/2015/04/extending-arquillian-graphene.html With Arquillian Graphene, you can write tests which inspect the GUI of your web application (HTML based ones) right from within your familiar Unit Test code structure. And there are already many nice features available, but sometimes, you want to extend the concepts of Arquillian Graphene. So that you can write cleaner code in some use cases. The good thing is that you can achieve this quite easily due to the internal structure of the framework which uses 'Enricher's and Service extensions.]]>
See also http://statelessprime.blogspot.co.at/2015/04/extending-arquillian-graphene.html With Arquillian Graphene, you can write tests which inspect the GUI of your web application (HTML based ones) right from within your familiar Unit Test code structure. And there are already many nice features available, but sometimes, you want to extend the concepts of Arquillian Graphene. So that you can write cleaner code in some use cases. The good thing is that you can achieve this quite easily due to the internal structure of the framework which uses 'Enricher's and Service extensions.]]> Tue, 14 Apr 2015 05:21:33 GMT /rdebusscher/extending-arquillian-graphene rdebusscher@slideshare.net(rdebusscher) Extending Arquillian graphene rdebusscher See also http://statelessprime.blogspot.co.at/2015/04/extending-arquillian-graphene.html With Arquillian Graphene, you can write tests which inspect the GUI of your web application (HTML based ones) right from within your familiar Unit Test code structure. And there are already many nice features available, but sometimes, you want to extend the concepts of Arquillian Graphene. So that you can write cleaner code in some use cases. The good thing is that you can achieve this quite easily due to the internal structure of the framework which uses 'Enricher's and Service extensions. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/extendinggraphene-150414052133-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds" /> See also http://statelessprime.blogspot.co.at/2015/04/extending-arquillian-graphene.html With Arquillian Graphene, you can write tests which inspect the GUI of your web application (HTML based ones) right from within your familiar Unit Test code structure. And there are already many nice features available, but sometimes, you want to extend the concepts of Arquillian Graphene. So that you can write cleaner code in some use cases. The good thing is that you can achieve this quite easily due to the internal structure of the framework which uses 'Enricher's and Service extensions.

Extending Arquillian graphene from Rudy De Busscher

]]> 772 2 https://cdn.slidesharecdn.com/ss_thumbnails/extendinggraphene-150414052133-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 Octopus framework; Permission based security framework for Java EE /slideshow/octopus-framework-permission-basedn/33268202 octopusv0-140408070159-phpapp02
Octopus framework for using permission based security in your Java EE app capable of securing URL, JSF components and CDI and EJB methods with the same security voters.]]>
Octopus framework for using permission based security in your Java EE app capable of securing URL, JSF components and CDI and EJB methods with the same security voters.]]> Tue, 08 Apr 2014 07:01:58 GMT /slideshow/octopus-framework-permission-basedn/33268202 rdebusscher@slideshare.net(rdebusscher) Octopus framework; Permission based security framework for Java EE rdebusscher Octopus framework for using permission based security in your Java EE app capable of securing URL, JSF components and CDI and EJB methods with the same security voters. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/octopusv0-140408070159-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds" /> Octopus framework for using permission based security in your Java EE app capable of securing URL, JSF components and CDI and EJB methods with the same security voters.

Octopus framework; Permission based security framework for Java EE from Rudy De Busscher

]]> 1671 2 https://cdn.slidesharecdn.com/ss_thumbnails/octopusv0-140408070159-phpapp02-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post

http://activitystrea.ms/schema/1.0/posted

0 https://cdn.slidesharecdn.com/profile-photo-rdebusscher-48x48.jpg?cb=1688106931 Senior Developer who loves to create web applications with the Jakarta EE/MicroProfile platform. I find it very important to deliver good quality code and designs and thus unit and integration testing are very important to me. www.atbash.be https://cdn.slidesharecdn.com/ss_thumbnails/jakarta-integration-testing-230419173212-a86fcea7-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/jakartaintegrationtestingpdf/257475646 jakarta-integration-te... https://cdn.slidesharecdn.com/ss_thumbnails/core-profilejakartaone2022-221206115205-f72c1cc3-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/coreprofilejakartaone2022pdf/254776814 core-profile_jakartaOn... https://cdn.slidesharecdn.com/ss_thumbnails/microstream-withoutdatabase-220920150402-f9516bac-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/microstreamwithoutdatabasepdf/253065475 MicroStream-WithoutDat...