This talk was delivered in an Ignite talk format at the Access 2016 Conference in Fredericton, New Brunswick.
This talk covers the idea behind why the library technology industry needs a platform to help increase opportunity.
Description of the WireCloud mashup engine, and its integration with other FIWARE Generic Enablers. It defines basic components such as widget, operator, and mashup, and goes on with advanced fuctionality of WireCloud such as Wiring, HTTP proxy, preferences, and the APIs to other FIWARE GenericEnablers.
Finally, it contains a basic workshop on the usage of WireCloud. It exposes a chat application split into a widget and an operator.
As one of the developers behind „mealy“, Florian is responsible for developing and running the app's backend. mealy is a mobile app which aggregates awesome food blogger recipes and presents individual recipe suggestions to each user based on a recommender engine.
The mealy backend follows the microservice pattern and is built using a Java based stack (Spring framework, MongoDB, RESTful APIs and RabbitMQ).
In this talk, Florian shared insights how mealy ensures constant service availability. He explained why mealy chose Docker as a key infrastructure component and shared learnings about running a Docker based infrastructure at public cloud providers such as Amazon AWS or Microsoft Azure.
How to Effectively Build Web APIs for Microservices WSO2
Presentation by:
Indika Sampath, Senior Technical Lead, WSO2
Rajith Roshan, Technical Lead, WSO2
In modern microservices architectures, a simple API request is deconstructed and decoupled into fine-grained API requests. Multiple microservices that work in collaboration handles these API requests. Under the hoods, these microservices connect to other microservices and run complex integration logic.
By using the correct tools and following industry standards, developers can build their microservices integration layer as well as the web API layer more efficiently and effectively.
WebRTC is an open-source project from Google that allows real-time communication like voice calls, video chat, and file sharing directly in the browser without plugins. It uses APIs to handle media capture, streaming and peer-to-peer data transmission between browsers. Supported browsers include Chrome, Firefox, Opera, and Android versions of Chrome and Firefox.
Martin Danielsson presented on API Management with wicked.haufe.io. API Management provides discoverability and self-service access to APIs for developers, monitors traffic to provide usage insights, and protects APIs from misuse through security procedures and policies. Wicked.haufe.io is an open source API Management platform based on Mashape Kong that provides features like rate limiting, OAuth 2.0 support, and a developer portal with self signup. It is designed to run in Docker and deploy on any infrastructure for machine-to-machine communication, single page applications, and mobile apps. The presentation demonstrated wicked.haufe.io functionality through a live demo.
Creating and Managing Technical Content for Open Source ProductsWSO2
Open source has not just changed the way we think about creating and selling products—it has also changed the way we teach people to use those products. Smart companies no longer keep technical content under lock and key. Rather, they freely distribute information with the goal of making as many people successful with their products as possible. In this webinar, we'll look at strategies for creating and managing technical content to support open source products, including:
The advantages of open content
The content release cycle
Tools and platforms for content distribution
Enabling community participation
Licensing
Description of the WireCloud mashup engine, and its integration with other FIWARE Generic Enablers. It defines basic components such as widget, operator, and mashup, and goes on with advanced fuctionality of WireCloud such as Wiring, HTTP proxy, preferences, and the APIs to other FIWARE GenericEnablers.
Finally, it contains a basic workshop on the usage of WireCloud. It exposes a chat application split into a widget and an operator.
As one of the developers behind „mealy“, Florian is responsible for developing and running the app's backend. mealy is a mobile app which aggregates awesome food blogger recipes and presents individual recipe suggestions to each user based on a recommender engine.
The mealy backend follows the microservice pattern and is built using a Java based stack (Spring framework, MongoDB, RESTful APIs and RabbitMQ).
In this talk, Florian shared insights how mealy ensures constant service availability. He explained why mealy chose Docker as a key infrastructure component and shared learnings about running a Docker based infrastructure at public cloud providers such as Amazon AWS or Microsoft Azure.
How to Effectively Build Web APIs for Microservices WSO2
Presentation by:
Indika Sampath, Senior Technical Lead, WSO2
Rajith Roshan, Technical Lead, WSO2
In modern microservices architectures, a simple API request is deconstructed and decoupled into fine-grained API requests. Multiple microservices that work in collaboration handles these API requests. Under the hoods, these microservices connect to other microservices and run complex integration logic.
By using the correct tools and following industry standards, developers can build their microservices integration layer as well as the web API layer more efficiently and effectively.
WebRTC is an open-source project from Google that allows real-time communication like voice calls, video chat, and file sharing directly in the browser without plugins. It uses APIs to handle media capture, streaming and peer-to-peer data transmission between browsers. Supported browsers include Chrome, Firefox, Opera, and Android versions of Chrome and Firefox.
Martin Danielsson presented on API Management with wicked.haufe.io. API Management provides discoverability and self-service access to APIs for developers, monitors traffic to provide usage insights, and protects APIs from misuse through security procedures and policies. Wicked.haufe.io is an open source API Management platform based on Mashape Kong that provides features like rate limiting, OAuth 2.0 support, and a developer portal with self signup. It is designed to run in Docker and deploy on any infrastructure for machine-to-machine communication, single page applications, and mobile apps. The presentation demonstrated wicked.haufe.io functionality through a live demo.
Creating and Managing Technical Content for Open Source ProductsWSO2
Open source has not just changed the way we think about creating and selling products—it has also changed the way we teach people to use those products. Smart companies no longer keep technical content under lock and key. Rather, they freely distribute information with the goal of making as many people successful with their products as possible. In this webinar, we'll look at strategies for creating and managing technical content to support open source products, including:
The advantages of open content
The content release cycle
Tools and platforms for content distribution
Enabling community participation
Licensing
Resource Discovery Infrastructure - what if we were starting from scratch?ostephens
This document discusses the history and evolution of library cataloging and metadata standards over time. It mentions several important standards, systems, and leaders in the field such as Ranganathan's 5 Laws of Library Science, MARC, AACR, RDA, Z39.50, and OCLC. It also acknowledges several important figures and resources that advanced the field such as Melvil Dewey, Charles Cutter, and Sir Tim Berners-Lee through the development of new technologies.
The document discusses trends in digital media and mobile technology and their implications for libraries. It notes that e-readers like Kindle are growing in popularity, more people have mobile phones, and mobile networks are expanding access in developing areas. While print is at risk, this also presents opportunities for libraries to rethink their services and focus on engaging experiences rather than just collections. The future of libraries depends on adapting to changing formats and finding new ways to contribute to knowledge production and consumption in their communities.
This document discusses the value and costs of library infrastructure systems. It notes that total library system costs, including staff costs, can exceed $764,000 annually for a research library. New "next generation" library services platforms aim to better integrate print and electronic resources, improve workflows, and provide analytics across multiple libraries. However, these new systems require libraries to essentially "start over" and may initially lack functionality, though they promise reduced total costs of ownership over time. The document examines perspectives from libraries, vendors, and consultants on the potential benefits and business cases for migrating to a new library services platform.
Uploading the presentation given at the OpenStack Summit, Austin in April, 2016. The video link is here ,
https://www.openstack.org/videos/video/multi-tenancy-for-docker-containers-with-keystone-and-adding-quota-limits
Building a Global-Scale Multi-Tenant Cloud Platform on AWS and Docker: Lesson...Felix Gessert
In this talk we share the lessons learned while building out the Baqend Cloud platform on AWS and Docker. Baqend’s AWS-hosted architecture consists of a caching CDN-Layer, global and local load balancing, a group of REST and Node.js servers and a database cluster with Redis and MongoDB. As customers have their own set of containerized REST and Node servers, we needed a cluster that on the one hand is horizontally scalable and on the other hand easily manageable and fault-tolerant from an operational perspective. Today there are at least 4 popular systems that claim to support this:
- Kubernetes
- Apache Mesos
- Docker Swarm
- AWS Elastic Container Service (ECS)
Thinking that ECS would certainly be the easiest option on AWS, we started building our cluster on it. We quickly came to realize that while ECS was astoundingly stable and easy to use there were inherent limitations that could not be worked around. An old Docker version, missing network isolation, no means of parameterizing task and forced memory constraints are major limitations of ECS we will talk about. Seeing the daunting operational overhead of running Kubernetes or Mesos in practice we turned to Docker’s native clustering solution Swarm. We will present how Swarm works with both Docker and AWS and highlight the advantages and downsides compared to Amazon’s ECS.
This operational plan aims to increase enrollment, improve student welfare, and develop faculty. Key strategies include intensive enrollment campaigns, upgrading facilities, strengthening guidance services, offering scholarships, and providing faculty development opportunities. Success will be measured through indicators such as enrollment numbers, student satisfaction ratings, and the percentage of faculty completing doctoral programs. Regular monitoring and evaluation of activities will allow corrective measures to ensure goals are achieved.
The document discusses trends in open source software. It notes that every company is becoming a software company and must understand software to survive. Open source is also growing, with 78% of companies now using open source software and 63% participating in open source projects. It discusses how companies like Google, Facebook, and Netflix are increasingly open sourcing their projects. It also summarizes the rise of open source programs in companies and the formation of the TODO Group, a collaboration of companies to share best practices around open source programs. The TODO Group partners with the Linux Foundation to help establish it as a legitimate entity.
My opening keynote for the 2016 Nordic APIs Platform Summit held in Stockholm, Sweden. In it I describe the 6 Insights that guide Nordic APIs content and events, including API Platforms, API Strategy, API Business Models, API Strategy, API Design, API Security, and API Marketing.
Introduction to The 6 Insights of API Practice (Bill Doerrfeld)Nordic APIs
This is a session given by Bill Doerrfeld at Nordic APIs 2016 Platform Summit on October 25th, in Stockholm Sweden.
Description:
At Nordic APIs, our goal is to help businesses make smart tech decisions using APIs. To that end, via events and content Nordic APIs has treaded the business and technical sides to consider holistic best practices for providing an API. In this introductory Summit keynote talk, I’ll introduce what we’ve learned in the form of 6 core tenants of API practice which we’ve also designed this conference to address. Together they define a functional and evolving API:
Platformification: Becoming an API-first company means undergoing a platformification process. This represents a global trend that many argue needs to be adopted to keep your business competitive within the digital economy.
Strategy: Even before development begins, it’s important to consider your core API strategy. This is a defensible position that aligns your tech with platform goals, strategically exposing internal assets catered to an industry niche.
Business Models: APIs have the power to improve efficiency, reduce overhead cost, open up complementary revenue streams, extend R&D, or even alter an existing business model entirely. Thus, you’ll want to determine the right monetization method that improves overall business and leads to end profitability.
Security: With new major data breaches reaching the public ear every month, the importance of digital security can never be underestimated. For APIs, much of that lies in monitoring usage, access management, and identity control.
Design: No developer wants to use an API with an ugly developer portal, unintuitive URL structures, outdated technology, or terrible lag time. In order to keep your developer consumer happy, paint the API portal and overall developer experience with an aesthetic brush.
Marketing: In order to spark adoption, you need to have more than awesome functionality. I’ll review evangelism and discovery techniques you can use to get an API in the hands of more developer users.
We’ll look at specific successful implementations of these philosophies in the wild, and mention examples from our blog and eBook content that have brought in industry experts to share their insights. I’ll initiate dialogue and open the conference up to see where we’re heading. What you can get out of embracing the core tenants of API practice?
This document provides an overview of open source software and recommendations for companies adopting open source. It discusses how open source can accelerate projects and attract talent. It profiles companies like Adobe, Netflix, Oracle, Samsung, and Microsoft that contribute to open source despite not being commonly associated with it. The document outlines how to launch an open source project, including using an open source license, README, contribution guidelines, and code of conduct. It also discusses roles in open source projects and various open source business models. The recommendations encourage companies to publish independent components on GitHub, take releases from GitHub, and create developer websites to engage with the open source community.
Using Open Source and Open Standards in the Platform gamePatrick Chanezon
This document discusses Docker Inc.'s efforts to establish an open platform for containers through open source and open standards. It summarizes Docker's work on projects like runc, OCI, and containerd that established the building blocks for container technologies. It also notes Docker's rapid growth from 2013 to 2016 and transition from focusing initially on developers to later prioritizing orchestration and production usage through projects like Docker Swarm. The document evaluates how Docker's open source strategy helped establish it as the dominant player in the container space initially before other companies began competing in the container platform market.
UiPath Education Series - How to Learn UiPath RPA Development and Land a JobDianaGray10
Deep dive into how to learn about UiPath RPA and Land a job in 2023:
📌 Share the personal journey of Speaker
📌 Resources for learning UiPath
📌 How to create an RPA portfolio
📌 How to reach the recruiters
📌 How to become successful in your RPA career
This document provides a history of Google's Developer Relations program from 2006 to 2011. It discusses how DevRel was originally founded in the US in 2006 and has since expanded globally. Key events discussed include the launches of Android, Google Maps API, and Google I/O conference. The document outlines DevRel's mission to make Google platforms the ecosystem of choice for developers and describes the roles of Developer Advocates, Engineers, and Program Managers. It also summarizes some of the programs DevRel runs like IO, Developer Days, GTUGs, and Developer Labs.
This is a presentation on OpenSocial in the Enterprise given at Devfest 2009 in Buenos Aires Argentina on Nov 17, 2009 by Google Developer Advocate, Chris Schalk, eXo Platform CEO Benjamin Mestrallet, and Globant's Bruno Rovagnati
Global Open Source Development 2011-2014 Review and 2015 ForecastSammy Fung
1) The document reviews global open source development from 2011-2014 and provides a forecast for 2015. Key technologies discussed include JavaScript, Node.js, Python, R, and open data.
2) Major open source organizations discussed include Mozilla, the Python Software Foundation, and the Open Knowledge Foundation. Events like PyCon and the Open Data Day hackathon are also mentioned.
3) The document concludes by discussing opportunities to get involved in and contribute to the global open source community, such as upcoming events in Hong Kong like HKOSCon 2015 and PyCon HK 2015.
API Marketing: First Comes Usability, Then DiscoverabilityBill Doerrfeld
How do we increase developer conversion? In this session, I cover some ways to market your API, on and offline. You'll learn the major directories and marketplaces to add your API to, and how to set up your service for machine-readable discover. I also discuss Search Engine Optimization (SEO) suggestions for developer portals, and API definitions like OpenAPI Specification. Lastly, I reiterate the importance of creating and sharing evergreen knowledge.
LF_APIStrat17_API Marketing: First Comes Usability, then DiscoverabilityLF_APIStrat
This document discusses strategies for increasing API discoverability and developer onboarding. It recommends focusing first on usability by improving documentation, API definitions, and developer portals. It also stresses the importance of visibility strategies like SEO, metadata standards, and profiling APIs in directories. Finally, it highlights advocacy approaches like evangelism, community building, and thought leadership content to promote APIs. The overall message is that a balanced approach across usability, visibility, and advocacy is key to making APIs discoverable and attracting developers.
Publishing API documentation -- WorkshopTom Johnson
These slides are from the REST API documentation workshop that I gave at the STC Summit 2015. For more details, see http://idratherbewriting.com/publishingapidocs.
This document provides information about becoming an open source contributor, including defining open source software, discussing why people should get involved, and providing tips for both contributors and maintainers. It highlights how open source is used widely, encourages finding approachable projects to contribute to, and emphasizes the importance of things like writing code, submitting pull requests, following guidelines, and being supportive and patient. The goal is to help people start and successfully contribute to the open source community.
Flink's Journey from Academia to the ASFFabian Hueske
Apache Flink is a project with a very active, supportive, and continuously growing community. Last year, Flink was among the top ten projects of the Apache Software Foundation with the most traffic on user and development mailing lists. Looking back, Flink started as a research prototype developed by three PhD students at TU Berlin in 2009. In 2014, the developers donated the code base to the ASF and joined the newly founded Apache Flink incubator project. Within three years, Flink grew into a healthy project and gained a lot of momentum.
In my presentation, I will discuss Flink's journey from an academic research project to one of the most active projects of the Apache Software Foundation. I will talk about the academic roots of the project, how the original developers got introduced to the ASF, Flink's incubation phase, and how its community evolved after it graduated and became an ASF top-level project. My talk will focus on the decisions, efforts, and circumstances that helped to grow a vital and welcoming open source community.
API Discovery: Visibility, Usability, and AdvocacyBill Doerrfeld
The document discusses strategies for increasing API adoption, including improving API discovery, visibility, usability, and advocacy. It provides recommendations across these areas, such as improving SEO, using API directories, enhancing documentation and portals, developing thought leadership content, and building developer communities through evangelism and support. The key message is that a balanced, multi-pronged approach is needed to effectively market an API and drive adoption.
Resource Discovery Infrastructure - what if we were starting from scratch?ostephens
This document discusses the history and evolution of library cataloging and metadata standards over time. It mentions several important standards, systems, and leaders in the field such as Ranganathan's 5 Laws of Library Science, MARC, AACR, RDA, Z39.50, and OCLC. It also acknowledges several important figures and resources that advanced the field such as Melvil Dewey, Charles Cutter, and Sir Tim Berners-Lee through the development of new technologies.
The document discusses trends in digital media and mobile technology and their implications for libraries. It notes that e-readers like Kindle are growing in popularity, more people have mobile phones, and mobile networks are expanding access in developing areas. While print is at risk, this also presents opportunities for libraries to rethink their services and focus on engaging experiences rather than just collections. The future of libraries depends on adapting to changing formats and finding new ways to contribute to knowledge production and consumption in their communities.
This document discusses the value and costs of library infrastructure systems. It notes that total library system costs, including staff costs, can exceed $764,000 annually for a research library. New "next generation" library services platforms aim to better integrate print and electronic resources, improve workflows, and provide analytics across multiple libraries. However, these new systems require libraries to essentially "start over" and may initially lack functionality, though they promise reduced total costs of ownership over time. The document examines perspectives from libraries, vendors, and consultants on the potential benefits and business cases for migrating to a new library services platform.
Uploading the presentation given at the OpenStack Summit, Austin in April, 2016. The video link is here ,
https://www.openstack.org/videos/video/multi-tenancy-for-docker-containers-with-keystone-and-adding-quota-limits
Building a Global-Scale Multi-Tenant Cloud Platform on AWS and Docker: Lesson...Felix Gessert
In this talk we share the lessons learned while building out the Baqend Cloud platform on AWS and Docker. Baqend’s AWS-hosted architecture consists of a caching CDN-Layer, global and local load balancing, a group of REST and Node.js servers and a database cluster with Redis and MongoDB. As customers have their own set of containerized REST and Node servers, we needed a cluster that on the one hand is horizontally scalable and on the other hand easily manageable and fault-tolerant from an operational perspective. Today there are at least 4 popular systems that claim to support this:
- Kubernetes
- Apache Mesos
- Docker Swarm
- AWS Elastic Container Service (ECS)
Thinking that ECS would certainly be the easiest option on AWS, we started building our cluster on it. We quickly came to realize that while ECS was astoundingly stable and easy to use there were inherent limitations that could not be worked around. An old Docker version, missing network isolation, no means of parameterizing task and forced memory constraints are major limitations of ECS we will talk about. Seeing the daunting operational overhead of running Kubernetes or Mesos in practice we turned to Docker’s native clustering solution Swarm. We will present how Swarm works with both Docker and AWS and highlight the advantages and downsides compared to Amazon’s ECS.
This operational plan aims to increase enrollment, improve student welfare, and develop faculty. Key strategies include intensive enrollment campaigns, upgrading facilities, strengthening guidance services, offering scholarships, and providing faculty development opportunities. Success will be measured through indicators such as enrollment numbers, student satisfaction ratings, and the percentage of faculty completing doctoral programs. Regular monitoring and evaluation of activities will allow corrective measures to ensure goals are achieved.
The document discusses trends in open source software. It notes that every company is becoming a software company and must understand software to survive. Open source is also growing, with 78% of companies now using open source software and 63% participating in open source projects. It discusses how companies like Google, Facebook, and Netflix are increasingly open sourcing their projects. It also summarizes the rise of open source programs in companies and the formation of the TODO Group, a collaboration of companies to share best practices around open source programs. The TODO Group partners with the Linux Foundation to help establish it as a legitimate entity.
My opening keynote for the 2016 Nordic APIs Platform Summit held in Stockholm, Sweden. In it I describe the 6 Insights that guide Nordic APIs content and events, including API Platforms, API Strategy, API Business Models, API Strategy, API Design, API Security, and API Marketing.
Introduction to The 6 Insights of API Practice (Bill Doerrfeld)Nordic APIs
This is a session given by Bill Doerrfeld at Nordic APIs 2016 Platform Summit on October 25th, in Stockholm Sweden.
Description:
At Nordic APIs, our goal is to help businesses make smart tech decisions using APIs. To that end, via events and content Nordic APIs has treaded the business and technical sides to consider holistic best practices for providing an API. In this introductory Summit keynote talk, I’ll introduce what we’ve learned in the form of 6 core tenants of API practice which we’ve also designed this conference to address. Together they define a functional and evolving API:
Platformification: Becoming an API-first company means undergoing a platformification process. This represents a global trend that many argue needs to be adopted to keep your business competitive within the digital economy.
Strategy: Even before development begins, it’s important to consider your core API strategy. This is a defensible position that aligns your tech with platform goals, strategically exposing internal assets catered to an industry niche.
Business Models: APIs have the power to improve efficiency, reduce overhead cost, open up complementary revenue streams, extend R&D, or even alter an existing business model entirely. Thus, you’ll want to determine the right monetization method that improves overall business and leads to end profitability.
Security: With new major data breaches reaching the public ear every month, the importance of digital security can never be underestimated. For APIs, much of that lies in monitoring usage, access management, and identity control.
Design: No developer wants to use an API with an ugly developer portal, unintuitive URL structures, outdated technology, or terrible lag time. In order to keep your developer consumer happy, paint the API portal and overall developer experience with an aesthetic brush.
Marketing: In order to spark adoption, you need to have more than awesome functionality. I’ll review evangelism and discovery techniques you can use to get an API in the hands of more developer users.
We’ll look at specific successful implementations of these philosophies in the wild, and mention examples from our blog and eBook content that have brought in industry experts to share their insights. I’ll initiate dialogue and open the conference up to see where we’re heading. What you can get out of embracing the core tenants of API practice?
This document provides an overview of open source software and recommendations for companies adopting open source. It discusses how open source can accelerate projects and attract talent. It profiles companies like Adobe, Netflix, Oracle, Samsung, and Microsoft that contribute to open source despite not being commonly associated with it. The document outlines how to launch an open source project, including using an open source license, README, contribution guidelines, and code of conduct. It also discusses roles in open source projects and various open source business models. The recommendations encourage companies to publish independent components on GitHub, take releases from GitHub, and create developer websites to engage with the open source community.
Using Open Source and Open Standards in the Platform gamePatrick Chanezon
This document discusses Docker Inc.'s efforts to establish an open platform for containers through open source and open standards. It summarizes Docker's work on projects like runc, OCI, and containerd that established the building blocks for container technologies. It also notes Docker's rapid growth from 2013 to 2016 and transition from focusing initially on developers to later prioritizing orchestration and production usage through projects like Docker Swarm. The document evaluates how Docker's open source strategy helped establish it as the dominant player in the container space initially before other companies began competing in the container platform market.
UiPath Education Series - How to Learn UiPath RPA Development and Land a JobDianaGray10
Deep dive into how to learn about UiPath RPA and Land a job in 2023:
📌 Share the personal journey of Speaker
📌 Resources for learning UiPath
📌 How to create an RPA portfolio
📌 How to reach the recruiters
📌 How to become successful in your RPA career
This document provides a history of Google's Developer Relations program from 2006 to 2011. It discusses how DevRel was originally founded in the US in 2006 and has since expanded globally. Key events discussed include the launches of Android, Google Maps API, and Google I/O conference. The document outlines DevRel's mission to make Google platforms the ecosystem of choice for developers and describes the roles of Developer Advocates, Engineers, and Program Managers. It also summarizes some of the programs DevRel runs like IO, Developer Days, GTUGs, and Developer Labs.
This is a presentation on OpenSocial in the Enterprise given at Devfest 2009 in Buenos Aires Argentina on Nov 17, 2009 by Google Developer Advocate, Chris Schalk, eXo Platform CEO Benjamin Mestrallet, and Globant's Bruno Rovagnati
Global Open Source Development 2011-2014 Review and 2015 ForecastSammy Fung
1) The document reviews global open source development from 2011-2014 and provides a forecast for 2015. Key technologies discussed include JavaScript, Node.js, Python, R, and open data.
2) Major open source organizations discussed include Mozilla, the Python Software Foundation, and the Open Knowledge Foundation. Events like PyCon and the Open Data Day hackathon are also mentioned.
3) The document concludes by discussing opportunities to get involved in and contribute to the global open source community, such as upcoming events in Hong Kong like HKOSCon 2015 and PyCon HK 2015.
API Marketing: First Comes Usability, Then DiscoverabilityBill Doerrfeld
How do we increase developer conversion? In this session, I cover some ways to market your API, on and offline. You'll learn the major directories and marketplaces to add your API to, and how to set up your service for machine-readable discover. I also discuss Search Engine Optimization (SEO) suggestions for developer portals, and API definitions like OpenAPI Specification. Lastly, I reiterate the importance of creating and sharing evergreen knowledge.
LF_APIStrat17_API Marketing: First Comes Usability, then DiscoverabilityLF_APIStrat
This document discusses strategies for increasing API discoverability and developer onboarding. It recommends focusing first on usability by improving documentation, API definitions, and developer portals. It also stresses the importance of visibility strategies like SEO, metadata standards, and profiling APIs in directories. Finally, it highlights advocacy approaches like evangelism, community building, and thought leadership content to promote APIs. The overall message is that a balanced approach across usability, visibility, and advocacy is key to making APIs discoverable and attracting developers.
Publishing API documentation -- WorkshopTom Johnson
These slides are from the REST API documentation workshop that I gave at the STC Summit 2015. For more details, see http://idratherbewriting.com/publishingapidocs.
This document provides information about becoming an open source contributor, including defining open source software, discussing why people should get involved, and providing tips for both contributors and maintainers. It highlights how open source is used widely, encourages finding approachable projects to contribute to, and emphasizes the importance of things like writing code, submitting pull requests, following guidelines, and being supportive and patient. The goal is to help people start and successfully contribute to the open source community.
Flink's Journey from Academia to the ASFFabian Hueske
Apache Flink is a project with a very active, supportive, and continuously growing community. Last year, Flink was among the top ten projects of the Apache Software Foundation with the most traffic on user and development mailing lists. Looking back, Flink started as a research prototype developed by three PhD students at TU Berlin in 2009. In 2014, the developers donated the code base to the ASF and joined the newly founded Apache Flink incubator project. Within three years, Flink grew into a healthy project and gained a lot of momentum.
In my presentation, I will discuss Flink's journey from an academic research project to one of the most active projects of the Apache Software Foundation. I will talk about the academic roots of the project, how the original developers got introduced to the ASF, Flink's incubation phase, and how its community evolved after it graduated and became an ASF top-level project. My talk will focus on the decisions, efforts, and circumstances that helped to grow a vital and welcoming open source community.
API Discovery: Visibility, Usability, and AdvocacyBill Doerrfeld
The document discusses strategies for increasing API adoption, including improving API discovery, visibility, usability, and advocacy. It provides recommendations across these areas, such as improving SEO, using API directories, enhancing documentation and portals, developing thought leadership content, and building developer communities through evangelism and support. The key message is that a balanced, multi-pronged approach is needed to effectively market an API and drive adoption.
The document discusses several emerging technologies including del.icio.us, wikis, blogs, podcasts, and the evolution of the World Wide Web from Web 1.0 to Web 2.0 to Web 3.0 (proposed Web 3.0). Del.icio.us is described as a social bookmarking service that allows flexible organization of bookmarks using tags. Wikis are defined as collaborative websites that allow users to edit pages. Blogs, podcasts, and their key features are also summarized. The differences between Web 1.0, 2.0, and the vision for Web 3.0 are outlined at a high level.
Online Journal Management using Open Journal Systems (OJS)Ina Smith
This document provides an overview of using Open Journal Systems (OJS) for online journal management. OJS is an open source journal management and publishing system that allows journals to accept submissions, peer review, edit and publish articles online. It has benefits such as being locally controlled, providing online submission and management tools, and building capacity for journals with fewer resources. The document discusses implementation of OJS, training, and continued support available through organizations like ASSAf and PKP. It also covers topics like registering with indexes, rights management, analytics and measuring impact.
This document provides an overview of using Open Journal Systems (OJS) for online journal management. OJS is an open source journal management and publishing system that allows journals to accept submissions, peer review, edit and publish articles online. It has benefits such as being locally controlled, providing online submission and management tools, and building capacity for journals with fewer resources. The document discusses implementing and customizing OJS, ensuring academic integrity of journals, registering with indexes, and measuring journal impact.
Reinventing Discovery: An Analysis of Big DataAndrew Nagy
As the late Steve Jobs would say, don’t listen to your customers, they don’t know what they want. Usability studies and live user analysis provide valuable feedback about your product or web site in terms of how the tool is used, but listening to the users about what they want out of the tool can result in a “whack-a-mole” scenario where you solve a problem for one user, but create new problems for other users. Analyzing usage data can provide a very different perspective on how live users actually use the tool and allow you to identify different personas and use cases. This talk will share how Serials Solutions collects and analyzes a dataset of queries and clicks generated by millions of users at hundreds of libraries around the world to find behaviors, patterns, successes and failures in the interface design and search algorithms and then how we leverage that to improve and redesign. We will share the details of our custom developed data warehouse system and how we leverage these tools to perform our analysis. We will also share with you before-and-afters that were developed based on the results of the ongoing analysis.
Web Scale Discovery From Start To FinishAndrew Nagy
1) Building a unified discovery index requires acquiring content from thousands of publishers and normalizing billions of records, which is a massive undertaking that requires significant resources.
2) The process involves acquiring content via various methods, deduplicating records from different sources, normalizing variations in formatting, and developing complex models for indexing and relevancy.
3) Developing a discovery solution as software-as-a-service requires an agile development approach with frequent iterations to incorporate client feedback.
The document summarizes the development history of VuFind, an open source library resource discovery portal, from its inception at Villanova University in 2006 to its release as open source software in 2007. It describes how the idea was to create a single interface for searching the library catalog and databases, and how the developers aimed to make it compatible with different library systems and easy to install. It also discusses the benefits and challenges of making it an open source project, including gaining collaborators but also requiring support and project switching costs.
VuFind is described as a "next generation catalog" or "resource discovery system" that aims to help users discover resources, rather than just find known items. It seeks to eliminate silos between a library's website, catalog, article search, and digital library by integrating them into a single interface. VuFind loads data from various sources like MARC data, OAI, and Z39.50, and can integrate with major integrated library systems by authenticating via SIP2 and displaying live item status and holdings data. A live demo of VuFind's capabilities is available at www.vufind.org.
Web-Scale Discovery: From start to for sale in one yearAndrew Nagy
This document discusses the major work required to build a unified discovery index from start to being ready for sale within one year. It notes that building such an index involves acquiring content from thousands of publishers, normalizing and deduplicating over 75 million records stored across 75 terabytes of data, and developing complex indexing models to deliver relevant search results. The process of acquiring, cleaning, and indexing vast amounts of content from various sources into a single searchable index is described as a very messy job that requires strong partnerships, funding, experienced teams, and ongoing maintenance.
Most important New features of Oracle 23c for DBAs and Developers. You can get more idea from my youtube channel video from https://youtu.be/XvL5WtaC20A
E-commerce Development Services- Hornet DynamicsHornet Dynamics
For any business hoping to succeed in the digital age, having a strong online presence is crucial. We offer Ecommerce Development Services that are customized according to your business requirements and client preferences, enabling you to create a dynamic, safe, and user-friendly online store.
Flutter is a popular open source, cross-platform framework developed by Google. In this webinar we'll explore Flutter and its architecture, delve into the Flutter Embedder and Flutter’s Dart language, discover how to leverage Flutter for embedded device development, learn about Automotive Grade Linux (AGL) and its consortium and understand the rationale behind AGL's choice of Flutter for next-gen IVI systems. Don’t miss this opportunity to discover whether Flutter is right for your project.
The Key to Digital Success_ A Comprehensive Guide to Continuous Testing Integ...kalichargn70th171
In today's business landscape, digital integration is ubiquitous, demanding swift innovation as a necessity rather than a luxury. In a fiercely competitive market with heightened customer expectations, the timely launch of flawless digital products is crucial for both acquisition and retention—any delay risks ceding market share to competitors.
Hand Rolled Applicative User ValidationCode KataPhilip Schwarz
Could you use a simple piece of Scala validation code (granted, a very simplistic one too!) that you can rewrite, now and again, to refresh your basic understanding of Applicative operators <*>, <*, *>?
The goal is not to write perfect code showcasing validation, but rather, to provide a small, rough-and ready exercise to reinforce your muscle-memory.
Despite its grandiose-sounding title, this deck consists of just three slides showing the Scala 3 code to be rewritten whenever the details of the operators begin to fade away.
The code is my rough and ready translation of a Haskell user-validation program found in a book called Finding Success (and Failure) in Haskell - Fall in love with applicative functors.
Project Management: The Role of Project Dashboards.pdfKarya Keeper
Project management is a crucial aspect of any organization, ensuring that projects are completed efficiently and effectively. One of the key tools used in project management is the project dashboard, which provides a comprehensive view of project progress and performance. In this article, we will explore the role of project dashboards in project management, highlighting their key features and benefits.
Liberarsi dai framework con i Web Component.pptxMassimo Artizzu
In Italian
Presentazione sulle feature e l'utilizzo dei Web Component nell sviluppo di pagine e applicazioni web. Racconto delle ragioni storiche dell'avvento dei Web Component. Evidenziazione dei vantaggi e delle sfide poste, indicazione delle best practices, con particolare accento sulla possibilità di usare web component per facilitare la migrazione delle proprie applicazioni verso nuovi stack tecnologici.
8 Best Automated Android App Testing Tool and Framework in 2024.pdfkalichargn70th171
Regarding mobile operating systems, two major players dominate our thoughts: Android and iPhone. With Android leading the market, software development companies are focused on delivering apps compatible with this OS. Ensuring an app's functionality across various Android devices, OS versions, and hardware specifications is critical, making Android app testing essential.
What to do when you have a perfect model for your software but you are constrained by an imperfect business model?
This talk explores the challenges of bringing modelling rigour to the business and strategy levels, and talking to your non-technical counterparts in the process.
6. “It’s axiomatic that a vibrant
and healthy platform is
dependent on the value
created by partners who are
outside the platform itself. If
a platform is too closed , then
partners cannot or will not
contribute”
Ken Chad, Amigos Online Conference, Sept 15, 2016
16. IndexData
• Development
Begins
• Mid 2015
Public Code
• FOLIO codebase
public on GitHub
• August 2016
Modules
• Special Interest
Groups Forming
• Core Module
Development
• October 2016
Platform
• APIs Formalized
• App Market formed
• Core Module
Development
• Extension App
Development
• 2017
Go Live
• First Library Goes
Live
• 2018
17. IndexData
• Development
Begins
• Mid 2015
Public Code
• FOLIO codebase
public on GitHub
• August 2016
Modules
• Special Interest
Groups Forming
• Core Module
Development
• October 2016
Platform
• APIs Formalized
• App Market formed
• Core Module
Development
• Extension App
Development
• 2017
Go Live
• First Library Goes
Live
• 2018
This talk is about Platform-as-a-Service
Platforms can make it very easy to build new products and services in a more efficient way
This platform is a collaborative open source project
The consolidation in the library automation industry has created a problem with a lack of competition and innovation. Let’s fix that.
In order to spark and support innovation – we need an open marketplace to increase competition and create opportunity
Platforms are a tool that allows developers and 3rd parties to easily create new tools and services
This is Library Platform as a Service
For those of who you are unfamiliar with the Platform as a Service concept – You’ve probably heard of Amazon’s Web Services
They are a collection of microservices that together can help build a powerful solution with out a tremendous amount of engineering work.
Another great example is Salesforce.com’s Force.com platform. It is again, a collection of microservices.
You do not have to worry about servers, infrastructure, networking – that is all provided for you as a service
The Internet of Things is a newly growing platform that companies from many industries are working on
This is my IOT platform in my home – I use products from different vendors to make up my ecosystem.
FOLIO is an open source platform. Designed to create and spark innovation. Creating an open marketplace to allow for new competition
The platform is designed into three components:
A system layer that contains data and configuration
An API layer to make it really easy to interface with the system layer
A UI Toolkit to make creating UIs easy and simple
By introducing a marketplace, developers can share their Apps and libraries can pick and choose the Apps that they want and need to support their workflows.
When will this all be done?
It started in 2015 by a development effort from IndexData.
Then in August of 2016, the code was made public on GitHub. An open slack channel, discuss forum and JIRA site has also been made available to support collaboration.
In 2018, there will be a solution that resembles an ILS sitting on top of the FOLIO platform along with an app marketplace.
Our future is bright, but we can only go there together! FOLIO Is a collaboration and we need as much support as we can get.
The future of libraries is open – please join the community.
We need your support.
We have a number of Special Interest Groups that you can join – from engineering groups to process and improvement groups.