API history
APIs today
WhereAPIs areheadingto?
API-First-Design
Conclusion
Vortragsfolien vom Digital Xchange 2019, weitere Informationen auf digital-xchange.de
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.
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.
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.
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.
Implementing API-led Cloud-native apps on OCISven Bernhardt
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.
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.
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.
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.
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.
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.
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.
Implementing API-led Cloud-native apps on OCISven Bernhardt
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.
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.
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.
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.
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?
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.
A talk given by Marcin Gebala during the first meetup of GraphQL Wroclaw on 29 January 2019.
GraphQL became a mature ecosystem that answers the needs of modern web apps, and one of the most exciting trends in programming. The presentation talks about benefits from migrating to GraphQL (both backend and frontend), and the most interesting tools making frontend development easier and more pleasant.
Conference Projects visualization: BIM and linear planning. Marriott Hotel (Warsaw), 16.10.2015.
Presentation given by Alan Sharp - Business Area Director – Civil Engineering & Construction Division at Trimble Navigation Ltd.
With the rising popularity of implementing GitOps patterns into the DevOps Lifecycle, it get's more important to secure your production deployments.
With the combination of Flux V2 for automated GitOps rollouts and flagger, we can take care of safe and reliable production deployments. Flagger enables us to do automated Blue/Green and Canary deployments and automatically roll back to the previous version, in case the quality gates will fail.
In this talk we will show the different deployment strategies that flagger offers and will show how an fully automated delivery can look like.
No-Java Enterprise Applications: It’s All About JavaScript [DEV5107]Soham Dasgupta
Oracle Code One 2018 Session by Soham Dasgupta.
Abstract : How can we have enterprise-level fully JavaScript-based applications based on Oracle JavaScript Extension Toolkit (Oracle JET) and Node.js with Oracle PaaS services? This session discusses how to implement security and integrate back-end systems and build management, compiling, unit testing, and deployment, all based on different JavaScript frameworks. It also shows how we can use JavaScript for typical UI features for which we mostly require Java or a Java-based framework.
WebRTC in WebKitGTK+ and WPE (Web Engines Hackfest 2018)Igalia
By Thibault Saunier.
Slides at https://webengineshackfest.org/2018/slides/webrtc-in-webkitgtk-and-wpe-by-thibault-saunier/
Web Engines Hackfest 2018
October 1 - 3, 2018
A Coruña (Spain)
https://www.webengineshackfest.org/2018
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 Building Blocks of DX: K8s Evolution from CLI to GitOpsOlyaSurits
Kubernetes has become the default container orchestrator framework, setting the standards for application deployment in a distributed architecture. Wider adaptability of the tool prompted the diversification of the end-user base, and a consistent DX for cluster interaction became essential for Kubernetes. The community channeled herculean efforts towards the enhancement of developer experience, by extending the cluster CLI, building portals and highly-responsive UIs. This talk will focus on the cluster interaction chronicles, showcasing tools and add-ons which contributed to a wider adoption for Kubernetes. An emphasis will be place on kubectl plugins and cluster state managers using mechanisms such as GitOps, ClickOps and even SheetOps.
Conference Projects visualization: BIM and linear planning. Marriott Hotel (Warsaw), 16.10.2015.
Presentation given by Przemysław Nogaj - Territory Sales Executive at Autodesk.
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 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.
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.
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?
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.
A talk given by Marcin Gebala during the first meetup of GraphQL Wroclaw on 29 January 2019.
GraphQL became a mature ecosystem that answers the needs of modern web apps, and one of the most exciting trends in programming. The presentation talks about benefits from migrating to GraphQL (both backend and frontend), and the most interesting tools making frontend development easier and more pleasant.
Conference Projects visualization: BIM and linear planning. Marriott Hotel (Warsaw), 16.10.2015.
Presentation given by Alan Sharp - Business Area Director – Civil Engineering & Construction Division at Trimble Navigation Ltd.
With the rising popularity of implementing GitOps patterns into the DevOps Lifecycle, it get's more important to secure your production deployments.
With the combination of Flux V2 for automated GitOps rollouts and flagger, we can take care of safe and reliable production deployments. Flagger enables us to do automated Blue/Green and Canary deployments and automatically roll back to the previous version, in case the quality gates will fail.
In this talk we will show the different deployment strategies that flagger offers and will show how an fully automated delivery can look like.
No-Java Enterprise Applications: It’s All About JavaScript [DEV5107]Soham Dasgupta
Oracle Code One 2018 Session by Soham Dasgupta.
Abstract : How can we have enterprise-level fully JavaScript-based applications based on Oracle JavaScript Extension Toolkit (Oracle JET) and Node.js with Oracle PaaS services? This session discusses how to implement security and integrate back-end systems and build management, compiling, unit testing, and deployment, all based on different JavaScript frameworks. It also shows how we can use JavaScript for typical UI features for which we mostly require Java or a Java-based framework.
WebRTC in WebKitGTK+ and WPE (Web Engines Hackfest 2018)Igalia
By Thibault Saunier.
Slides at https://webengineshackfest.org/2018/slides/webrtc-in-webkitgtk-and-wpe-by-thibault-saunier/
Web Engines Hackfest 2018
October 1 - 3, 2018
A Coruña (Spain)
https://www.webengineshackfest.org/2018
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 Building Blocks of DX: K8s Evolution from CLI to GitOpsOlyaSurits
Kubernetes has become the default container orchestrator framework, setting the standards for application deployment in a distributed architecture. Wider adaptability of the tool prompted the diversification of the end-user base, and a consistent DX for cluster interaction became essential for Kubernetes. The community channeled herculean efforts towards the enhancement of developer experience, by extending the cluster CLI, building portals and highly-responsive UIs. This talk will focus on the cluster interaction chronicles, showcasing tools and add-ons which contributed to a wider adoption for Kubernetes. An emphasis will be place on kubectl plugins and cluster state managers using mechanisms such as GitOps, ClickOps and even SheetOps.
Conference Projects visualization: BIM and linear planning. Marriott Hotel (Warsaw), 16.10.2015.
Presentation given by Przemysław Nogaj - Territory Sales Executive at Autodesk.
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 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.
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.
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.
Serverless is currently the talk of the town and is enjoying increasing popularity. What does serverless actually mean, what are its characteristics and when do you prefer the use of serverless technologies to a container-based solution?
With the Fn project, Oracle now has a serverless open source platform that can run in the cloud, in its own data center or on a developer's local computer. This distinguishes the solution from other serverless platforms on the market. The Fn project is developed by the same team that previously implemented IronFunctions. The framework is based on Docker and currently does not require a managed runtime environment. But is it still serverless?
The session explains basic serverless concepts, benefits and deployment scenarios of the platform-independent Fn Serverless framework.
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.
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.
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.
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.
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.
www.opitz-consulting.com
Digitalization is bothering IT and business departments in the same way. Cloud, omni-channel and multi-device support as well as the modernization of legacy applications are main topics for companies to ensure sustained economic growth. A central challenge in this area is: How to ensure business agility regarding rapidly changing business requirements on the one hand and how to keep the robustness of core business functionalities on the other hand? An API-Layer, for decoupling those building blocks become more and more important. But how can it be achieved? This session covers the importance of API management and how companies can benefit from a consistent API management approach.
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.
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.
www.opitz-consulting.com
Digital transformation is on its way and the industry is required to adopt new concepts and techniques, like the Internet of things (IoT), Cloud and Enterprise Mobility. As a matter of that, new business models arise, which need to be evaluated by companies to not lose market shares and stay in touch with the competitors.
Gartner’s vision of Bi-modal IT seems to become more and more the reality, which besides all chances, also brings a lot of challenges companies have to deal with. One essential topic for implementing the ideas of Bi-modal IT is API Management – at least from our point of view. In addition, it is also a key enabler to define a solid strategy, in order to meet the challenges with respect to digital transformation.
Our experts Sven Bernhardt and Danilo Schmiedel held this session at DOAG 2016 in Nuremberg.
Digital transformation is on its way and the industry is required to adopt new concepts and techniques, like the Internet of things (IoT), Cloud and Enterprise Mobility. As a matter of that, new business models arise, which need to be evaluated by companies to not lose market shares and stay in touch with the competitors.
Gartner’s vision of Bi-modal IT seems to become more and more the reality, which besides all chances, also brings a lot of challenges companies have to deal with. One essential topic for implementing the ideas of Bi-modal IT is API Management – at least from our point of view. In addition, it is also a key enabler to define a solid strategy, in order to meet the challenges with respect to digital transformation.
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.
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.
apidays Helsinki & North 2023 - The future of API Management, Jona Apelbaum &...apidays
apidays Helsinki & North 2023
API Ecosystems - Connecting Physical and Digital
June 5 & 6, 2023
“The future of API Management”
Code-Driven API Magic: Revolutionizing Gateway, Developer Portal, and GraphQL
Jona Apelbaum, Field Engineer EMEA at Solo.io & Ep Heijting, EMEA Sales Lead at Solo.io
------
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/
API First - Best Practices for consistent API managementSven Bernhardt
APIs are an essential component of modern application architectures and allow the efficient implementation of innovative solutions with a consistently implemented management approach. The added value for companies: New digital markets and economies through closer networking with customers and partners. But what quality demands do such business APIs have to meet in order to deliver the desired added value? What does the lifecycle look like, especially in the design phase, and how can this IT-technical support be provided? In this presentation, we will explain best practices, show you how to design APIs, and how to implement a consistent API design lifecycle.
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.
Similar to Evolution of API-driven Architectures (20)
In diesem Webcast bekommen Sie Tipps und Hilfen auf dem Weg zu einer aufgeräumten Java Landschaft, mit der Sie Kosten und Risiken minimieren. Unsere Lizenzierungs- und Java-Experten sprechen dafür u. a. über diese Fragen:
* Wann ist Java "frei"? Und wann nicht?
* Wie Sie Java Installationen entdecken: Scanning-Tools und Inventarisierungslösungen
* Was steckt hinter Java, JDK und JRE? ... Mal genau erklärt
* Welche Open JDKs gibt es? Vor- und Nachteile, Supportmöglichkeiten
* Was wird morgen? Lifecycle Management, Release-Cadence-Wechsel
* Welche Oracle Lizenz-Metriken werden wann angewandt? Prozessor Core Metrik und NUP richtig zählen, Preislisten
* Geht es auch "ohne"?
* Welche Applikationen basieren auf Java?
* Wem gehört mein Java? Spezialfragen im Umfeld von Virtualisierung und Cloud
* Wie lassen sich Kosten sparen? Kostenminimierungsansätze
Die Aufzeichnung finden Sie hier:
https://youtu.be/k1ZpxoES18I
In diesem Webcast bekommen Sie Tipps und Hilfen auf dem Weg zu einer aufgeräumten Java Landschaft, mit der Sie Kosten und Risiken minimieren. Unsere Lizenzierungs- und Java-Experten sprechen dafür u. a. über diese Fragen:
* Wann ist Java "frei"? Und wann nicht?
* Wie Sie Java Installationen entdecken: Scanning-Tools und Inventarisierungslösungen
* Was steckt hinter Java, JDK und JRE? ... Mal genau erklärt
* Welche Open JDKs gibt es? Vor- und Nachteile, Supportmöglichkeiten
* Was wird morgen? Lifecycle Management, Release-Cadence-Wechsel
* Welche Oracle Lizenz-Metriken werden wann angewandt? Prozessor Core Metrik und NUP richtig zählen, Preislisten
* Geht es auch "ohne"?
* Welche Applikationen basieren auf Java?
* Wem gehört mein Java? Spezialfragen im Umfeld von Virtualisierung und Cloud
* Wie lassen sich Kosten sparen? Kostenminimierungsansätze
Die Aufzeichnung finden Sie hier: https://youtu.be/abVeIGmxYB0
Folien zum Webcast mit Fritz Wein Weinhappl (Oracle) und Uwe Küchler (OPITZ) am 27. April 2021.
Die Aufzeichnung finden Sie unter: https://youtu.be/un4gzCsmfwg
Im Bereich der professionellen Softwareentwicklung hat sich in den letzten 10 Jahren viel getan. In diesem Vortrag schauen wir uns an, was es eigentlich bedeutet, professionelle und nicht nur funktionierende Software zu entwickeln. Gerade auf der persönlichen und Teamebene unterscheidet sich die Disziplin der Softwareentwicklung in vielen Bereichen von den Anforderungen die noch vor einigen Jahren Gültigkeit besaßen.
Die Kernänderungen werden im Vortrag anhand von 10 Thesen verdeutlicht, erläutert und soll darüber zum Nachdenken über den Berufsethos eines Softwareentwicklers anregen. Neben Entwicklern richtet sich der Vortrag vor allem auch an Projektverantwortliche, da auch aufgezeigt wird, dass es weitere wichtige Aspekte neben den rein funktionalen Anforderungen zu beachten gilt.
Zum Referenten:
Richard Attermeyer arbeitet bei OPITZ CONSULTING als Senior Solution Architect im Bereich Technologiemanagement und Innovation. Dort leitet er unter anderem das Architecture Board. Er beschäftigt sich seit Jahren mit flexiblen Systemarchitekturen und deren Wechselwirkungen mit Entwicklungsprozessen und Unternehmens- und Managementkulturen. Hot Topics: CI/CD, Technologiemanagement, flexible Systemarchitekturen und DevOps.
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/
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
Generating a custom Ruby SDK for your web service or Rails API using Smithyg2nightmarescribd
Have you ever wanted a Ruby client API to communicate with your web service? Smithy is a protocol-agnostic language for defining services and SDKs. Smithy Ruby is an implementation of Smithy that generates a Ruby SDK using a Smithy model. In this talk, we will explore Smithy and Smithy Ruby to learn how to generate custom feature-rich SDKs that can communicate with any web service, such as a Rails JSON API.
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.
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.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
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.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.