Presentation given at Oracle Groundbreakers APAC Tour 2020 talk.
Find corresponding code sample at: https://github.com/svenbernhardt/employee-service-helidon-se
Cloud-native is the way new applications should be built today. It doesn't matter here, if the application is going to be deployed in the Cloud or On-prem. The most important thing is that an application is applicable for getting the most out of the Cloud with respect to efficiency. APIs and Containers are essential building blocks of Cloud-native applications. As Cloud-native apps are driven by APIs, the development of such an app should start with defining the API in an API design-first approach.
Within this session I'll give further insights into what makes Cloud-native development different from classical app development. Furthermore, we'll go through the respective development steps (API design, Service development, Deployment to OCI, API exposure) to make the session more practical. For exposing the app to the outside world OCI API Gateway will be used. The development of the Cloud-native app is done using Oracle's Microservice framework Helidon.
Cloud-native Integration in the Oracle CloudSven Bernhardt
Integration matters today, more than ever! Integration is essential to adapt new concepts, like AI and ML and allows enterprises to turn their owned data into value. But integration is not simple, it is complex and needs to be capable to deal with rapidly changing requirements.
Within in this session we’ll look into Oracle Cloud Infrastructure integration capabilities and will learn how integration solutions can be build based on services like API Gateway, Kubernetes (OKE) or OCI Streaming.
Implementing API-led Cloud-native apps on OCISven Bernhardt
Session was held at DOAG 2020 Online edition!
Cloud-native is the way new applications should be built today. It doesn’t matter here, if the application is going to be deployed in the Cloud or On-prem. The most important thing is that an application is applicable for getting the most out of the Cloud with respect to efficiency. APIs and Containers are essential building blocks of Cloud-native applications. As Cloud-native apps are driven by APIs, the development of such an app should start with defining the API in an API design-first approach.
Within this session I’ll give further insights into what makes Cloud-native development different from classical app development. Furthermore, we’ll go through the respective development steps (API design, Service development, Deployment to OCI, API exposure) to make the session more practical. For exposing the app to the outside world OCI API Gateway will be used. The development of the Cloud-native app is done using Oracle’s Microservice framework Helidon.
Cloud-native Integration in the Oracle CloudSven Bernhardt
Presentation held on DOAG 2020 Online edition
The world is hybrid! So, from my perspective Cloud-native is the way new applications should be built today, no matter the context or the problem to solve. With respect to integration architectures this means that we need to rethink the way integration architectures should be built using the advantages and benefits of arising technologies to tackle new challenges in the integration space, like dynamic, unpredictable workloads. The good new is: The patterns stay the same!
Within this session, I’ll go through the components of a modern integration stack based on Oracle Cloud Infrastructure (API Gateway, Streaming, Functions, OKE, …) and how those components might be combined to create flexible, robust and sustainable integration solutions.
API Gateway or Service Mesh - Complementary or excluding conceptsSven Bernhardt
Presentation slides from DOAG conference 2020.
API Gateway are already around for a while. With the rise of Microservices architectures and highly distributed architectures, new concepts like Service meshes arise. Since Service mesh and API Gateway implementations seem to have similar functionalities, we have to deal with questions wether to use the one or the other. But is it really an “or”? Maybe is it just another fallacy?
In this session, I’ll explain basic concepts, common functionalities and differences for both concepts, to answer the question, if it’s complementary or excluding concepts? To make this session more practical, it’ll be supported by coding examples where certain aspects of the talk are shown based on Cloud-native example app that run upon OCI.
Intuitive APIs are critical success factors for modern software architectures. APIs should be easy to use, difficult to misuse, consumer friendly, easy to maintain and consistently designed. In order to achieve these goals, it is important to develop APIs before starting the actual development and in a collaborative approach involving various stakeholders. The API-first design approach is important when it comes to exposing existing functionality in the enterprise, e.g. implemented as microservices, to the outside world. But what role do APIs play in microservice architectures? How are APIs and microservices implementations combined and how do I integrate this with a DevOps approach? These questions will be answered in this session and explained on a consistent Microservice example. From a tooling perspective I leverage the power of Oracle Cloud with tools like Apiary, Oracle Kubernetes Engine (OKE), Wercker (aka Container Pipelines) and Oracle Container Registry.
Kallos Solutions specializes in providing world class enterprise software products and custom solutions for your business. With Kallos, you get innovative and proven enterprise applications at superior value – in terms of price, speed, depth of functionality, scalability and quality.
With its own range of products, a powerful solution delivery platform, and an innovative ‘see what you get early’ methodology, you virtually eliminate risk in implementing such solutions.
In the Java environment, Springboot is usually the default framework when it comes to implementing microservices. But also the Java Enterprise Community does not sleep and opposes the new frameworks on the basis of microprofiles, whereby the development of microservices using JEE standards cloud-native, without bloated AppServers, is possible.
A relatively young framework in this ranks is Helidon. It is interesting to note that the framework comes in two variants, a Micorprofile-based (MP) and a function-based (SE) variant, which makes it interesting for different applications. In addition to this differentiating feature, Helidon convinces with out-of-the-box build support (Maven). Features can be enabled simply by adding new Maven dependencies. Furthermore, Kubernetes is the native target platform for services implemented in Helidon.
The session provides an introduction to the basic idea of the framework, compares the two development approaches and compares the framework with other established solutions in terms of its suitability for everyday use.
Service integration made easy with Open Source KumaSven Bernhardt
Cloud-native application design is the new default. Cloud-native applications are often organized as a collection of independent and loosely-coupled services, allowing for more flexibility and agility with respect to changing business requirements. Application runtimes become hybrid at the same time, so we have to deal with distributed cloud and on-prem workloads. This makes the world even more complex from connectivity perspective, since services forming an application need to interact with each other, with already existing monolithic applications and this both on-prem and in the cloud.
As we can see, there’s a lot of network communication involved and since the network needs to be considered unsecure, it must be ensured that it happens in a secure, reliable and comprehensible way. Since efficiency and agility is a critical factor nowadays, we need new , modern approaches which allows development teams to act act autonomously while being able to focus on the important things at the same time.
A service mesh like Kuma can help you to address the arising challenges in the area of security, connectivity and observability transparently by moving the responsibility from the application to the infrastructure layer. At the same time, a service mesh gives a self service path to development teams for implementing respective requirements more efficiently. This means an extension to traditional connectivity handling approaches, where traffic is restricted by firewall rules and explicit knowledge from a network team is needed. This allows for implementing business requirements more efficiently and more flexible with respect to connectivity and reliability.
This session gives an introduction to Kuma, how it is different from other service mesh implementations and shows how easy it is to get started with it.
Cloud-native Integration in the Oracle CloudSven Bernhardt
Integration matters today, more than ever! Integration is essential to adapt new concepts, like AI and ML and allows enterprises to turn their owned data into value. But integration is not simple, it is complex and needs to be capable to deal with rapidly changing requirements.
Within in this session we’ll look into Oracle Cloud Infrastructure integration capabilities and will learn how integration solutions can be build based on services like API Gateway, Kubernetes (OKE) or OCI Streaming.
Implementing API-led Cloud-native apps on OCISven Bernhardt
Session was held at DOAG 2020 Online edition!
Cloud-native is the way new applications should be built today. It doesn’t matter here, if the application is going to be deployed in the Cloud or On-prem. The most important thing is that an application is applicable for getting the most out of the Cloud with respect to efficiency. APIs and Containers are essential building blocks of Cloud-native applications. As Cloud-native apps are driven by APIs, the development of such an app should start with defining the API in an API design-first approach.
Within this session I’ll give further insights into what makes Cloud-native development different from classical app development. Furthermore, we’ll go through the respective development steps (API design, Service development, Deployment to OCI, API exposure) to make the session more practical. For exposing the app to the outside world OCI API Gateway will be used. The development of the Cloud-native app is done using Oracle’s Microservice framework Helidon.
Cloud-native Integration in the Oracle CloudSven Bernhardt
Presentation held on DOAG 2020 Online edition
The world is hybrid! So, from my perspective Cloud-native is the way new applications should be built today, no matter the context or the problem to solve. With respect to integration architectures this means that we need to rethink the way integration architectures should be built using the advantages and benefits of arising technologies to tackle new challenges in the integration space, like dynamic, unpredictable workloads. The good new is: The patterns stay the same!
Within this session, I’ll go through the components of a modern integration stack based on Oracle Cloud Infrastructure (API Gateway, Streaming, Functions, OKE, …) and how those components might be combined to create flexible, robust and sustainable integration solutions.
API Gateway or Service Mesh - Complementary or excluding conceptsSven Bernhardt
Presentation slides from DOAG conference 2020.
API Gateway are already around for a while. With the rise of Microservices architectures and highly distributed architectures, new concepts like Service meshes arise. Since Service mesh and API Gateway implementations seem to have similar functionalities, we have to deal with questions wether to use the one or the other. But is it really an “or”? Maybe is it just another fallacy?
In this session, I’ll explain basic concepts, common functionalities and differences for both concepts, to answer the question, if it’s complementary or excluding concepts? To make this session more practical, it’ll be supported by coding examples where certain aspects of the talk are shown based on Cloud-native example app that run upon OCI.
Intuitive APIs are critical success factors for modern software architectures. APIs should be easy to use, difficult to misuse, consumer friendly, easy to maintain and consistently designed. In order to achieve these goals, it is important to develop APIs before starting the actual development and in a collaborative approach involving various stakeholders. The API-first design approach is important when it comes to exposing existing functionality in the enterprise, e.g. implemented as microservices, to the outside world. But what role do APIs play in microservice architectures? How are APIs and microservices implementations combined and how do I integrate this with a DevOps approach? These questions will be answered in this session and explained on a consistent Microservice example. From a tooling perspective I leverage the power of Oracle Cloud with tools like Apiary, Oracle Kubernetes Engine (OKE), Wercker (aka Container Pipelines) and Oracle Container Registry.
Kallos Solutions specializes in providing world class enterprise software products and custom solutions for your business. With Kallos, you get innovative and proven enterprise applications at superior value – in terms of price, speed, depth of functionality, scalability and quality.
With its own range of products, a powerful solution delivery platform, and an innovative ‘see what you get early’ methodology, you virtually eliminate risk in implementing such solutions.
In the Java environment, Springboot is usually the default framework when it comes to implementing microservices. But also the Java Enterprise Community does not sleep and opposes the new frameworks on the basis of microprofiles, whereby the development of microservices using JEE standards cloud-native, without bloated AppServers, is possible.
A relatively young framework in this ranks is Helidon. It is interesting to note that the framework comes in two variants, a Micorprofile-based (MP) and a function-based (SE) variant, which makes it interesting for different applications. In addition to this differentiating feature, Helidon convinces with out-of-the-box build support (Maven). Features can be enabled simply by adding new Maven dependencies. Furthermore, Kubernetes is the native target platform for services implemented in Helidon.
The session provides an introduction to the basic idea of the framework, compares the two development approaches and compares the framework with other established solutions in terms of its suitability for everyday use.
Service integration made easy with Open Source KumaSven Bernhardt
Cloud-native application design is the new default. Cloud-native applications are often organized as a collection of independent and loosely-coupled services, allowing for more flexibility and agility with respect to changing business requirements. Application runtimes become hybrid at the same time, so we have to deal with distributed cloud and on-prem workloads. This makes the world even more complex from connectivity perspective, since services forming an application need to interact with each other, with already existing monolithic applications and this both on-prem and in the cloud.
As we can see, there’s a lot of network communication involved and since the network needs to be considered unsecure, it must be ensured that it happens in a secure, reliable and comprehensible way. Since efficiency and agility is a critical factor nowadays, we need new , modern approaches which allows development teams to act act autonomously while being able to focus on the important things at the same time.
A service mesh like Kuma can help you to address the arising challenges in the area of security, connectivity and observability transparently by moving the responsibility from the application to the infrastructure layer. At the same time, a service mesh gives a self service path to development teams for implementing respective requirements more efficiently. This means an extension to traditional connectivity handling approaches, where traffic is restricted by firewall rules and explicit knowledge from a network team is needed. This allows for implementing business requirements more efficiently and more flexible with respect to connectivity and reliability.
This session gives an introduction to Kuma, how it is different from other service mesh implementations and shows how easy it is to get started with it.
Intuitive APIs are critical success factors for modern software architectures. APIs should be easy to use, difficult to misuse, consumer friendly, easy to maintain and consistently designed.
In order to achieve these goals, it is important to develop APIs before starting the actual development and in a collaborative approach involving various stakeholders. This API-first design approach is important when it comes to exposing existing functionality in the enterprise, e.g. implemented as microservices, to the outside world.
But what role do APIs play in microservice architectures? How are API and Microservice implementations combined and how do I integrate them with a DevOps approach?
Questions answered in this session. A holistic development approach starting with API development up to the deployment of a microservice is considered. Tools such as Oracle Apiary, which support an API-first design approach or Oracle Wercker for the automation of build and deployment, will be presented.
Integration is as relevant as ever. Change seems to be omnipresent and software architectures are constantly evolving together with technologies, concepts and tooling. As a result of companies leveraging available Cloud technologies we are now dealing with elastic infrastructures and hybrid application ecosystems, which means that on-Premises systems and Cloud services need to be integrated, giving way to added complexity. Moreover, to unlock data and functionality in a scalable and secure manner, integration strategies must be consistent with an API-first design. When it comes to concerns such as decoupling, performance or availability, it must be possible to scale distinct components within the integration infrastructure independently. Ideally, these components should be able to deploy and run isolated from each other to ensure the system’s resiliency and flexibility, since the components are not influencing or dependent on each other.
This presentation will take you on a little time journey while discussing the role and relevancy of integration architectures, key patterns and their evolution (Publish/Subscribe, Event Sourcing, CQRS) as well as the way how those should be implemented today. Are we still talking about monolithic integration platforms or is there a new kid on the block, more lightweight, following a Microservices architectural style?
API-first design - Basis for an consistent API-Management approachSven Bernhardt
Intuitive API design is a critical success factor for APIs. API-First propagates a collaborative approach, where API development starts with the design and brings various stakeholders together, which dramatically increases efficiency and consistency while defining APIs. Questions that that come up in this area are about quality requirements APIs have to meet nowadays, in order to deliver the desired business value. In this session we want to present an approach how APIs can be defined and implemented consistently using tools like Apiary and Apimatic and the design artifacts can be incorporated in existing CI/CD pipelines, using tools like Dredd, since APIs are a first-class citizen which need to be maintained appropriately.
From EAI to Serverless - Evolution of integration architecturesSven Bernhardt
Integration is still relevant. Change is ubiquitous and software architectures must constantly evolve. The adaptation of new technologies, concepts and tools is necessary in order to be flexible with regard to new requirements. Many companies use available cloud technologies for this purpose. This leads to elastic infrastructures and hybrid application ecosystems; on-premise systems and cloud services must be integrated, leading to increased complexity. To open up new sales channels, enterprise data and functions are made accessible to third parties in a scalable and secure manner.
How can the resulting requirements for decoupling, performance or availability be met within the framework of a future-proof, scalable integration infrastructure that is also fault tolerant and highly fail-safe?
This presentation takes you on a short journey through time and discusses the role and relevance of integration architectures, key patterns and their development (publish/subscribe, event sourcing, CQRS) as well as the way they should be implemented today. Are we still talking about monolithic integration platforms or is there a "New Kid on the Block" that is lightweight and follows an architectural style of Microservices?
Getting to the Next Level with Eclipse Concierge - Jan Rellermeyer + Tim Verb...mfrancis
OSGi Community Event 2016 Presentation by Jan Rellermeyer (IBM), Tim Verbelen (imec) & Jochen Hiller (Deutsche Telekom AG)
Eclipse Concierge provides a clean, small and lightweight implementation of the OSGi core framework specification, specifically tailored to embedded systems and IoT. In this talk, we will cover how to use and deploy the Concierge OSGi framework (e.g. using OSGi enRoute), and discuss many of the new and upcoming features in the Concierge project such as the OSGi REST interface and Cloud Ecosystems reference implementations. We will also present our work in progress on implementing the OSGi R6 core specification level and novel demonstrations that illustrate the advantages of having a lean and streamlined OSGi implementation to deal with deployment and dynamism in IoT applications.
The importance of APIs is increasing. Usually, API projects do not start on a green field. Often there's an existing, mostly monolithic application landscape, which needs to be embedded and integrated with new applications implemented in a Cloud-native fashion on new technologies like Kubernetes. The question is: Which principles must be considered to build a future-oriented, flexible API management platform? It is potentially not enough to simply work with a central, monolithic API gateway solutions. But, what requirements are placed on a modern API management platform? This session will give an introduction on how modern API architectures should be build, considering concepts like Microgateways, Ingress and Servicemesh.
OSGi & Java in Industrial IoT - More than a Solid Trend - Essential to Scale ...mfrancis
OSGi Community Event 2016 Keynote Presentation by Robert Andres (Eurotech) & Walter Hofmann (Hitachi High Technologies)
With the promise of “real” IoT, the requirements for computational capabilities and agility at the edge demand IT-centric architectures and solutions that are based on open and industry standards. “IoT stacks” that are built on OSGi and Java’s solid foundation ensure effective modular software development and management on abstracted hardware.
Total cost of ownership in these IoT solutions matters a lot more than the simple combined hardware and software cost per edge node. Sophisticated software elements – including business intelligence tools, databases, and analytics packages – leverage data remotely and centrally to achieve the best results for customers. A perfect example of an analytics solution using such an approach is the predictive maintenance solution that Hitachi offers, leveraging Eurotech’s IoT hardware and software building blocks that heavily rely on OSGi.
Quarkus is the new and shiny Kubernetes native framework that promises to solve everything you ever wanted. But what is the truth out there? How do some real-world scenarios look like and what is it really used for?
API Gateway or Service mesh - Complementary or excluding conceptsSven Bernhardt
API Gateway are already around for a while. With the rise of Microservices architectures and highly distributed architectures, new concepts like Service meshes arise. Since Service mesh and API Gateway implementations seem to have similar functionalities, we have to deal with questions wether to use the one or the other. But is it really an “or”? Maybe is it just another fallacy?
In this session, I’ll explain basic concepts, common functionalities and differences for both concepts, to answer the question, if it’s complementary or excluding concepts? To make this session more practical, it’ll be supported by coding examples where certain aspects of the talk are shown based on Cloud-native example app that run upon OCI.
apidays LIVE Paris 2021 - Edge Side APIs by Kevin Dunglas, Les Tilleulsapidays
apidays LIVE Paris 2021 - APIs and the Future of Software
December 7, 8 & 9, 2021
Edge Side APIs: Fast and Reliable Hypermedia APIs
Kevin Dunglas, CEO at Les Tilleuls & Creator of APIPlatform, Vulcain, and Mercure Protocole
"はじめてのKong Konnect" APIゲートウェイと Service Meshについて学ぼう! Junji Nishihara
Kong Konnectの基礎を知っていただくために"はじめてのKong Konnect"オンラインミートアップを開催します
今回はAPIゲートウェイとService Mesh。そのデザインパターンの違いと関係性、なぜAPIの管理とService Meshは異なるユースケースを補完するパターンなのか、について解説します
Kong Konnectは、API Gateway(APIゲートウェイ)、Service Mesh(サービスメッシュ)、およびIngress(イングレス)を統合して、APIライフサイクル全体にわたってエンドツーエンドのサービス接続を提供するAPIサービスコネクティビティプラットフォームです。これは、アプリケーション内のサービス間、ないしはアプリケーション間でエンドツーエンドの接続を提供し、エッジでサービスを公開する唯一のプラットフォームです
Kong Konnectは、オンプレミス、クラウド、VM、Container(コンテナ)さらにはkubernetesなど、あらゆるプラットフォーム、そしてREST、GraphQL、gRPC、Kafkaなどの最新のプロトコルを介してサービスを接続します。Hybrid Cloud(ハイブリッドクラウド構成)やMulti Cloud(マルチクラウド構成)など、あらゆるインフラストラクチャおよびあらゆる展開パターンにわたって100%一貫した方法で展開できます
Kong Konnectメリット
APIゲートウェイからService Meshに至るまで一貫したポリシー適用/オペレーションにより、セキュアなAPIサービスコネクティビティを展開
あらゆるインフラストラクチャをサポート、ベンダーロックインからの解放
Kong Konnectライセンスは本番/開発環境、ノードなどの数にかかわらず、API数とAPIコール数のみで算出。APIシステム全体のコストを最適化
Test-Driven Cloud Development with Oracle SOA Cloud Service and Oracle Develo...Sven Bernhardt
Automated tests are key for quality assurance and for ensuring business agility from a long-term perspective. That is especially important in complex integration projects if you develop your integrations on-premises or in the cloud. If a hybrid strategy is used, it is important to have a consistent testing approach for cloud and on-premises. In this session learn how to implement a consistent approach based on Oracle SOA Cloud Service that works on-premises and in the cloud. See how this approach can test BPEL, BPMN, SB, Java, human tasks, XSLT, and XQuery across all relevant test layers (elementary unit tests, component tests, end-to-end tests) consistently.
[WSO2Con EU 2018] OpenAPI Specification 3 - The Evolution of SwaggerWSO2
Swagger is the de facto standard for API description. It has evolved into a new version specified by the Open API Initiative under the umbrella of the Linux Foundation. This presentation explores improvements and new features that will help you to define even better APIs. A sample using Apache CXF, Spring Boot and WSO2 API Manager illustrates the benefits of implementing OpenAPI Specification 3.
Implementing API-led Cloud-native apps on OCISven Bernhardt
Presentation held at AIOUG Sangam 2020
Cloud-native is the way new applications should be built today. It doesn’t matter here, if the application is going to be deployed in the Cloud or On-prem. The most important thing is that an application is applicable for getting the most out of the Cloud with respect to efficiency. APIs and Containers are essential building blocks of Cloud-native applications. As Cloud-native apps are driven by APIs, the development of such an app should start with defining the API in an API design-first approach.
Within this session I’ll give further insights into what makes Cloud-native development different from classical app development. Furthermore, we’ll go through the respective development steps (API design, Service development, Deployment to OCI, API exposure) to make the session more practical. For exposing the app to the outside world OCI API Gateway will be used. The development of the Cloud-native app is done using Oracle’s Microservice framework Helidon.
Cloud-native Application Development on OCISven Bernhardt
Presentation delivered at DOAG 2022
Abstract:
Building applications in a Cloud-native way is the new normal, since the world is hybrid nowadays. Cloud-native applications are flexible, scalable and portable from On-prem environment to any Cloud platform as well as between different Cloud-vendor platforms without changing the actual implementation. This session will look at the key characteristics of Cloud-native applications and what this means for enterprises. In this session, I'll also give an overview on OCI and the provided Cloud-native apps development platform. In addition, I'll demo developing and running Cloud-native apps in OCI and will introduce the relevant Services.
Intuitive APIs are critical success factors for modern software architectures. APIs should be easy to use, difficult to misuse, consumer friendly, easy to maintain and consistently designed.
In order to achieve these goals, it is important to develop APIs before starting the actual development and in a collaborative approach involving various stakeholders. This API-first design approach is important when it comes to exposing existing functionality in the enterprise, e.g. implemented as microservices, to the outside world.
But what role do APIs play in microservice architectures? How are API and Microservice implementations combined and how do I integrate them with a DevOps approach?
Questions answered in this session. A holistic development approach starting with API development up to the deployment of a microservice is considered. Tools such as Oracle Apiary, which support an API-first design approach or Oracle Wercker for the automation of build and deployment, will be presented.
Integration is as relevant as ever. Change seems to be omnipresent and software architectures are constantly evolving together with technologies, concepts and tooling. As a result of companies leveraging available Cloud technologies we are now dealing with elastic infrastructures and hybrid application ecosystems, which means that on-Premises systems and Cloud services need to be integrated, giving way to added complexity. Moreover, to unlock data and functionality in a scalable and secure manner, integration strategies must be consistent with an API-first design. When it comes to concerns such as decoupling, performance or availability, it must be possible to scale distinct components within the integration infrastructure independently. Ideally, these components should be able to deploy and run isolated from each other to ensure the system’s resiliency and flexibility, since the components are not influencing or dependent on each other.
This presentation will take you on a little time journey while discussing the role and relevancy of integration architectures, key patterns and their evolution (Publish/Subscribe, Event Sourcing, CQRS) as well as the way how those should be implemented today. Are we still talking about monolithic integration platforms or is there a new kid on the block, more lightweight, following a Microservices architectural style?
API-first design - Basis for an consistent API-Management approachSven Bernhardt
Intuitive API design is a critical success factor for APIs. API-First propagates a collaborative approach, where API development starts with the design and brings various stakeholders together, which dramatically increases efficiency and consistency while defining APIs. Questions that that come up in this area are about quality requirements APIs have to meet nowadays, in order to deliver the desired business value. In this session we want to present an approach how APIs can be defined and implemented consistently using tools like Apiary and Apimatic and the design artifacts can be incorporated in existing CI/CD pipelines, using tools like Dredd, since APIs are a first-class citizen which need to be maintained appropriately.
From EAI to Serverless - Evolution of integration architecturesSven Bernhardt
Integration is still relevant. Change is ubiquitous and software architectures must constantly evolve. The adaptation of new technologies, concepts and tools is necessary in order to be flexible with regard to new requirements. Many companies use available cloud technologies for this purpose. This leads to elastic infrastructures and hybrid application ecosystems; on-premise systems and cloud services must be integrated, leading to increased complexity. To open up new sales channels, enterprise data and functions are made accessible to third parties in a scalable and secure manner.
How can the resulting requirements for decoupling, performance or availability be met within the framework of a future-proof, scalable integration infrastructure that is also fault tolerant and highly fail-safe?
This presentation takes you on a short journey through time and discusses the role and relevance of integration architectures, key patterns and their development (publish/subscribe, event sourcing, CQRS) as well as the way they should be implemented today. Are we still talking about monolithic integration platforms or is there a "New Kid on the Block" that is lightweight and follows an architectural style of Microservices?
Getting to the Next Level with Eclipse Concierge - Jan Rellermeyer + Tim Verb...mfrancis
OSGi Community Event 2016 Presentation by Jan Rellermeyer (IBM), Tim Verbelen (imec) & Jochen Hiller (Deutsche Telekom AG)
Eclipse Concierge provides a clean, small and lightweight implementation of the OSGi core framework specification, specifically tailored to embedded systems and IoT. In this talk, we will cover how to use and deploy the Concierge OSGi framework (e.g. using OSGi enRoute), and discuss many of the new and upcoming features in the Concierge project such as the OSGi REST interface and Cloud Ecosystems reference implementations. We will also present our work in progress on implementing the OSGi R6 core specification level and novel demonstrations that illustrate the advantages of having a lean and streamlined OSGi implementation to deal with deployment and dynamism in IoT applications.
The importance of APIs is increasing. Usually, API projects do not start on a green field. Often there's an existing, mostly monolithic application landscape, which needs to be embedded and integrated with new applications implemented in a Cloud-native fashion on new technologies like Kubernetes. The question is: Which principles must be considered to build a future-oriented, flexible API management platform? It is potentially not enough to simply work with a central, monolithic API gateway solutions. But, what requirements are placed on a modern API management platform? This session will give an introduction on how modern API architectures should be build, considering concepts like Microgateways, Ingress and Servicemesh.
OSGi & Java in Industrial IoT - More than a Solid Trend - Essential to Scale ...mfrancis
OSGi Community Event 2016 Keynote Presentation by Robert Andres (Eurotech) & Walter Hofmann (Hitachi High Technologies)
With the promise of “real” IoT, the requirements for computational capabilities and agility at the edge demand IT-centric architectures and solutions that are based on open and industry standards. “IoT stacks” that are built on OSGi and Java’s solid foundation ensure effective modular software development and management on abstracted hardware.
Total cost of ownership in these IoT solutions matters a lot more than the simple combined hardware and software cost per edge node. Sophisticated software elements – including business intelligence tools, databases, and analytics packages – leverage data remotely and centrally to achieve the best results for customers. A perfect example of an analytics solution using such an approach is the predictive maintenance solution that Hitachi offers, leveraging Eurotech’s IoT hardware and software building blocks that heavily rely on OSGi.
Quarkus is the new and shiny Kubernetes native framework that promises to solve everything you ever wanted. But what is the truth out there? How do some real-world scenarios look like and what is it really used for?
API Gateway or Service mesh - Complementary or excluding conceptsSven Bernhardt
API Gateway are already around for a while. With the rise of Microservices architectures and highly distributed architectures, new concepts like Service meshes arise. Since Service mesh and API Gateway implementations seem to have similar functionalities, we have to deal with questions wether to use the one or the other. But is it really an “or”? Maybe is it just another fallacy?
In this session, I’ll explain basic concepts, common functionalities and differences for both concepts, to answer the question, if it’s complementary or excluding concepts? To make this session more practical, it’ll be supported by coding examples where certain aspects of the talk are shown based on Cloud-native example app that run upon OCI.
apidays LIVE Paris 2021 - Edge Side APIs by Kevin Dunglas, Les Tilleulsapidays
apidays LIVE Paris 2021 - APIs and the Future of Software
December 7, 8 & 9, 2021
Edge Side APIs: Fast and Reliable Hypermedia APIs
Kevin Dunglas, CEO at Les Tilleuls & Creator of APIPlatform, Vulcain, and Mercure Protocole
"はじめてのKong Konnect" APIゲートウェイと Service Meshについて学ぼう! Junji Nishihara
Kong Konnectの基礎を知っていただくために"はじめてのKong Konnect"オンラインミートアップを開催します
今回はAPIゲートウェイとService Mesh。そのデザインパターンの違いと関係性、なぜAPIの管理とService Meshは異なるユースケースを補完するパターンなのか、について解説します
Kong Konnectは、API Gateway(APIゲートウェイ)、Service Mesh(サービスメッシュ)、およびIngress(イングレス)を統合して、APIライフサイクル全体にわたってエンドツーエンドのサービス接続を提供するAPIサービスコネクティビティプラットフォームです。これは、アプリケーション内のサービス間、ないしはアプリケーション間でエンドツーエンドの接続を提供し、エッジでサービスを公開する唯一のプラットフォームです
Kong Konnectは、オンプレミス、クラウド、VM、Container(コンテナ)さらにはkubernetesなど、あらゆるプラットフォーム、そしてREST、GraphQL、gRPC、Kafkaなどの最新のプロトコルを介してサービスを接続します。Hybrid Cloud(ハイブリッドクラウド構成)やMulti Cloud(マルチクラウド構成)など、あらゆるインフラストラクチャおよびあらゆる展開パターンにわたって100%一貫した方法で展開できます
Kong Konnectメリット
APIゲートウェイからService Meshに至るまで一貫したポリシー適用/オペレーションにより、セキュアなAPIサービスコネクティビティを展開
あらゆるインフラストラクチャをサポート、ベンダーロックインからの解放
Kong Konnectライセンスは本番/開発環境、ノードなどの数にかかわらず、API数とAPIコール数のみで算出。APIシステム全体のコストを最適化
Test-Driven Cloud Development with Oracle SOA Cloud Service and Oracle Develo...Sven Bernhardt
Automated tests are key for quality assurance and for ensuring business agility from a long-term perspective. That is especially important in complex integration projects if you develop your integrations on-premises or in the cloud. If a hybrid strategy is used, it is important to have a consistent testing approach for cloud and on-premises. In this session learn how to implement a consistent approach based on Oracle SOA Cloud Service that works on-premises and in the cloud. See how this approach can test BPEL, BPMN, SB, Java, human tasks, XSLT, and XQuery across all relevant test layers (elementary unit tests, component tests, end-to-end tests) consistently.
[WSO2Con EU 2018] OpenAPI Specification 3 - The Evolution of SwaggerWSO2
Swagger is the de facto standard for API description. It has evolved into a new version specified by the Open API Initiative under the umbrella of the Linux Foundation. This presentation explores improvements and new features that will help you to define even better APIs. A sample using Apache CXF, Spring Boot and WSO2 API Manager illustrates the benefits of implementing OpenAPI Specification 3.
Implementing API-led Cloud-native apps on OCISven Bernhardt
Presentation held at AIOUG Sangam 2020
Cloud-native is the way new applications should be built today. It doesn’t matter here, if the application is going to be deployed in the Cloud or On-prem. The most important thing is that an application is applicable for getting the most out of the Cloud with respect to efficiency. APIs and Containers are essential building blocks of Cloud-native applications. As Cloud-native apps are driven by APIs, the development of such an app should start with defining the API in an API design-first approach.
Within this session I’ll give further insights into what makes Cloud-native development different from classical app development. Furthermore, we’ll go through the respective development steps (API design, Service development, Deployment to OCI, API exposure) to make the session more practical. For exposing the app to the outside world OCI API Gateway will be used. The development of the Cloud-native app is done using Oracle’s Microservice framework Helidon.
Cloud-native Application Development on OCISven Bernhardt
Presentation delivered at DOAG 2022
Abstract:
Building applications in a Cloud-native way is the new normal, since the world is hybrid nowadays. Cloud-native applications are flexible, scalable and portable from On-prem environment to any Cloud platform as well as between different Cloud-vendor platforms without changing the actual implementation. This session will look at the key characteristics of Cloud-native applications and what this means for enterprises. In this session, I'll also give an overview on OCI and the provided Cloud-native apps development platform. In addition, I'll demo developing and running Cloud-native apps in OCI and will introduce the relevant Services.
API design-first allows the collaborative development of user-centric business APIs. In this context, the API specification is developed first and then the development of the frontend and backend can be started directly, whereby the API is mocked in the first step and feedback from the development is continuously incorporated into the specification. In order to do this efficiently, the delivery of specification changes needs to be as automated as possible, i.e. from spec change (commit) to deployment on the API gateway to publishing on the Dev Portal.
Presentation was delivered at Sangam21 (AIOUG)
API design-first allows the collaborative development of user-centric business APIs. In this context, the API specification is developed first and then the development of the frontend and backend can be started directly, whereby the API is mocked in the first step and feedback from the development is continuously incorporated into the specification. In order to do this efficiently, the delivery of specification changes needs to be as automated as possible, i.e. from spec change (commit) to deployment on the API gateway to publishing on the Dev Portal.
Building applications in a Cloud-native way is the new normal, since the world is hybrid nowadays. Cloud-native applications are flexible, scalable and portable from On-prem environment to any Cloud platform as well as between different Cloud-vendor platforms without changing the actual implementation. This session will look at the key characteristics of Cloud-native applications. In addition, I'll give an overview on OCI as a Cloud-native apps development platform and will look into relevant Services that are needed to build Cloud-native apps from scratch.
Flexible, hybrid API-led software architectures with KongSven Bernhardt
Kong is a lightweight, cloud-native API solution that makes it easier and faster than ever to connect APIs and microservices in today’s hybrid, multi-cloud environments. With its agnostic, flexible deployment approach, Kong can be used in today’s heterogeneous IT system landscapes to integrate a wide variety of data and systems – even across company boundaries – using APIs. In addition to REST APIs, Kong also offers support for gRPC and GraphQL, which broadens the possibilities to implement modern application architectures.
In this presentation, we will discuss deployment patterns and use cases for Kong to demonstrate the flexibility of the platform. Using a practical example, aspects of the API development and deployment process as well as the integration in existing software development processes will be discussed.
Cloud-native Application Development - The new normalSven Bernhardt
Presentation delivered at Digital Exchange Bergisches Rheinland 2022
Abstract:
Building applications in a Cloud-native way is the new normal, since the world is hybrid nowadays. Cloud-native applications are flexible, scalable and portable from On-prem environment to any Cloud platform as well as between different Cloud-vendor platforms without changing the actual implementation. This session will look at the key characteristics of Cloud-native applications and what this means for enterprises. In this session, I'll also give an overview on OCI and the provided Cloud-native apps development platform. In addition, I'll demo developing and running Cloud-native apps in OCI and will introduce the relevant Services.
Analytics meets Integration – Modern Development mit Data APIsFabian Hardt
Nachdem Analytics Plattformen mittlerweile fester Bestandteil der Unternehmens IT-Landschaften sind, wir auch die Vernetzung dieser zentralen Datenplattformen mit anderen Systemen zunehmend wichtiger. Um diese sicher und nachvollziehbar (API-Gateway), sowie individuell passend gestalten zu können (API-Modellierung), sind Data APIs ein möglicher Lösungsweg. Was es damit auf sich hat und wie eine Beispielimplementierung mit einem entsprechenden API-Gateway aussehen könnte, präsentieren wir Ihnen in diesem Vortrag.
Elevating Development: Embracing APIOps for Enhanced Developer ProductivitySven Bernhardt
APIOps, a dynamic fusion of API-first design principles and streamlined operational strategies, is reshaping the landscape of software development. This approach prioritizes the creation of application programming interfaces (APIs) as a foundational step, enabling modularization, reusability, and alignment with business goals.
Through seamless orchestration of the API lifecycle, APIOps embraces continuous integration, deployment, and management practices. This methodology empowers cross-functional teams to collaborate effectively, expediting project timelines and enhancing product quality. By decoupling frontend and backend development via APIs, developers can work concurrently, fostering agility and innovation without compromising stability. An APIOps approach has the potential to revolutionize software engineering, increase developer productivity, and thus efficiently deliver user-centric applications.
In this presentation, Sven explores:
How API-first and APIOps make your APIs great
APIOps' principles, benefits and capacity to drive transformative development practices
Kong’s APIOps support and how to get started
Delivering New Digital Experiences Fast - Introducing ChoreoWSO2
Watch webinar recording: https://wso2.com/library/webinars/deliver-new-digital-experiences-fast-with-choreo/
To differentiate yourself, you need to create unique and compelling digital experiences for both internal and external customers. However, this can be difficult and slow due to the complexity that comes from integrating existing systems, building new services, and managing APIs. Piecing together the development and operation technologies you need - including Kubernetes, Docker, and service meshes - takes time and requires dedicated expertise to manage, which can be hard to come by.
Choreo is a Digital Platform, as a service, for delivering new digital experiences. Choreo abstracts away the complexity of cloud-native infrastructure for your dev and ops teams so you can create new services, integrations, and APIs in hours or days instead of weeks or months.
This slide deck explores how you can use Choreo to
- Innovate in hours, not months by creating, composing, collaborating on, and reusing API-driven business logic
- Replace your complex infrastructure and coding with tools that make dev and ops simple and fast
- Make security and governance part of your DevOps automation with a platform where everything is secured and governed by default
Analytics meets Integration - Modern Development with Data APIsSven Bernhardt
Talk was delivered at DOAG 2022 with Fabian Hardt
Abstract:
Since analytics platforms are now an integral part of corporate IT landscapes, the networking of these central data platforms with other systems is becoming increasingly important. In order to be able to design these securely and comprehensibly (API gateway), as well as individually (API modelling), data APIs are a possible solution. In this presentation, we will show you what this means and what an example implementation with a corresponding API gateway could look like.
API history
APIs today
WhereAPIs areheadingto?
API-First-Design
Conclusion
Vortragsfolien vom Digital Xchange 2019, weitere Informationen auf digital-xchange.de
The Best of Both Worlds: Introducing WSO2 API Manager 4.0.0WSO2
APIs now serve as the primary building blocks for assembling data, events, and services from within the organization, throughout ecosystems, and across devices. Integrated legacy systems and support for modern event-driven architectures, on the other hand, are critical in allowing timely, relevant digital experiences in response to customer behavior. To support these demands, WSO2 has added significant new capabilities to WSO2 API Manager 4.0.0.
Complete support for streaming APIs and event-driven architecture (EDA)
The first solution to support full implementation of the AsyncAPI specification
A Service Catalog to enable developers to discover a given service seamlessly
API / API product revisioning to keep track of the changes
Feature-rich, cloud-based analytics for easy integration
You will gain a full understanding of WSO2 API Manager 4.0.0 features and how they cater to current API Management demands by attending this webinar.
DURING THE WEBINAR, WE WILL COVER:
Experience the power and synergy of Service Integration and API Management in a fully functional API ecosystem
Understand the motivation behind WSO2 API Manager 4.0.0 release
New streaming and event-driven architecture support available in API Manager 4.0.0
Learn the importance of catering all API Management and integration demands with one connected platform
Explore other new features and enhancements to the product
apidays Paris 2022 - Adding a mock as a service capability to your API strate...apidays
apidays Paris 2022 - APIs the next 10 years: Software, Society, Sovereignty, Sustainability
December 14, 15 & 16, 2022
Adding a mock as a service capability to your API strategy portfolio
Ludovic Pourrat, API Architect at Lombard Odier
------
Check out our conferences at https://www.apidays.global/
Do you want to sponsor or talk at one of our conferences?
https://apidays.typeform.com/to/ILJeAaV8
Learn more on APIscene, the global media made by the community for the community:
https://www.apiscene.io
Explore the API ecosystem with the API Landscape:
https://apilandscape.apiscene.io/
Deep dive into the API industry with our reports:
https://www.apidays.global/industry-reports/
Subscribe to our global newsletter:
https://apidays.typeform.com/to/i1MPEW
www.opitz-consulting.com
Automated tests are the key for quality assurance and for ensuring business agility from a long-term perspective. That is especially important in complex integration projects, independently if you develop your integrations on-premise or in the cloud. If a hybrid strategy is used it is important to have a consistent testing approach for cloud and on-premise. In this session we will show how to implement a consistent DevOps approach to establish short release cycles and to deliver system integration projects successfully. We will show how-to test aspects like BPEL, BPMN, Service Bus, Java, Human Tasks, XSLT and XQuery across all relevant test layers (Elementary Unit Tests, Component Tests, End-to-End Tests) by following the same approach.
How to take distributed architectures to the next level with API gateways and service meshes.
Anyone who thinks that the trend towards cloud-native applications is passing by like a hip fashion trend is overlooking something: Cloud-native is basically a puzzle piece in a larger game. This puzzle piece helps make solutions for a runtime environment, for example, as flexible as possible. Which is not unimportant. The goal of the big game is to build a software architecture that is capable of change on the one hand and robust at the same time. To do that, we need a lot of puzzle pieces, and move strategically through each level. Because while we realize cloud-native solutions as a microservices architecture, we get highly distributed architectures that present us with difficult tasks in areas such as deployment, security or connectivity. We have to solve these tasks before we enter the next level.
The respective demo scenario is available in my personal Github account: https://github.com/svenbernhardt/api-mesh-demo
Modern Integration based on OCI Cloud-native ServicesSven Bernhardt
Talk was delivered at DOAG 2022
Abstract:
Integration has always been important and has become more so, especially when we look at IT modernisation programmes. Every company today needs to modernise to remain competitive in the long term.
When we talk about modernisation, it is about breaking down monolithic architectures, often into more flexible microservices architectures. When developing new applications, we follow the principles of cloud-native. What does this mean for our integration architecture or what capabilities are expected from modern integration platforms?
In this session I will answer these and other questions. I will also show how to design and implement a modern integration solution with OCI cloud-native services, such as OKE, Functions or API Gateway, and what role an iPaaS solution such as Oracle Integration Cloud (OIC) plays in this context.
Rumble in the Jungle - API Kickstart with KongSven Bernhardt
Talk was delivered at Digital Exchange Bergisches Rheinland 2022
Abstract:
APIs have become indispensable in today's IT world, because (almost) everything has an API. This circumstance can quickly lead to an API jungle that is difficult to manage. However, it must be possible to see whether and how APIs are used, which APIs exist at all or how they are secured. The use of an API gateway is a first step towards making the impending chaos manageable.
Since infrastructures and platforms are very heterogeneous today and we are confronted with hybrid architectures, we need an API gateway that is flexible enough to deal with this heterogeneity. The Kong API Gateway offers this flexibility and can be deployed in almost any system environment, helping to shed light on the existing API jungle.
In this session I will introduce basic concepts of the API Gateway solution and show how easy and fast you can enter the world of API management with the Kong API Gateway.
Integration architectures based on Microservices, APIs and eventsSven Bernhardt
Talk from DigitalXChange 2023:
Integration is a key element of any modernization project and is perhaps more relevant than ever. In our IT modernization project, we had to overcome a 30-year monolith and used state-of-the-art technologies to bring the old and new worlds together. We used Containers, API Gateway, Service Mesh and Event Hub as well as Kubernetes as the central runtime platform to increase flexibility, agility and developer productivity.
This presentation shows how integrations are addressed today using modern technologies.
Similar to Implementing API-led Cloud-native apps on OCI (20)
Effective and simple - integration architectures with Apache Camel and QuarkusSven Bernhardt
Presentation held at DOAG 2023 in Nuremberg.
Integration is the basis for the modernization of IT system landscapes! This talk is about the challenges of integrating applications and systems in organizations and how Apache Camel and Quarkus can be used as integration tools to efficiently overcome these challenges.
We will give an overview of our idea of building an integration architecture and its components and show how integration solutions can be implemented quickly and efficiently based on it.
We will discuss the advantages of Camel and Quarkus and present practical examples and best practices. We will also look at the concepts of microservices and event-driven architecture and show how these can be integrated into integration solutions.
One Gateway to Rule them All: Building a Federated API Management PlatformSven Bernhardt
Presentation held at DOAG 2023 in Nuremberg.
There is no alternative for companies today to introduce an API strategy and set up an API management platform if they want to remain successful in the long term. In times of hybrid, multi-cloud architectures, characteristics such as efficiency, flexibility and manageability are required. A federated API management approach offers all of this.
Kong offers an API gateway that is flexible and extensible and is therefore ideally suited for setting up such an approach. This presentation will introduce how Kong can be used to build an API platform that can be used to securely deploy and manage APIs across multiple environments. In this context, I will cover the following aspects:
- Federated API Management: what it is and how it differs from other approaches
- Features of the Kong API gateway and its capabilities
- Strategies for managing APIs across multiple environments with Kong
- Implementation details and good practices for building a federated API management platform with Kong
The goal of the presentation is to convey the benefits of a federated approach by demonstrating how API development and management can be unified across multiple environments, reducing complexity and overhead and improving overall security and compliance.
Modernization options for Oracle Forms applicationsSven Bernhardt
Presentation held at DOAG 2023 in Nuremberg.
In mature IT system landscapes, there are still many monolithic applications that have grown over the years and were built on an outdated technology platform. Oracle Forms, which itself has been on the market for decades, is no exception. New innovative features are often difficult or impossible to implement on this basis. It is also difficult to find the appropriate resources in terms of the skillset required for implementation.
In this presentation, I will discuss the possible options for modernizing Forms applications. Among other things, I will discuss whether there is a "one-fits-all" solution or whether different approaches need to be combined. In this context, I will also present a concrete case study: In our company, we are currently replacing our Forms monolith - our core system - which has grown over 30 years. I will report on the procedure, the lessons learned and the approaches used. In particular, I will also discuss how essential it is to take a closer look at the topic of integration in this context and to think about it.
Kong 101 - Jumpstart into the world of APIsSven Bernhardt
Kong 101 introduction workshop held at Cloudland 2023.
Workshop materials in Git: https://github.com/svenbernhardt/kong101
Abstract:
We encounter APIs every day, which are present in almost all aspects of our daily lives. For example, when we pay with a card at the supermarket, the communication required for the transaction takes place in the background via APIs. This poses security risks and measures need to be taken to ensure that only authorized consumers can access APIs and that APIs are available 24/7.
An API gateway can help in this regard by acting as a central access point for APIs and helping to establish a common policy layer that decouples API consumers and providers. Kong is an open-source API gateway implementation designed for speed, scalability, and flexibility. It is platform and system independent, making it ideal for building distributed API environments.
This workshop will cover the basic concepts of Kong, the gateway architecture, ways to set up a Kong environment, and how to deploy and configure APIs. Through hands-on exercises, participants will have the opportunity to experience for themselves how easy and intuitive working with APIs using Kong can be.
Declarative observability management for Microservice architecturesSven Bernhardt
Cloud-native is the new normal! Cloud-native architectures are usually implemented using a distributed Microservice architecture style. This furthers agility and flexibility as changes can rapidly be implemented, as the services are loosely coupled. But this comes at a price, as application monitoring becomes increasingly complex. Observability data, which is logs, metrics and traces, needs to be collected in a central place so that DevOps teams can analyze problems through a single pane of glass and thus allows for efficiently monitor Microservices architectures.
Within this talk I’ll show how a basic observability strategy can easily being implemented without the need to touch your existing application logic. Kong Gateway and Kuma are essential components for the resulting solution architecture, to facilitate consistent logs, metrics and traces across all services. Using this approach, you're able to trace down the complete request lifecycle starting from the first call to Kong Gateway that acts as entry point to the Mesh. Within the Microservices domain, Kuma takes care for making inter-service communication transparently comprehensible. As a monitoring stack, the Grafana stack, consisting of Grafana, Prometheus, Loki and Tempo, will be used to gather all observability data in a central place and provide it for further analysis.
Build and Manage Multi-Cloud Applications Using KumaSven Bernhardt
A service mesh helps to make service communication in distributed system architectures more secure, reliable, and traceable. In this context, one often thinks of terms like microservices, containers, or Kubernetes; the whole thing, of course, is mostly cloud-based. However, the reality is not quite so simple: IT system landscapes today are very heterogeneous and workloads are distributed on-premises as well as across one or more public cloud providers. This brings up a whole new set of questions, such as how to securely merge multiple clouds or how applications that cannot be containerized can benefit from the advantages of a mesh.
Build and Manage Multi-Cloud Applications Using KumaSven Bernhardt
A service mesh helps to make service communication more secure, reliable and traceable in distributed system architectures. In connection with the topic of service mesh, we often think of terms such as microservices, containers or Kubernetes; i.e. terms from the orbit of modern design methods, architectural approaches or technologies. Of course, everything is usually cloud-based.
In reality, however, the world is not quite so simple: IT system landscapes today are very heterogeneous and system landscapes have grown over the years, with a colorful mix of architectural patterns and runtime platforms having emerged. Kubernetes-based workloads are possibly distributed across one or more public cloud providers. This brings with it a whole range of new questions, e.g. how to securely bring together multiple clouds or how applications that cannot be operated in a containerized manner can benefit from the advantages of a mesh.
In this presentation Sven and Fabian will talk about:
– How a service mesh can help to easily build and manage multi-cloud applications
– How to design a multi-cloud, multi-cluster mesh
– Handle aspects like security or observability consistently without the need for implementation changes
Torch the light - Implementing Observability for Microservice ArchitecturesSven Bernhardt
Talk was delivered at Kong Summit 2022
Abstract:
Cloud-native architectures are usually implemented using a distributed microservice architecture style. This furthers agility and flexibility since changes can rapidly be implemented, as the services are loosely coupled. But this comes at a price -- application monitoring becomes increasingly complex. In this talk, Sven Bernhardt will show how a basic observability strategy can easily be implemented without the need to alter your existing application logic. Sven will demonstrate: - How to use Kong Gateway and Kuma to facilitate consistent logs, metrics, and traces across all services. - How to trace down the complete request lifecycle starting from the first call to Kong Gateway - How Kuma makes inter-service communication transparently comprehensible - How the Grafana stack — consisting of Grafana, Prometheus, Loki and Tempo — can be used to gather all observability data in a central place and provide it for further analysis.
Talk was delivered at DOAG 2022 with Fabian Hardt
Abstract:
A service mesh helps to make service communication in distributed system architectures more secure, reliable and traceable. In connection with the topic of service mesh, terms such as microservices, containers or Kubernetes often come to mind; terms from the sphere of modern design methods, architectural approaches or technologies. Of course, everything is cloud-based as a rule.
In reality, however, the world is not quite so simple: IT system landscapes today are very heterogeneous and have grown over years, with a colourful mix of architecture patterns and runtime platforms. On-premises hosted monoliths that come from VM-based systems on the one hand and Kubernetes-based workloads, possibly distributed between on-premises and one or more public cloud providers, on the other. This brings with it a whole host of new questions, such as how to bring the cloud and on-premises world together securely or how applications that cannot be operated containerised can also benefit from the advantages of a mesh.
This session will look at how service mesh can help address complex connectivity, security and observability challenges in today's heterogeneous world. In this context, real-world scenarios from projects will be presented.
Next Gen Big Data Plattform mit Hadoop, APIs und KubernetesSven Bernhardt
Data is the new oil! Topics such as data-driven architectures or data on-demand are being dealt with by companies and their IT departments as part of the ubiquitous digitization efforts to make data available to third parties, even beyond company boundaries. When accessing data, you need to make sure it is delivered securely, in the format you need, and at the right time. The definition and implementation of appropriate, tool-independent business APIs is also an obvious choice when setting up a Big Data platform, since a flexible and extensible architecture is particularly important here. In addition to tools from the Big Data universe, integration components such as API gateways for secure access to the data and integration services that convert the data formats and protocols are added. Furthermore, APIs are important to decouple the individual components of such a data platform from each other, as the technology lifecycles become increasingly short-lived and tools can potentially disappear from the market quickly.
In this lecture, an example architecture is used to explain what needs to be considered when building a modern big data platform and how the provision of data and the abstraction of individual components can be achieved by implementing APIs. A core message of the lecture is that Big Data can no longer be viewed in isolation from other topics, such as classic integration challenges or containerized services. In addition to conventional Big Data tools such as Hadoop components, Nifi, Kafka, etc., the role of Kubernetes and API gateways will also be discussed.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
"Impact of front-end architecture on development cost", Viktor TurskyiFwdays
I have heard many times that architecture is not important for the front-end. Also, many times I have seen how developers implement features on the front-end just following the standard rules for a framework and think that this is enough to successfully launch the project, and then the project fails. How to prevent this and what approach to choose? I have launched dozens of complex projects and during the talk we will analyze which approaches have worked for me and which have not.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP