Multi Domain REST API routing for Data Mesh based Data Products
0 likes26 views
The document discusses establishing a naming convention for customer-facing APIs within a data mesh environment, focusing on the challenges of exposing various data products across domains. It presents two potential solutions: one using a fully qualified domain name with centralized routing, and another using subdomain-based routing to streamline interactions while noting trade-offs like loss of centralized control. The information is intended for guidance only and not as a commitment to deliver specific features or functionalities.
1 of 7
Ad
Recommended
API Management and software services.pdf
API Management and software services.pdfProwess Software Services Inc
Ā
APIs enable easy communication and MuleSoft integration solutions of various systems that help accomplish enterprise business goals.
What was once a sizeable undertaking of building custom code that involved understanding the internals of other systems, building, and configuring the adapters, has now become an API-based integration that is easy and familiar for the developer community to integrate.
It is safe to say that if API is not part of the strategy for the product or a service, the real business value of the product may never be realized.
The wide adoption of APIs may be attributed to the ease and familiarity of APIs within the developer community.
Most of the REST-based features on which APIs are designed come with the HTTP protocol, which is widely used as the transport protocol for APIs.
It is the underlying protocol for data communication on the World Wide Web. The implementation of HTTP follows the principles laid out in the REST architectural style and becomes a natural choice of transport protocol for any APIs that need to be built for accessibility on the Web.Whitepaper-API-Design-Best-Practices. Prowess software services
Whitepaper-API-Design-Best-Practices. Prowess software servicesProwess Software Services Inc
Ā
With the onset of digital transformation journeys for enterprises across the world, APIs have become a
natural strategy for enterprises to provide access to their products and services. APIs enable easy
communication and integration of various systems that help accomplish enterprise business goals. What was
once a sizeable undertaking of building custom code that involved understanding the internals of other
systems, building, and configuring the adapters, has now become an API-based integration that is both easy
and familiar for the developer community to integrate with. It is safe to say that if API is not part of the
strategy for the product or a service, the real business value of the product may never be realized.
Whitepaper - A Guide to API Design Best Practices
Whitepaper - A Guide to API Design Best PracticesProwess Software Services Inc
Ā
ProwessSoft updated whitepaper on API design best practices offers a practical & concise guide to help developers design & implement high-quality APIs, ensuring improved user experience, security, & scalability. Contact us for more details!
Close.API Design ā More than just a Payload Definition
API Design ā More than just a Payload DefinitionPhil Wilkins
Ā
The document discusses various aspects of API design that go beyond just the payload, such as documentation, security, support for adoption and change management. It emphasizes that API design involves more than just the technical specification, and should include additional documentation, SDKs, test frameworks, and approaches to support consumers. Well-designed APIs consider the full lifecycle and user experience, not just the implementation details.Creating a RESTful api without losing too much sleep
Creating a RESTful api without losing too much sleepMike Anderson
Ā
The document outlines best practices for creating a RESTful API, emphasizing principles such as HATEOAS, structured coding, and security through built-in authentication. It covers testing methodologies, data formatting, resource naming conventions, versioning strategies, and the importance of interactive documentation. Tools like Postman are suggested for exercising the API, while caution is advised against common pitfalls like overly complex methods and inadequate testing.Hybrid cloud-cloud-services-white-paper-external-apw12358usen-20180516
Hybrid cloud-cloud-services-white-paper-external-apw12358usen-20180516Tanjina Prema
Ā
This white paper discusses identifying potential API use cases in the telecommunications industry. It begins by outlining common business drivers for API initiatives such as speed, reach, internet of things, and domains. It then describes a methodology for identifying business APIs that focuses on understanding the audience, their needs, and terms of use. Examples of potential telecom APIs are provided for internal developers, partners, public access, and using mobile device features and location data. The paper argues that telecom companies can expand their business and acquire new customers by developing and exposing relevant APIs.Api design best practice
Api design best practiceRed Hat
Ā
The document discusses API design best practices. It begins with an overview of API lifecycles and introduces two approaches to API design: design first and code first. It then outlines several design principles for APIs, including treating APIs as products and focusing on developer experience. The document also discusses OpenAPI Specification 3.0 and tools for API design like Stoplight, Restlet, and Apicurio. It concludes with complementary tools for API testing, mocking, and design.A_Complete_Guide_to_API_Development.pdf
A_Complete_Guide_to_API_Development.pdfPamRobert
Ā
The document serves as a comprehensive guide to API development, highlighting the significance of APIs in modern web applications and their crucial role in facilitating communication between software platforms. It discusses essential features and best practices for creating effective APIs, including authorization, data management, and security considerations. Additionally, the document explains the differences between REST and SOAP APIs and ends with an invitation for professional API development services.Api Design
Api DesignJason Harmon
Ā
This document discusses API design fundamentals including REST constraints, developer experience, scalability, sustainability, and consistency. It reviews REST constraints like statelessness and uniform interfaces. It emphasizes designing for developer experience by making APIs easy to use and well documented. Other topics covered include resource modeling, collections, filtering, versioning, and using hypermedia to link related resources.Modern REST API design principles and rules.pdf
Modern REST API design principles and rules.pdfAparna Sharma
Ā
The document outlines modern REST API design principles, emphasizing the importance of structure, naming, and functions when developing an API like newsdata.io. It explains the concept of APIs and REST, detailing when to use REST over SOAP, as well as guidelines for building effective APIs, including naming conventions and handling errors. Additionally, it discusses the challenges of REST APIs, such as security concerns and lack of state management.JOSA TechTalks - RESTful API Concepts and Best Practices
JOSA TechTalks - RESTful API Concepts and Best PracticesJordan Open Source Association
Ā
The document outlines key concepts and best practices for designing RESTful APIs, emphasizing the importance of a stateless architecture and standard HTTP methods. It discusses the main ingredients of a REST API, such as resources, protocols, and status codes, and contrasts REST with alternatives like SOAP and GraphQL. Best practices include treating APIs like consumer products, ensuring user experience through consistent naming and response handling, and maintaining backward compatibility through versioning.Enterprise API deployment best practice
Enterprise API deployment best practiceSanjay Roy
Ā
The document outlines how an enterprise API management platform can help organizations address challenges in the modern API economy. Specifically, it discusses how such a platform can:
1) Modernize legacy application interfaces by mediating between different interface standards.
2) Create new APIs and applications by orchestrating internal and third-party APIs.
3) Securely manage the lifecycle of APIs, applications, and partners from development to production.Designing Usable APIs featuring Forrester Research, Inc.
Designing Usable APIs featuring Forrester Research, Inc.CA API Management
Ā
The document discusses the design of usable APIs and emphasizes the importance of aligning API development with business goals and the developer experience (DX). It outlines different API categories and types, and stresses the significance of messages and security protocols in API design. Additionally, the document provides recommendations for effective API design, encouraging a focus on usability and the needs of developer users.Mini training- Scenario Driven Design
Mini training- Scenario Driven DesignBetclic Everest Group Tech Team
Ā
The document discusses scenario-driven design, emphasizing the importance of client needs and usage scenarios in API design. It critiques traditional RESTful approaches for exposing raw data and stresses the necessity of considering business logic within APIs. By leveraging specific client scenarios, the goal is to enhance usability, performance, and maintainability while reducing redundancy.Open Ap Is State Of The Market
Open Ap Is State Of The MarketConSanFrancisco123
Ā
a+b=c
The document discusses the state of open APIs. Some key points include:
1. Open APIs allow companies to make money, save money, build their brand, and move functionality to the cloud. Many large companies rely heavily on APIs.
2. The business of APIs is moving to cloud-based models. APIs are becoming the glue that integrates software-as-a-service applications and internal and external systems.
3. Successful APIs have a good underlying service, business model, simple design, choices for developers, and support. Different protocols and data formats can work for different situations depending on simplicity versus complexity.Top 7 wrong common beliefs about Enterprise API implementation
Top 7 wrong common beliefs about Enterprise API implementationOCTO Technology
Ā
The document discusses 7 common misconceptions about enterprise API implementation. It argues that an API strategy is not just about technical implementation or buying a product, but involves organizational, functional, and technical considerations. A successful API requires viewing it as a product and considering impacts across the entire organization.Octo API-days 2015
Octo API-days 2015Antoine CHANTALOU
Ā
The document discusses common misconceptions about enterprise API implementation, highlighting key differences between SOAP and REST, and the importance of a comprehensive API strategy. It emphasizes that API management should focus on consumer needs rather than just technical integration and suggests strategies for building effective APIs. Additionally, it underscores the significance of organizational structure and collaboration in API development and promotes the idea of open APIs for better external engagement.Effective API Design
Effective API DesignBansilal Haudakari
Ā
This document discusses principles for effective API design. It defines an API as providing a way for developers to interact with and consume a service. It outlines six principles for API design: design first, choose the right runtime, define contracts, monitor usage, continuously improve, and socialize APIs. The principles emphasize designing for developers and specific use cases, ensuring scalability and reliability of the runtime, and engaging with developers through documentation and community. Well-designed APIs that follow these principles can become valuable products and ecosystems, while mediocre APIs that don't engage stakeholders may fail to meet business objectives.The ultimate api checklist by Blendr.io
The ultimate api checklist by Blendr.ioBlendr.io
Ā
The document outlines an API checklist for SaaS companies emphasizing the importance of adopting an API-first strategy for effective integrations. Key recommendations include using HTTPS, proper error handling, versioning, and secure authentication to enhance API usability and security. Additionally, it highlights best practices such as providing documentation, enabling webhooks, and implementing usage limits to optimize API consumption and support integration needs.Api design part 1
Api design part 1Ibrahim Elsawaf
Ā
The document provides an overview of API design. It discusses key concepts like the API hierarchy of needs which is inspired by Maslow's hierarchy of needs. It outlines different architectural styles for APIs including tunneling, URI, hypermedia, and event-driven. It also discusses architectural layers for APIs including security, caching, representation, and orchestration layers. Additionally, it introduces the USE paradigm for API design which emphasizes usability, scalability, and evolvability as important qualities for APIs. The document provides guidance on how to design APIs with these qualities in mind.API ARU-ARU
API ARU-ARUCData Software Japan
Ā
The document discusses common pitfalls in API design and developer experience (DX). It notes that many APIs are designed based on the user experience (UX) of the underlying services, rather than focusing on DX. This results in obstacles like complex documentation, restrictive access policies, and unclear data formats that make APIs difficult for developers to use. The presentation argues that APIs should redefine UX as DX by focusing on the needs of developer users through measures like automated documentation, liberal trial access, and technical support.O reilly sacon2018nyc - restful api design - master - v1.0
O reilly sacon2018nyc - restful api design - master - v1.0Tom Hofte
Ā
The document outlines a tutorial on designing a resource model for a public API, presented by Tom Hƶfte and Marco van der Linden at the O'Reilly Software Architecture Conference in 2018. It covers the importance of API domain discovery, REST resource modeling, and how to map domain entities and operations to REST resources. The tutorial emphasizes best practices for creating user-friendly, extensible, and maintainable APIs, along with exercises to apply the concepts learned.Fundamental essentials for api design
Fundamental essentials for api designMichael James Cyrus
Ā
The document provides best practices for designing RESTful APIs, including:
1. Use JSON for responses as it is ubiquitous, human-readable, and allows easy changes to fields.
2. Design RESTful URLs around logical resources that are manipulated using HTTP methods like GET, POST, PUT, and DELETE.
3. Always use SSL to encrypt communications and simplify authentication with access tokens instead of signing requests.Fundamental essentials for api design
Fundamental essentials for api designMichael James Cyrus
Ā
This document outlines best practices for designing and configuring RESTful APIs, emphasizing the importance of real-world applicability over academic standards. Key topics include the use of JSON for its ubiquity and readability, the significance of SSL for security, and the necessity of effective documentation and versioning. It also addresses common design challenges, HTTP methods, resource relationships, and error handling to create scalable and maintainable APIs.Fundamental Essentials for API Design
Fundamental Essentials for API DesignMichael James Cyrus
Ā
This document outlines best practices for designing and configuring RESTful APIs to enhance scalability, security, and usability. It emphasizes the importance of using HTTP protocols effectively, maintaining clear documentation, ensuring version control, and implementing features like JSON responses, filtering, and authentication to facilitate a seamless developer experience. Key aspects include following REST principles for resource management, using SSL for security, and considering user-friendly endpoints and response structures.OData Introduction and Impact on API Design (Webcast)
OData Introduction and Impact on API Design (Webcast)Apigee | Google Cloud
Ā
The document discusses the implications of OData on API design, introducing concepts around data exposure and the transition to more API-centric approaches in business. It compares REST APIs with OData's schema-centric model and provides examples of OData requests and responses, emphasizing its filtering and querying capabilities. Additionally, it poses questions about the community's support and the potential for standardizing around OData.Top 10 Lessons Learned from the Netflix API - OSCON 2014
Top 10 Lessons Learned from the Netflix API - OSCON 2014Daniel Jacobson
Ā
The document discusses lessons learned from Netflix's API strategy over time. It notes that Netflix started with a focus on growing a community of public developers but now prioritizes ensuring subscribers can stream. It also discusses separating concerns between API providers and consumers, embracing differences in audiences, being pragmatic over dogmatic in API decisions, enabling fast iteration, planning for failures, and scaling infrastructure to match growth.Api Design Patterns Meap V07 Meap V07 Jj Geewax
Api Design Patterns Meap V07 Meap V07 Jj Geewaxmohellrakes
Ā
Api Design Patterns Meap V07 Meap V07 Jj Geewax
Api Design Patterns Meap V07 Meap V07 Jj Geewax
Api Design Patterns Meap V07 Meap V07 Jj GeewaxTClab Dynamic Solar Panel Positioning Systems
TClab Dynamic Solar Panel Positioning SystemsJohan Louwers
Ā
The document discusses dynamic solar panel positioning systems, focusing on the engineering study of dual-axis positioning that optimizes solar energy capture through precise adjustments of azimuth and altitude angles. Utilizing technologies such as slew drives for azimuth corrections and linear actuators for altitude adjustments, the system improves energy efficiency by tracking the sun's path. Additionally, it highlights the use of the Python package 'pyephem' for calculating solar positions and the integration of various sensors within the TCLab platform for monitoring and control.Oracle Cloud With Azure DevOps Pipelines
Oracle Cloud With Azure DevOps PipelinesJohan Louwers
Ā
Oracle Cloud DevOps with Azure Pipelines allows connecting Azure Pipelines to Oracle Cloud Infrastructure (OCI) APIs and deployed components through the use of self-hosted Azure agents running within OCI. This enables full pipeline execution within OCI while leveraging tools like Terraform for infrastructure provisioning and cx_Oracle for working with Oracle databases. Ensuring agents have direct connectivity and aiming for a software-defined automated strategy is recommended over cross-cloud connections.More Related Content
Similar to Multi Domain REST API routing for Data Mesh based Data Products (20)
Api Design
Api DesignJason Harmon
Ā
This document discusses API design fundamentals including REST constraints, developer experience, scalability, sustainability, and consistency. It reviews REST constraints like statelessness and uniform interfaces. It emphasizes designing for developer experience by making APIs easy to use and well documented. Other topics covered include resource modeling, collections, filtering, versioning, and using hypermedia to link related resources.Modern REST API design principles and rules.pdf
Modern REST API design principles and rules.pdfAparna Sharma
Ā
The document outlines modern REST API design principles, emphasizing the importance of structure, naming, and functions when developing an API like newsdata.io. It explains the concept of APIs and REST, detailing when to use REST over SOAP, as well as guidelines for building effective APIs, including naming conventions and handling errors. Additionally, it discusses the challenges of REST APIs, such as security concerns and lack of state management.JOSA TechTalks - RESTful API Concepts and Best Practices
JOSA TechTalks - RESTful API Concepts and Best PracticesJordan Open Source Association
Ā
The document outlines key concepts and best practices for designing RESTful APIs, emphasizing the importance of a stateless architecture and standard HTTP methods. It discusses the main ingredients of a REST API, such as resources, protocols, and status codes, and contrasts REST with alternatives like SOAP and GraphQL. Best practices include treating APIs like consumer products, ensuring user experience through consistent naming and response handling, and maintaining backward compatibility through versioning.Enterprise API deployment best practice
Enterprise API deployment best practiceSanjay Roy
Ā
The document outlines how an enterprise API management platform can help organizations address challenges in the modern API economy. Specifically, it discusses how such a platform can:
1) Modernize legacy application interfaces by mediating between different interface standards.
2) Create new APIs and applications by orchestrating internal and third-party APIs.
3) Securely manage the lifecycle of APIs, applications, and partners from development to production.Designing Usable APIs featuring Forrester Research, Inc.
Designing Usable APIs featuring Forrester Research, Inc.CA API Management
Ā
The document discusses the design of usable APIs and emphasizes the importance of aligning API development with business goals and the developer experience (DX). It outlines different API categories and types, and stresses the significance of messages and security protocols in API design. Additionally, the document provides recommendations for effective API design, encouraging a focus on usability and the needs of developer users.Mini training- Scenario Driven Design
Mini training- Scenario Driven DesignBetclic Everest Group Tech Team
Ā
The document discusses scenario-driven design, emphasizing the importance of client needs and usage scenarios in API design. It critiques traditional RESTful approaches for exposing raw data and stresses the necessity of considering business logic within APIs. By leveraging specific client scenarios, the goal is to enhance usability, performance, and maintainability while reducing redundancy.Open Ap Is State Of The Market
Open Ap Is State Of The MarketConSanFrancisco123
Ā
a+b=c
The document discusses the state of open APIs. Some key points include:
1. Open APIs allow companies to make money, save money, build their brand, and move functionality to the cloud. Many large companies rely heavily on APIs.
2. The business of APIs is moving to cloud-based models. APIs are becoming the glue that integrates software-as-a-service applications and internal and external systems.
3. Successful APIs have a good underlying service, business model, simple design, choices for developers, and support. Different protocols and data formats can work for different situations depending on simplicity versus complexity.Top 7 wrong common beliefs about Enterprise API implementation
Top 7 wrong common beliefs about Enterprise API implementationOCTO Technology
Ā
The document discusses 7 common misconceptions about enterprise API implementation. It argues that an API strategy is not just about technical implementation or buying a product, but involves organizational, functional, and technical considerations. A successful API requires viewing it as a product and considering impacts across the entire organization.Octo API-days 2015
Octo API-days 2015Antoine CHANTALOU
Ā
The document discusses common misconceptions about enterprise API implementation, highlighting key differences between SOAP and REST, and the importance of a comprehensive API strategy. It emphasizes that API management should focus on consumer needs rather than just technical integration and suggests strategies for building effective APIs. Additionally, it underscores the significance of organizational structure and collaboration in API development and promotes the idea of open APIs for better external engagement.Effective API Design
Effective API DesignBansilal Haudakari
Ā
This document discusses principles for effective API design. It defines an API as providing a way for developers to interact with and consume a service. It outlines six principles for API design: design first, choose the right runtime, define contracts, monitor usage, continuously improve, and socialize APIs. The principles emphasize designing for developers and specific use cases, ensuring scalability and reliability of the runtime, and engaging with developers through documentation and community. Well-designed APIs that follow these principles can become valuable products and ecosystems, while mediocre APIs that don't engage stakeholders may fail to meet business objectives.The ultimate api checklist by Blendr.io
The ultimate api checklist by Blendr.ioBlendr.io
Ā
The document outlines an API checklist for SaaS companies emphasizing the importance of adopting an API-first strategy for effective integrations. Key recommendations include using HTTPS, proper error handling, versioning, and secure authentication to enhance API usability and security. Additionally, it highlights best practices such as providing documentation, enabling webhooks, and implementing usage limits to optimize API consumption and support integration needs.Api design part 1
Api design part 1Ibrahim Elsawaf
Ā
The document provides an overview of API design. It discusses key concepts like the API hierarchy of needs which is inspired by Maslow's hierarchy of needs. It outlines different architectural styles for APIs including tunneling, URI, hypermedia, and event-driven. It also discusses architectural layers for APIs including security, caching, representation, and orchestration layers. Additionally, it introduces the USE paradigm for API design which emphasizes usability, scalability, and evolvability as important qualities for APIs. The document provides guidance on how to design APIs with these qualities in mind.API ARU-ARU
API ARU-ARUCData Software Japan
Ā
The document discusses common pitfalls in API design and developer experience (DX). It notes that many APIs are designed based on the user experience (UX) of the underlying services, rather than focusing on DX. This results in obstacles like complex documentation, restrictive access policies, and unclear data formats that make APIs difficult for developers to use. The presentation argues that APIs should redefine UX as DX by focusing on the needs of developer users through measures like automated documentation, liberal trial access, and technical support.O reilly sacon2018nyc - restful api design - master - v1.0
O reilly sacon2018nyc - restful api design - master - v1.0Tom Hofte
Ā
The document outlines a tutorial on designing a resource model for a public API, presented by Tom Hƶfte and Marco van der Linden at the O'Reilly Software Architecture Conference in 2018. It covers the importance of API domain discovery, REST resource modeling, and how to map domain entities and operations to REST resources. The tutorial emphasizes best practices for creating user-friendly, extensible, and maintainable APIs, along with exercises to apply the concepts learned.Fundamental essentials for api design
Fundamental essentials for api designMichael James Cyrus
Ā
The document provides best practices for designing RESTful APIs, including:
1. Use JSON for responses as it is ubiquitous, human-readable, and allows easy changes to fields.
2. Design RESTful URLs around logical resources that are manipulated using HTTP methods like GET, POST, PUT, and DELETE.
3. Always use SSL to encrypt communications and simplify authentication with access tokens instead of signing requests.Fundamental essentials for api design
Fundamental essentials for api designMichael James Cyrus
Ā
This document outlines best practices for designing and configuring RESTful APIs, emphasizing the importance of real-world applicability over academic standards. Key topics include the use of JSON for its ubiquity and readability, the significance of SSL for security, and the necessity of effective documentation and versioning. It also addresses common design challenges, HTTP methods, resource relationships, and error handling to create scalable and maintainable APIs.Fundamental Essentials for API Design
Fundamental Essentials for API DesignMichael James Cyrus
Ā
This document outlines best practices for designing and configuring RESTful APIs to enhance scalability, security, and usability. It emphasizes the importance of using HTTP protocols effectively, maintaining clear documentation, ensuring version control, and implementing features like JSON responses, filtering, and authentication to facilitate a seamless developer experience. Key aspects include following REST principles for resource management, using SSL for security, and considering user-friendly endpoints and response structures.OData Introduction and Impact on API Design (Webcast)
OData Introduction and Impact on API Design (Webcast)Apigee | Google Cloud
Ā
The document discusses the implications of OData on API design, introducing concepts around data exposure and the transition to more API-centric approaches in business. It compares REST APIs with OData's schema-centric model and provides examples of OData requests and responses, emphasizing its filtering and querying capabilities. Additionally, it poses questions about the community's support and the potential for standardizing around OData.Top 10 Lessons Learned from the Netflix API - OSCON 2014
Top 10 Lessons Learned from the Netflix API - OSCON 2014Daniel Jacobson
Ā
The document discusses lessons learned from Netflix's API strategy over time. It notes that Netflix started with a focus on growing a community of public developers but now prioritizes ensuring subscribers can stream. It also discusses separating concerns between API providers and consumers, embracing differences in audiences, being pragmatic over dogmatic in API decisions, enabling fast iteration, planning for failures, and scaling infrastructure to match growth.Api Design Patterns Meap V07 Meap V07 Jj Geewax
Api Design Patterns Meap V07 Meap V07 Jj Geewaxmohellrakes
Ā
Api Design Patterns Meap V07 Meap V07 Jj Geewax
Api Design Patterns Meap V07 Meap V07 Jj Geewax
Api Design Patterns Meap V07 Meap V07 Jj GeewaxMore from Johan Louwers (20)
TClab Dynamic Solar Panel Positioning Systems
TClab Dynamic Solar Panel Positioning SystemsJohan Louwers
Ā
The document discusses dynamic solar panel positioning systems, focusing on the engineering study of dual-axis positioning that optimizes solar energy capture through precise adjustments of azimuth and altitude angles. Utilizing technologies such as slew drives for azimuth corrections and linear actuators for altitude adjustments, the system improves energy efficiency by tracking the sun's path. Additionally, it highlights the use of the Python package 'pyephem' for calculating solar positions and the integration of various sensors within the TCLab platform for monitoring and control.Oracle Cloud With Azure DevOps Pipelines
Oracle Cloud With Azure DevOps PipelinesJohan Louwers
Ā
Oracle Cloud DevOps with Azure Pipelines allows connecting Azure Pipelines to Oracle Cloud Infrastructure (OCI) APIs and deployed components through the use of self-hosted Azure agents running within OCI. This enables full pipeline execution within OCI while leveraging tools like Terraform for infrastructure provisioning and cx_Oracle for working with Oracle databases. Ensuring agents have direct connectivity and aiming for a software-defined automated strategy is recommended over cross-cloud connections.Oracle Cloud native functions - create application from cli
Oracle Cloud native functions - create application from cliJohan Louwers
Ā
This document outlines the process for creating applications using Oracle Cloud Functions from the command line interface (CLI). It emphasizes that the information provided is for guidance only and should not be relied upon for purchasing decisions. Additionally, it details the steps required to configure the environment and deploy a serverless function application named 'neptune'.Oracle Labs - research mission & project potfolio
Oracle Labs - research mission & project potfolioJohan Louwers
Ā
Oracle Labs conducts a balanced research portfolio encompassing exploratory and directed research, consulting, and product incubation. Key focus areas include computer architecture, distributed systems, machine learning, and programming language research, aimed at improving performance and efficiency across various applications. Current projects involve cloud infrastructure, graph analytics, database processing, and innovative optimization techniques.Install Redis on Oracle Linux
Install Redis on Oracle LinuxJohan Louwers
Ā
This document is a quick installation guide for setting up Redis on Oracle Linux, intended for development and personal use. It details steps for installing the EPEL repository, Redis, and configuring network settings while highlighting features and benefits of Oracle Linux. The guide also includes instructions for verifying the installation and ensuring that Redis is functioning correctly.Fn project quick installation guide
Fn project quick installation guideJohan Louwers
Ā
This document provides a quick installation guide for FN Project on Oracle Linux:
- It assumes Oracle Linux 7 is installed and the correct yum repositories are enabled.
- Docker is installed using the command "yum -y install docker-engine" and started.
- FN Project is installed by downloading and executing an install script from GitHub.
- FN Project is started using the "fn start" command.Oracle python pandas merge DataFrames
Oracle python pandas merge DataFramesJohan Louwers
Ā
This document provides a tutorial on merging two dataframes using the Python library Pandas, as part of a wider workshop. It outlines the steps to load datasets from CSV files and merge them using specified keys. The intended use of the code is for educational purposes only and should not be used in production applications.import data from Oracle Database into Python Pandas Dataframe
import data from Oracle Database into Python Pandas DataframeJohan Louwers
Ā
This document provides a tutorial on loading data from an Oracle database into a pandas DataFrame using Python. It outlines the use of the cx_Oracle library, demonstrating a sample code to establish a connection and execute a SQL query. The material serves as an educational example and is not intended for real-world application.Voice assistants for the insurance industry
Voice assistants for the insurance industry Johan Louwers
Ā
This document discusses the rapid adoption of voice assistants and the opportunities they present for financial services firms. It notes that voice assistant usage has increased significantly in recent years, especially among younger demographics, and is expected to continue growing quickly. Retail and e-commerce companies have started capitalizing on voice shopping. Now financial services firms need to develop strategies to engage customers through this new voice channel, like using voice assistants to provide personalized products and services or improve customer service. The document argues voice is becoming a critical new interaction method and financial companies must adopt a voice strategy to succeed.Enterprise wide publish subscribe with Apache Kafka
Enterprise wide publish subscribe with Apache KafkaJohan Louwers
Ā
The document discusses enterprise wide publish/subscribe models using Apache Kafka. It describes moving from monolithic architectures to microservice architectures and how Kafka can be used to distribute transactions between microservices. It provides examples of publishing and subscribing using Kafka clients and discusses considerations for deploying Kafka in a highly available manner across multiple data centers.Industry 4.0 and Oracle Cloud
Industry 4.0 and Oracle CloudJohan Louwers
Ā
The document discusses Industry 4.0 and the integration of artificial intelligence across various cloud and on-premise infrastructures, emphasizing its mathematical basis and processing requirements. It highlights Capgemini's commitment to innovation in consulting and technology services, aiming to help organizations leverage digital transformation. Capgemini, with a diverse workforce of 200,000 members worldwide, generated global revenues of EUR 12.8 billion in 2017.Docker and microservices - moving from a monolith to microservices
Docker and microservices - moving from a monolith to microservicesJohan Louwers
Ā
The document discusses moving from a monolithic application architecture to microservices. It begins by stating some ground rules for the presentation. It then discusses how microservices are defined as independently deployable services that communicate via APIs. Docker containers are presented as a way to package and deploy microservices for benefits like automated deployment and scaling. Key differences between containers and virtual machines are highlighted. An example deployment architecture with containers is shown. The document acknowledges that transitioning to microservices and containers will be a long process but will enable benefits like agility, performance and higher release frequency.Cloud native applications for banking
Cloud native applications for bankingJohan Louwers
Ā
The document discusses how banks are increasingly adopting cloud-native approaches to application development and deployment to improve business agility, customer experiences, and operational efficiency. It outlines three common uses cases driving cloud-native adoption: 1) transforming the business for greater agility and flexibility, 2) optimizing operational efficiency using public cloud infrastructure, and 3) adopting an API ecosystem. While cloud-native approaches provide benefits, banks face challenges integrating legacy infrastructure and cultural changes. The document recommends banks assess their application portfolio to determine what can be lifted to the cloud, rewritten for cloud, or retired.Conversational retail
Conversational retailJohan Louwers
Ā
The document discusses the rise of conversational commerce and the adoption of voice technology by consumers. It highlights Capgemini's leadership in consulting and digital transformation, noting its commitment to innovation and strategic services. The information includes Capgemini's financials and emphasizes its focus on the human aspect of technology-driven business success.Oracle Cloudday security
Oracle Cloudday securityJohan Louwers
Ā
The document discusses the harsh realities of enterprise security, emphasizing that organizations should prepare for hacking incidents rather than questioning if they will occur. It provides insights into cyber attacks, their motivations and origins, as well as the risks associated with third-party applications and their impacts on businesses. Additionally, it highlights solutions offered by Oracle, such as machine learning and security analytics, to proactively combat security threats.Oracle Cloudday - the future of retail
Oracle Cloudday - the future of retailJohan Louwers
Ā
The document discusses the future of retail in the Oracle Cloud, emphasizing the importance of omni-channel retail models and real-time customer data responsiveness. It outlines various technology solutions and examples, such as mobile pre-ordering, dynamic pricing, and AI-driven customer interaction, leveraging Oracle's cloud services. The hybrid model suggested combines cloud-native solutions with third-party software to enhance retail logistics and customer engagement.Capgemini Oracle Cloud Access Security Broker
Capgemini Oracle Cloud Access Security BrokerJohan Louwers
Ā
The Oracle Cloud Access Security Broker (CASB) provides automated security monitoring for cloud applications and workloads, offering features like threat detection, incident response, and security configuration management. It enhances visibility and compliance, enabling organizations to secure cloud environments from day one and automate responses to incidents. Capgemini supports customers in deploying Oracle technology, ensuring optimal solutions and business value through a global network of innovation and consultancy.Microservices in the oracle cloud
Microservices in the oracle cloudJohan Louwers
Ā
The document discusses microservices and using the Oracle Container Cloud Service. It introduces Johan Louwers and his background. It then discusses the evolution from monolithic applications to microservices-based applications. It provides an example architecture of using microservices with the Oracle Container Cloud Service, with each microservice running in a Docker container. It describes how the Oracle Integration Cloud Service can provide integration between microservices and other Oracle Cloud services.Oracle cloud, private, public and hybrid
Oracle cloud, private, public and hybridJohan Louwers
Ā
The document provides an overview of Oracle's cloud offerings, including insights into public, private, and hybrid cloud models. It emphasizes the importance of choosing the right cloud solution to fit specific needs and discusses the management of hybrid clouds using Oracle's enterprise tools. Additionally, it outlines next steps for customers regarding the consolidation of systems and the use of Oracle's cloud services.RethinkDB on Oracle Linux
RethinkDB on Oracle LinuxJohan Louwers
Ā
The document discusses options for running RethinkDB on Oracle Linux. There are three main options: 1) on bare metal servers, 2) within Oracle VM virtual machines, or 3) using Oracle Cloud. A fourth option discussed is using Docker containers with RethinkDB. The document provides guidance on installing RethinkDB, including needing to compile Google Protocol Buffers and using a RethinkDB YUM repository. It also reviews checking the RethinkDB installation and provides contact information.Ad
Recently uploaded (20)
AI vs Human Writing: Can You Tell the Difference?
AI vs Human Writing: Can You Tell the Difference?Shashi Sathyanarayana, Ph.D
Ā
This slide illustrates a side-by-side comparison between human-written, AI-written, and ambiguous content. It highlights subtle cues that help readers assess authenticity, raising essential questions about the future of communication, trust, and thought leadership in the age of generative AI.CapCut Pro Crack For PC Latest Version {Fully Unlocked} 2025
CapCut Pro Crack For PC Latest Version {Fully Unlocked} 2025pcprocore
Ā
šš”š¼šš²:šš¼š½š š¹š¶š»šø & š½š®ššš² š¶š»šš¼ šš¼š¼š“š¹š² š»š²š šš®šÆ> https://pcprocore.com/ šā
CapCut Pro Crack is a powerful tool that has taken the digital world by storm, offering users a fully unlocked experience that unleashes their creativity. With its user-friendly interface and advanced features, itās no wonder why aspiring videographers are turning to this software for their projects.You are not excused! How to avoid security blind spots on the way to production
You are not excused! How to avoid security blind spots on the way to productionMichele Leroux Bustamante
Ā
We live in an ever evolving landscape for cyber threats creating security risk for your production systems. Mitigating these risks requires participation throughout all stages from development through production delivery - and by every role including architects, developers QA and DevOps engineers, product owners and leadership. No one is excused! This session will cover examples of common mistakes or missed opportunities that can lead to vulnerabilities in production - and ways to do better throughout the development lifecycle.EIS-Webinar-Engineering-Retail-Infrastructure-06-16-2025.pdf
EIS-Webinar-Engineering-Retail-Infrastructure-06-16-2025.pdfEarley Information Science
Ā
As AI reshapes expectations in retail and B2B commerce, organizations are recognizing a critical reality: meaningful AI outcomes depend on well-structured, adaptable infrastructure. In this session, Seth Earley is joined by Phil Ryan - AI strategist, search technologist, and founder of Glass Leopard Technologies - for a candid conversation on what it truly means to engineer systems for scale, agility, and intelligence.
Phil draws on more than two decades of experience leading search and AI initiatives for enterprise organizations. Together, he and Seth explore the challenges businesses face when legacy architectures limit personalization, agility, and real-time decisioning - and what needs to change to support agentic technologies and next-best-action capabilities.
Key themes from the webinar include:
Composability as a prerequisite for AIĀ - Why modular, loosely coupled systems are essential for adapting to rapid innovation and evolving business needs
Search and relevance as foundational to AIĀ - How techniques honed-in enterprise search have laid the groundwork for more responsive and intelligent customer experiences
From MDM and CDP to agentic systemsĀ - How data platforms are evolving to support richer customer context and dynamic orchestration
Engineering for business alignmentĀ - Why successful AI programs require architectural decisions grounded in measurable outcomes
The conversation is practical and forward-looking, connecting deep technical understanding with real-world business needs. Whether youāre modernizing your commerce stack or exploring how AI can enhance product discovery, personalization, or customer journeys, this session provides a clear-eyed view of the capabilities, constraints, and priorities that matter most.Quantum AI Discoveries: Fractal Patterns Consciousness and Cyclical Universes
Quantum AI Discoveries: Fractal Patterns Consciousness and Cyclical UniversesSaikat Basu
Ā
Embark on a cosmic journey exploring the intersection of quantum
computing, consciousness, and ancient wisdom. Together we'll uncover the
recursive patterns that bind our reality.The Future of Product Management in AI ERA.pdf
The Future of Product Management in AI ERA.pdfAlyona Owens
Ā
Hi, Iām Aly Owens, I have a special pleasure to stand here as over a decade ago I graduated from CityU as an international student with an MBA program. I enjoyed the diversity of the school, ability to work and study, the network that came with being here, and of course the price tag for students here has always been more affordable than most around.
Since then I have worked for major corporations like T-Mobile and Microsoft and many more, and I have founded a startup. I've also been teaching product management to ensure my students save time and money to get to the same level as me faster avoiding popular mistakes. Today as Iāve transitioned to teaching and focusing on the startup, I hear everybody being concerned about Ai stealing their jobsā¦ Weāll talk about it shortly.
But before that, I want to take you back to 1997. One of my favorite movies is āFifth Elementā. It wowed me with futuristic predictions when I was a kid and Iām impressed by the number of these predictions that have already come true. Self-driving cars, video calls and smart TV, personalized ads and identity scanning. Sci-fi movies and books gave us many ideas and some are being implemented as we speak. But we often get ahead of ourselves:
Flying cars,Colonized planets, Human-like AI: not yet, Time travel, Mind-machine neural interfaces for everyone: Only in experimental stages (e.g. Neuralink).
Cyberpunk dystopias: Some vibes (neon signs + inequality + surveillance), but not total dystopia (thankfully).
On the bright side, we predict that the working hours should drop as Ai becomes our helper and there shouldnāt be a need to work 8 hours/day. Nobody knows for sure but we can require that from legislation. Instead of waiting to see what the government and billionaires come up with, I say we should design our own future.
So, we as humans, when we donāt know something - fear takes over. The same thing happened during the industrial revolution. In the Industrial Era, machines didnāt steal jobsāthey transformed them but people were scared about their jobs. The AI era is making similar changes except it feels like robots will take the center stage instead of a human. First off, even when it comes to the hottest space in the military - drones, Ai does a fraction of work. AI algorithms enable real-time decision-making, obstacle avoidance, and mission optimization making drones far more autonomous and capable than traditional remote-controlled aircraft. Key technologies include computer vision for object detection, GPS-enhanced navigation, and neural networks for learning and adaptation. But guess what? There are only 2 companies right now that utilize Ai in drones to make autonomous decisions - Skydio and DJI.
Database Benchmarking for Performance Masterclass: Session 2 - Data Modeling ...
Database Benchmarking for Performance Masterclass: Session 2 - Data Modeling ...ScyllaDB
Ā
Specific best practices and pitfalls for benchmarking popular high-performance databases.Mastering AI Workflows with FME by Mark DoĢring
Mastering AI Workflows with FME by Mark DoĢringSafe Software
Ā
Harness the full potential of AI with FME: From creating high-quality training data to optimizing models and utilizing results, FME supports every step of your AI workflow. Seamlessly integrate a wide range of models, including those for data enhancement, forecasting, image and object recognition, and large language models. Customize AI models to meet your exact needs with FMEās powerful tools for training, optimization, and seamless integrationAgentic AI for Developers and Data Scientists Build an AI Agent in 10 Lines o...
Agentic AI for Developers and Data Scientists Build an AI Agent in 10 Lines o...All Things Open
Ā
Presented at All Things Open RTP Meetup
Presented by William Hill - Developer Advocate, NVIDIA
Title: Agentic AI for Developers and Data Scientists
Build an AI Agent in 10 Lines of Code and the Concepts Behind the Code
Abstract: In this talk we will demonstrate building a working data science AI agent in 10 lines of basic Python code in a Colab notebook. Our AI Agent will perform LLM prompt-driven visual analysis using open-source libraries. In this session we will show how to develop an AI Agent using GPUs through NVIDIAās developer program and Google Colab notebooks. After coding our AI Agent, we will break down the 10 lines of code. We will show the key components and open source library integrations that enable the agent's functionality, focusing on practical implementation details and then the theoretical concepts. The presentation concludes with a survey of current LLM technologies and the latest trends in developing AI applications for enthusiasts and enterprisesFrom Manual to Auto Searching- FME in the Driver's Seat
From Manual to Auto Searching- FME in the Driver's SeatSafe Software
Ā
Finding a specific car online can be a time-consuming task, especially when checking multiple dealer websites. A few years ago, I faced this exact problem while searching for a particular vehicle in New Zealand. The local classified platform, Trade Me (similar to eBay), wasnāt yielding any results, so I expanded my search to second-hand dealer sitesāonly to realise that periodically checking each one was going to be tedious. Thatās when I noticed something interesting: many of these websites used the same platform to manage their inventories. Recognising this, I reverse-engineered the platformās structure and built an FME workspace that automated the search process for me. By integrating API calls and setting up periodic checks, I received real-time email alerts when matching cars were listed. In this presentation, Iāll walk through how I used FME to save hours of manual searching by creating a custom car-finding automation system. While FME canāt buy a car for youāyetāit can certainly help you find the one youāre after!Curietech AI in action - Accelerate MuleSoft development
Curietech AI in action - Accelerate MuleSoft developmentshyamraj55
Ā
CurieTech AI in Action ā Accelerate MuleSoft Development
Overview:
This presentation demonstrates how CurieTech AIās purpose-built agents empower MuleSoft developers to create integration workflows faster, more accurately, and with less manual effort
linkedin.com
+12
curietech.ai
+12
meetups.mulesoft.com
+12
.
Key Highlights:
Dedicated AI agents for every stage: Coding, Testing (MUnit), Documentation, Code Review, and Migration
curietech.ai
+7
curietech.ai
+7
medium.com
+7
DataWeave automation: Generate mappings from tables or samplesā95%+ complete within minutes
linkedin.com
+7
curietech.ai
+7
medium.com
+7
Integration flow generation: Auto-create Mule flows based on specificationsāspeeds up boilerplate development
curietech.ai
+1
medium.com
+1
Efficient code reviews: Gain intelligent feedback on flows, patterns, and error handling
youtube.com
+8
curietech.ai
+8
curietech.ai
+8
Test & documentation automation: Auto-generate MUnit test cases, sample data, and detailed docs from code
curietech.ai
+5
curietech.ai
+5
medium.com
+5
Why Now?
Achieve 10Ć productivity gains, slashing development time from hours to minutes
curietech.ai
+3
curietech.ai
+3
medium.com
+3
Maintain high accuracy with code quality matching or exceeding manual efforts
curietech.ai
+2
curietech.ai
+2
curietech.ai
+2
Ideal for developers, architects, and teams wanting to scale MuleSoft projects with AI efficiency
Conclusion:
CurieTech AI transforms MuleSoft development into an AI-accelerated workflowāletting you focus on innovation, not repetition."Database isolation: how we deal with hundreds of direct connections to the d...
"Database isolation: how we deal with hundreds of direct connections to the d...Fwdays
Ā
What can go wrong if you allow each service to access the database directly? In a startup, this seems like a quick and easy solution, but as the system scales, problems appear that no one could have guessed.
In my talk, I'll share Solidgate's experience in transforming its architecture: from the chaos of direct connections to a service-based data access model. I will talk about the transition stages, bottlenecks, and how isolation affected infrastructure support. I will honestly show what worked and what didn't. In short, we will analyze the controversy of this talk.Cracking the Code - Unveiling Synergies Between Open Source Security and AI.pdf
Cracking the Code - Unveiling Synergies Between Open Source Security and AI.pdfPriyanka Aash
Ā
Cracking the Code - Unveiling Synergies Between Open Source Security and AI9-1-1 Addressing: End-to-End Automation Using FME
9-1-1 Addressing: End-to-End Automation Using FMESafe Software
Ā
This session will cover a common use case for local and state/provincial governments who create and/or maintain their 9-1-1 addressing data, particularly address points and road centerlines. In this session, you'll learn how FME has helped Shelby County 9-1-1 (TN) automate the 9-1-1 addressing process; including automatically assigning attributes from disparate sources, on-the-fly QAQC of said data, and reporting. The FME logic that this presentation will cover includes: Table joins using attributes and geometry, Looping in custom transformers, Working with lists and Change detection.Security Tips for Enterprise Azure Solutions
Security Tips for Enterprise Azure SolutionsMichele Leroux Bustamante
Ā
Delivering solutions to Azure may involve a variety of architecture patterns involving your applications, APIs data and associated Azure resources that comprise the solution. This session will use reference architectures to illustrate the security considerations to protect your Azure resources and data, how to achieve Zero Trust, and why it matters. Topics covered will include specific security recommendations for types Azure resources and related network security practices. The goal is to give you a breadth of understanding as to typical security requirements to meet compliance and security controls in an enterprise solution.PyCon SG 25 - Firecracker Made Easy with Python.pdf
PyCon SG 25 - Firecracker Made Easy with Python.pdfMuhammad Yuga Nugraha
Ā
Explore the ease of managing Firecracker microVM with the firecracker-python. In this session, I will introduce the basics of Firecracker microVM and demonstrate how this custom SDK facilitates microVM operations easily. We will delve into the design and development process behind the SDK, providing a behind-the-scenes look at its creation and features. While traditional Firecracker SDKs were primarily available in Go, this module brings a simplicity of Python to the table.Wenn alles versagt - IBM Tape schĆ¼tzt, was zƤhlt! Und besonders mit dem neust...
Wenn alles versagt - IBM Tape schĆ¼tzt, was zƤhlt! Und besonders mit dem neust...Josef Weingand
Ā
IBM LTO10Connecting Data and Intelligence: The Role of FME in Machine Learning
Connecting Data and Intelligence: The Role of FME in Machine LearningSafe Software
Ā
In this presentation, we want to explore powerful data integration and preparation for Machine Learning. FME is known for its ability to manipulate and transform geospatial data, connecting diverse data sources into efficient and automated workflows. By integrating FME with Machine Learning techniques, it is possible to transform raw data into valuable insights faster and more accurately, enabling intelligent analysis and data-driven decision making.You are not excused! How to avoid security blind spots on the way to production
You are not excused! How to avoid security blind spots on the way to productionMichele Leroux Bustamante
Ā
Ad
Multi Domain REST API routing for Data Mesh based Data Products
- 1. Multi-domain REST API routing Building a standard naming convention for customer facing APIs in a data mesh Johan Louwers CEA ā EMEA APR-2024
- 2. The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, timing, and pricing of any features or functionality described for Oracleās products may change and remains at the sole discretion of Oracle Corporation. Safe harbor statement Copyright Ā© 2024, Oracle and/or its affiliates | Johan Louwers ā Chief Enterprise Architect
- 3. Fair warning from the presenter Copyright Ā© 2024, Oracle and/or its affiliates | Johan Louwers ā Chief Enterprise Architect 3 Commonly problems can be solved in multiple ways, this is just an example of one of the possible routes you can take to solve this specific problem.
- 4. API request routing for data mesh data products Copyright Ā© 2024, Oracle and/or its affiliates | Johan Louwers ā Chief Enterprise Architect 4 Problem Statement: There are several data products within separate sub-domains, and the aim is to expose them through REST APIs while maintaining consistent and logical naming conventions across these diverse domains.
- 5. API request routing for data mesh data products Copyright Ā© 2024, Oracle and/or its affiliates | Johan Louwers ā Chief Enterprise Architect 5 Solution 1: Establish a Fully Qualified Domain Name (FQDN), as an example we will use api.company.com, and employ routing and proxy functionality to direct specific paths like /products, /stock, and /orders to their corresponding data product subdomains, enabling them to handle the requests Downside; a central component in the form of API routing / proxy services which results in lesser autonomy of each individual business application domain. Als introducing an additional single point of failure
- 6. API request routing for data mesh data products Copyright Ā© 2024, Oracle and/or its affiliates | Johan Louwers ā Chief Enterprise Architect 6 Solution 2: this involves implementing subdomain-based routing, where each subdomain under the main domain corresponds to a specific data product. This approach eliminates an extra layer between the consumer and provider, streamlining the interaction process. Although this approach offers advantages, it's essential to consider the trade-offs. With subdomain-based routing, centralized control mechanisms, logging, and authentication functionalities are lost with the removal of the intermediate layer.
- 7. Thank You Johan Louwers 7 Copyright Ā© 2024, Oracle and/or its affiliates | Johan Louwers ā Chief Enterprise Architect July 4th, 2023