Good code isn’t enough for a successful open source project. First of all, only you know how to use what you’ve made. Maybe it’s time for a little UI and UX help? At the very least some documentation! Next, how is anyone else going to find what you’ve created? And that’s only the beginning. Ruth Suehle, manager of Red Hat’s Open Source and Standards community leadership team, will take you through examples of the best and the worst, from projects large and small, to help you see what you need beyond your code to build a successful open source project and community.
Microservices with Apache Karaf and Apache CXF: Practical Experience – Andrei Shakirin
Today Microservices architecture is widely recognized and accepted by a lot of development teams. At the same time the people realize that this architecture has some restrictions and challenges.
Interesting that Microservices and OSGi architectures are very close. The talk will analyse the core ideas of both architectures and shows the benefits provided by the OSGi Eco system for Microservices developer.
Based on practical experience, the presenter will demonstrate the best engineering practices in design and development Microservices with Apache Karaf (powered by OSGi) including modularity, resilience, continuous delivery and testability.
One important aspect of Microservices architecture is communication using lightweight mechanisms. Apache CXF is the perfect choice for this. The talk will show how to design, secure, customize and document your Microservices APIs using Apache CXF
OSGi has evolved and matured beyond recognition over the last few years. It’s now easier than ever before, to build dynamic, modular Java applications to address the challenges imposed by ever growing and constantly changing business requirements. Despite that, OSGi seems to be far from receiving the appreciation it deserves.
In this talk I’d like to go over what OSGi community is (not) doing to attract “outsiders”. I’d argue it can do better. Based on observations and conversation from the last 2 years trying to advocate for OSGi among Java developers, I’ll try to position OSGi it in today’s reality of microservices, containers, automation, Java 9, … and bring the perspective of an “outsider” together with all the presumptions, fallacies and promises. Finally I’d like to share some ideas about addressing those, promote relevant OSGi parts and perhaps make it more attractive.
How I Built an Access Management System Using Java and Apache Directory Fortress – Shawn McKinney
This session describes the rationale for the Apache Fortress project. It examines requirements, specifications and designs for Access Management use cases. There will be an overview of the Apache Directory Fortress project along with a demo at the end.
Will the Apache Maturity Model Save Your Project? – Bertrand Delacretaz
The Apache Project Maturity Model ( http://s.apache.org/maturity-model ) was written to help explain how Apache projects work, in a modular way that allows it to be adopted partially by projects who operate outside of Apache. Will that model help save your fledgling project, or is that just a set of boring rules? Describing the reasoning behind the model’s items, with concrete examples from successful Apache projects, will help us find out and apply the model to our own projects in a helpful way.
I Will Not Attend Your Meeting, I’m an Open Source Person – Bertrand Delacretaz
Meetings are very costly for people who work on a Maker’s Schedule (as defined by Paul Graham, https://s.apache.org/ms), like software developers. Yet in many corporate environments meetings are the default way of addressing issues.
Due to their asynchronous and distributed modes of of operation, Open Source projects have over the years designed and refined an efficient way of collaborating without requiring face-to-face meetings.
Can we transpose this to corporate environments, to reduce the cost and aggravation of boring and unproductive meetings?
We think the answer is yes, if we can reproduce the constant flow of information and asynchronous decision making mechanisms of Open Source. This talk will show you how to implement these changes, based on Bertrand’s successful experience in corporate environments.
Why and How to Build CloudStack API Plug-ins (with a Real-World Example) – Mike Tutkowski
Apache CloudStack is a highly customizable cloud management platform. It enables developers to write plug-ins for a wide range of areas including, but not limited to, storage, networking, VM distribution across hosts, and API.
I would like to explain why it can be beneficial to extend CloudStack’s standard API with your own API commands and how to do this.
I walk the audience through a real-world example that demonstrates a business case for extending CloudStack’s API. During this process, you learn how to cleanly separate the API, business, and DB layers. At the end, you have transparently extended CloudStack’s API so that clients do not have to know which API commands they invoke on CloudStack are standard and which are custom added.