Server-Side Eclipse is the latest effort to use the Eclipse architecture and the OSGi platform to develop modular web applications. This tutorial introduces the technology, concepts and tools needed to develop Eclipse based web applications. A significant portion of the tutorial will be spent on hands-on activities with the aim of bringing attendees up to speed quickly with setting up the workspace, developing and deploying applications as well as looking at debugging and monitoring techniques.
Building Server-Side Eclipse based web applications 2010Gunnar Wagenknecht
Server-Side Eclipse is the latest effort to use the Eclipse architecture and the OSGi platform to develop modular web applications. This tutorial introduces the technology, concepts and tools needed to develop Eclipse based web applications.
Server-Side Eclipse is the latest effort to use the Eclipse architecture and the OSGi platform to develop modular web applications. This tutorial introduces the technology, concepts and tools needed to develop Eclipse based web applications. A significant portion of the tutorial will be spent on hands-on activities with the aim of bringing attendees up to speed quickly with setting up the workspace, developing and deploying applications as well as looking at debugging and monitoring techniques.
Building Server-Side Eclipse based web applications 2010Gunnar Wagenknecht
Server-Side Eclipse is the latest effort to use the Eclipse architecture and the OSGi platform to develop modular web applications. This tutorial introduces the technology, concepts and tools needed to develop Eclipse based web applications.
Extending the Platform with Spring Boot and Cloud FoundryKenny Bastani
When developing cloud native applications that are deployed and operated using a cloud platform, such as Cloud Foundry, there becomes a need to provision middleware services using the platform. The result of building platform services are that developers using the platform are able to take advantage of service offerings as bindings for their application deployments.
SpringOne Platform 2016
Speaker: Kenny Bastani; Developer Advocate, Pivotal.
Cloud Foundry is a powerful structured platform. For many organizations their first experience with Cloud Foundry feels like jumping in a time machine and emerging in a world where the automations are done and--even more surprising--they work! But that’s just the beginning.
Cloud Foundry is a trustworthy, capable foundation you can build upon. It’s power lies in the flexibility provided through a structured, clear framework for extension. That’s what I want to show you in this talk.
There are several supported mechanisms for extending the platform. In this talk we’ll consider each method and which problem areas they address well. We’ll cover everything from user-provided services to first class services managed by BOSH.
You may be extending the platform to provide unique, new services to your users; or to bridge cloud-native applications running on Cloud Foundry with existing data centers and tools. No matter your use case you’ll gain a valuable understanding of the extensibility of the platform itself to truly make it your own.
Cloud Foundry gives platform operators and platform engineers an incredible framework for delivering transformative value to application developers. Learn how in this talk.
Managing the Complexity of Microservices DeploymentsVMware Tanzu
SpringOne Platform 2017
Prithpal Bhogill, Google; Kenny Bastani, Pivotal
"To rapidly deliver microservices to production, organizations are turning to infrastructure automation provided by a cloud-native platform, like Cloud Foundry. With a platform in place, every microservice team will have what they need to create a CI/CD pipeline that safely delivers applications to a production environment. The final ingredient for success is knowing the right patterns for connecting microservices together over HTTP using REST APIs.
In this session, Kenny Bastani from Pivotal and Prithpal Bhogill from Google dive into a reference architecture that demonstrates the patterns and practices for securely connecting microservices together using Apigee Edge integration for Pivotal Cloud Foundry.
This session covers:
Basics for building cloud-native applications as microservices on Pivotal Cloud Foundry using Spring Boot and Spring Cloud Services
Patterns and practices that are enabling small autonomous microservice teams to provision backing services for their applications
How to securely expose microservices over HTTP using Apigee Edge for PCF"
SpringFramework 5에서 선보이는 Reactive와 같은 핵심기능이 2017 2017년 12월 샌프란시스코에서 열린 Spring One Platform행사에서 소개된 내용중 Spring Data, Spring Security, Spring WebFlux프로젝트에 녹아져 있는지 살펴봅니다. 또한 이러한 기능들이 어떻게 여러분의 시스템의 반응성을 높이고 효율적으로 동작하게 하는지 알아봅니다.
Latency analysis for your microservices using Spring Cloud & ZipkinVMware Tanzu
SpringOne Platform 2017
Marcin Grzejszczak, Pivotal; Reshmi Krishna, Pivotal
"Microservices are becoming increasingly popular. When a request spreads across several services, it quickly becomes challenging to analyse latency especially in real time. In this talk we will present an overview of the new features introduced in the latest Spring Cloud Sleuth release trains that helps you with latency analysis. We will cover recent additions and improvements including annotation based span creation and continuation, span adjusting.
We will then describe how to incorporate these features into an existing Spring Boot application so as to enable latency analysis of your microservices architecture.
Additionally we will deploy the application to Pivotal Cloud Foundry and will demonstrate how to do latency analysis out of the box with the help of PCF metrics and Spring Cloud Sleuth. By the end, you should feel empowered to add latency analysis into your microservices architecture."
Tools to Slay the Fire Breathing Monoliths in Your EnterpriseVMware Tanzu
SpringOne Platform 2017
Rohit Kelapure, Pivotal; Joe Szodfridt, Pivotal; Shaun Anderson, Pivotal
Are fire-breathing monoliths lurking throughout your Enterprise? Many of these ancient behemoths can be millions of lines long and can wreak havoc when trying to evolve and transform your business. Unfortunately, your business depends on services they provide, so they can’t just be eliminated without a battle plan. The Pivotal App Transformation practice has continuously refined approaches and techniques to slay your monoliths. In this session, we will discuss how to carve up your legacy dragons into manageable pieces using techniques and patterns such as Event Storming, Strangling, Starving, Slice Analysis and Domain Driven Decomposition. Monolith slaying is not easy, but with the right tools and weapons at your disposal, your journey to the Cloud can be as easy as a stroll through the forest.
Continuous Delivery for Microservice Architectures with Concourse & Cloud Fou...VMware Tanzu
SpringOne Platform 2016
Speaker: Alex Ley; Product Manager, Pivotal
Building a continuous delivery pipeline for your micro-service based architecture can be a real challenge when using more conventional CI systems like Jenkins and GoCD. How do you get a clear picture of the CI workflow and status? What artifact was deployed and when? How is this all configured?
Introducing Concourse (https://concourse.ci), an open source pipeline based CI system that focuses on simplicity, usability and reproducibility. It offers isolated builds, a range of integrations and is built upon a proven technology stack from Cloud Foundry.
This talk will demonstrate creating a continuous delivery pipeline for a Spring microservice-based application that uses Spring Cloud. You will see how the pipeline tests services, integrates and then blue / green deploys to Cloud Foundry.
Expect to rush to your laptop to try out Concourse after this session!
Documenting RESTful APIs with Spring REST Docs VMware Tanzu
SpringOne Platform 2017
Jennifer Strater, Zenjob
"RESTful APIs are eating the world, yet all too often the documentation can cause indigestion for the APIs' developers and their users. Developers have to deal with annotation overload, repetition, and an unpleasant writing environment. Users are then left with documentation that's inaccurate and difficult to use. It doesn't have to be this way.
This talk will introduce Spring REST Docs and its test-driven approach to RESTful API documentation. We'll look at how it combines the power of Asciidoctor and your integration tests to produce documentation that's accurate and easy-to-read, while keeping your code DRY and free from annotation overload. We'll look at features that are new in Spring REST Docs, focusing on support for documenting APIs that have been implemented using Spring Framework 5's WebFlux."
SpringOne Platform 2017
Miranda LeBlanc, Liberty Mutual
For early adopters, CI/CD and DevOps are obvious choices for driving software innovation at lightning speed, but how do you go about motivating the entire IT organization? At Liberty Mutual Insurance, we've been on a DevOps, Agile and CI/CD journey for at least the last 10 years. Come hear about how we've organically grown a culture supporting CI/CD practices and what our current struggles are in transforming 100 year old insurance company to run like a start up.
Who Does What? Mapping Cloud Foundry Activities and Entitlements to IT RolesVMware Tanzu
SpringOne Platform 2016
Speaker: Cornelia Davis; Sr. Director of Technology, Pivotal.
While “cf push” is the center of it all, there are many more things that various individuals can do with the Cloud Foundry platform. They can monitor, scale and upgrade those deployed apps. And also deploy, monitor, scale and upgrade the platform itself. Further, to operationalize the platform in an enterprise there are quotas, security groups, route services, environment variable groups and many other “knobs” that may also be tuned, and there are various roles and permission structures to govern these. In this session Cornelia will take a holistic view of the Cloud Foundry “control plane” and map the key functions to IT roles (perhaps with some redefinition), and she’ll show which entitlements allow which configurations. Ultimately the goal is to understand how Cloud Foundry can be effectively used to optimize the development and operations (Devops) in your organization. Participants will leave with a concrete framework for transforming current IT practices, roles and responsibilities using the Cloud Foundry platform.
SpringOne Platform 2017
Kris De Volder, Pivotal; Martin Lippert, Pivotal
"In this session we will unveil a new generation of Spring tools. These new tools, which are mostly built from scratch, will not only include the next generation of the Spring Tool Suite (for Eclipse) called STS4, but will feature new and lightweight editor-centric alternatives, for editors such as Atom and Visual Studio Code. In each environment the new tools make it easier to develop Spring Boot applications, deploy applications to Cloud Foundry, develop CI pipelines for those apps, and more.
In this session we will show all of these in action using live coding. The session will include writing, running, testing, and debugging Spring boot applications using Spring Tool Suite, Eclipse, Atom, and Visual Studio Code. We will live code a CI pipeline for them, deploy them to Cloud Foundry, and see how running applications feed information back into your coding environment to further help you understand, debug, and develop your Spring Boot applications.
We will also look at the underlying technology that enables us to create tooling just once and make it available easily across a variety of editors and IDEs."
Fast 5 Things You Can Do Now to Get Ready for the CloudVMware Tanzu
SpringOne Platform 2019
Fast 5 Things You Can Do Now to Get Ready for the Cloud
Speaker: Robert Sirchia, Practice Lead, Magenic Technologies
YouTube: https://youtu.be/WLw82cV0Lwk
Cloud Foundry Services on PKS with No Extra Code, "We Bosh So You Don’t Have ...VMware Tanzu
SpringOne Platform 2018
Cloud Foundry Services on PKS with No Extra Code, "We Bosh So You Don’t Have To!" (Kibosh)
Jeenal Shah, Pivotal; Joe Eltgroth, Pivotal
Lattice: A Cloud-Native Platform for Your Spring ApplicationsMatt Stine
As presented at SpringOne2GX 2015 in Washington, DC.
Lattice is a cloud-native application platform that enables you to run your applications in containers like Docker, on your local machine via Vagrant. Lattice includes features like:
Cluster scheduling
HTTP load balancing
Log aggregation
Health management
Lattice does this by packaging a subset of the components found in the Cloud Foundry elastic runtime. The result is an open, single-tenant environment suitable for rapid application development, similar to Kubernetes and Mesos Applications developed using Lattice should migrate unchanged to full Cloud Foundry deployments.
Lattice can be used by Spring developers to spin up powerful micro-cloud environments on their desktops, and can be useful for developing and testing cloud-native application architectures. Lattice already has deep integration with Spring Cloud and Spring XD, and you’ll have the opportunity to see deep dives into both at this year’s SpringOne 2GX. This session will introduce the basics:
Installing Lattice
Lattice’s Architecture
How Lattice Differs from Cloud Foundry
How to Package and Run Your Spring Apps on Lattice
Cloud Configuration Ecosystem at IntuitVMware Tanzu
SpringOne Platform 2017
Marcello de Sales, Intuit
"Configuration management at Intuit has been reshaped over the last 18 months since the adoption of Spring Cloud Config Server. This work represents a breakthrough in configuration management practices that are changing how Intuit implements configuration management since the company’s inception over 20+ years ago. In essence, any application ranging from desktop and service monoliths started their migration to the cloud without breaking their own DNA: configuration was still part of the binary built on Continuous Integration to be deployed in different data centers. As a consequence, we were still facing the same old challenges: what happens when a new configuration change is required for the entire fleet on multiple private data centers and the cloud? The new answer lies in the adoption of the Spring Cloud Config Server as our One Intuit Configuration Service using the SaaS model, which represents a new shift from manual Operational changes to the simple Pull Requests on related Github Enterprise repositories.
Needless to say, ranging from small internal services to the giants of TurboTax and Quickbooks that are used by millions of users worldwide, there are amazing results with the adoption of this Configuration practice and service such as the decreased time to change configuration from hours to minutes without involving Operations team while getting consistent configuration across a fleet of services. On the other hand, the strong adoption rate brought up a set of new challenges for us to support this new approach in the Enterprise: how to properly architect Spring Cloud Config to be deployed as a SaaS application in the Enterprise? how can we guarantee that users are pushing valid configuration properties to their repo? How can we help them debug their properties consistently, but without relying solely on Github Pull Requests? Finally, what if we need to replicate this solution for Mobile clients? Do we need to deploy hundreds of Configuration servers in the Cloud, and consequently, take the bite on cost?
Overall, the solutions to the questions above are comprised of SaaS deployment of the Spring Cloud Config with some enterprise tweaks for security and performance. Then, we have created a Github Pre-receive hook called Spring Cloud Config Validator to validate user’s config repositories and a web application called Spring Cloud Config Inspector that helps users debug their config keys as associated values, secrets, etc. Lastly, our Spring Cloud Config Publisher solution allows users to use their applications to console a subset of their config properties from an Amazon S3 bucket that the publisher will be publishing to at every new valid commit.
Slides of talk given at Spark Conference:
Modularity reduces software complexity. In this session we’ll present an OSGi based technology stack that can be used for building scalable and modular web applications in Java with standards such as JAX-RS, dependency injection and websockets. We’ll also show you how HTML5 and JavaScript based frontends can be developed and deployment alongside the backend supporting its modularity.
Extending the Platform with Spring Boot and Cloud FoundryKenny Bastani
When developing cloud native applications that are deployed and operated using a cloud platform, such as Cloud Foundry, there becomes a need to provision middleware services using the platform. The result of building platform services are that developers using the platform are able to take advantage of service offerings as bindings for their application deployments.
SpringOne Platform 2016
Speaker: Kenny Bastani; Developer Advocate, Pivotal.
Cloud Foundry is a powerful structured platform. For many organizations their first experience with Cloud Foundry feels like jumping in a time machine and emerging in a world where the automations are done and--even more surprising--they work! But that’s just the beginning.
Cloud Foundry is a trustworthy, capable foundation you can build upon. It’s power lies in the flexibility provided through a structured, clear framework for extension. That’s what I want to show you in this talk.
There are several supported mechanisms for extending the platform. In this talk we’ll consider each method and which problem areas they address well. We’ll cover everything from user-provided services to first class services managed by BOSH.
You may be extending the platform to provide unique, new services to your users; or to bridge cloud-native applications running on Cloud Foundry with existing data centers and tools. No matter your use case you’ll gain a valuable understanding of the extensibility of the platform itself to truly make it your own.
Cloud Foundry gives platform operators and platform engineers an incredible framework for delivering transformative value to application developers. Learn how in this talk.
Managing the Complexity of Microservices DeploymentsVMware Tanzu
SpringOne Platform 2017
Prithpal Bhogill, Google; Kenny Bastani, Pivotal
"To rapidly deliver microservices to production, organizations are turning to infrastructure automation provided by a cloud-native platform, like Cloud Foundry. With a platform in place, every microservice team will have what they need to create a CI/CD pipeline that safely delivers applications to a production environment. The final ingredient for success is knowing the right patterns for connecting microservices together over HTTP using REST APIs.
In this session, Kenny Bastani from Pivotal and Prithpal Bhogill from Google dive into a reference architecture that demonstrates the patterns and practices for securely connecting microservices together using Apigee Edge integration for Pivotal Cloud Foundry.
This session covers:
Basics for building cloud-native applications as microservices on Pivotal Cloud Foundry using Spring Boot and Spring Cloud Services
Patterns and practices that are enabling small autonomous microservice teams to provision backing services for their applications
How to securely expose microservices over HTTP using Apigee Edge for PCF"
SpringFramework 5에서 선보이는 Reactive와 같은 핵심기능이 2017 2017년 12월 샌프란시스코에서 열린 Spring One Platform행사에서 소개된 내용중 Spring Data, Spring Security, Spring WebFlux프로젝트에 녹아져 있는지 살펴봅니다. 또한 이러한 기능들이 어떻게 여러분의 시스템의 반응성을 높이고 효율적으로 동작하게 하는지 알아봅니다.
Latency analysis for your microservices using Spring Cloud & ZipkinVMware Tanzu
SpringOne Platform 2017
Marcin Grzejszczak, Pivotal; Reshmi Krishna, Pivotal
"Microservices are becoming increasingly popular. When a request spreads across several services, it quickly becomes challenging to analyse latency especially in real time. In this talk we will present an overview of the new features introduced in the latest Spring Cloud Sleuth release trains that helps you with latency analysis. We will cover recent additions and improvements including annotation based span creation and continuation, span adjusting.
We will then describe how to incorporate these features into an existing Spring Boot application so as to enable latency analysis of your microservices architecture.
Additionally we will deploy the application to Pivotal Cloud Foundry and will demonstrate how to do latency analysis out of the box with the help of PCF metrics and Spring Cloud Sleuth. By the end, you should feel empowered to add latency analysis into your microservices architecture."
Tools to Slay the Fire Breathing Monoliths in Your EnterpriseVMware Tanzu
SpringOne Platform 2017
Rohit Kelapure, Pivotal; Joe Szodfridt, Pivotal; Shaun Anderson, Pivotal
Are fire-breathing monoliths lurking throughout your Enterprise? Many of these ancient behemoths can be millions of lines long and can wreak havoc when trying to evolve and transform your business. Unfortunately, your business depends on services they provide, so they can’t just be eliminated without a battle plan. The Pivotal App Transformation practice has continuously refined approaches and techniques to slay your monoliths. In this session, we will discuss how to carve up your legacy dragons into manageable pieces using techniques and patterns such as Event Storming, Strangling, Starving, Slice Analysis and Domain Driven Decomposition. Monolith slaying is not easy, but with the right tools and weapons at your disposal, your journey to the Cloud can be as easy as a stroll through the forest.
Continuous Delivery for Microservice Architectures with Concourse & Cloud Fou...VMware Tanzu
SpringOne Platform 2016
Speaker: Alex Ley; Product Manager, Pivotal
Building a continuous delivery pipeline for your micro-service based architecture can be a real challenge when using more conventional CI systems like Jenkins and GoCD. How do you get a clear picture of the CI workflow and status? What artifact was deployed and when? How is this all configured?
Introducing Concourse (https://concourse.ci), an open source pipeline based CI system that focuses on simplicity, usability and reproducibility. It offers isolated builds, a range of integrations and is built upon a proven technology stack from Cloud Foundry.
This talk will demonstrate creating a continuous delivery pipeline for a Spring microservice-based application that uses Spring Cloud. You will see how the pipeline tests services, integrates and then blue / green deploys to Cloud Foundry.
Expect to rush to your laptop to try out Concourse after this session!
Documenting RESTful APIs with Spring REST Docs VMware Tanzu
SpringOne Platform 2017
Jennifer Strater, Zenjob
"RESTful APIs are eating the world, yet all too often the documentation can cause indigestion for the APIs' developers and their users. Developers have to deal with annotation overload, repetition, and an unpleasant writing environment. Users are then left with documentation that's inaccurate and difficult to use. It doesn't have to be this way.
This talk will introduce Spring REST Docs and its test-driven approach to RESTful API documentation. We'll look at how it combines the power of Asciidoctor and your integration tests to produce documentation that's accurate and easy-to-read, while keeping your code DRY and free from annotation overload. We'll look at features that are new in Spring REST Docs, focusing on support for documenting APIs that have been implemented using Spring Framework 5's WebFlux."
SpringOne Platform 2017
Miranda LeBlanc, Liberty Mutual
For early adopters, CI/CD and DevOps are obvious choices for driving software innovation at lightning speed, but how do you go about motivating the entire IT organization? At Liberty Mutual Insurance, we've been on a DevOps, Agile and CI/CD journey for at least the last 10 years. Come hear about how we've organically grown a culture supporting CI/CD practices and what our current struggles are in transforming 100 year old insurance company to run like a start up.
Who Does What? Mapping Cloud Foundry Activities and Entitlements to IT RolesVMware Tanzu
SpringOne Platform 2016
Speaker: Cornelia Davis; Sr. Director of Technology, Pivotal.
While “cf push” is the center of it all, there are many more things that various individuals can do with the Cloud Foundry platform. They can monitor, scale and upgrade those deployed apps. And also deploy, monitor, scale and upgrade the platform itself. Further, to operationalize the platform in an enterprise there are quotas, security groups, route services, environment variable groups and many other “knobs” that may also be tuned, and there are various roles and permission structures to govern these. In this session Cornelia will take a holistic view of the Cloud Foundry “control plane” and map the key functions to IT roles (perhaps with some redefinition), and she’ll show which entitlements allow which configurations. Ultimately the goal is to understand how Cloud Foundry can be effectively used to optimize the development and operations (Devops) in your organization. Participants will leave with a concrete framework for transforming current IT practices, roles and responsibilities using the Cloud Foundry platform.
SpringOne Platform 2017
Kris De Volder, Pivotal; Martin Lippert, Pivotal
"In this session we will unveil a new generation of Spring tools. These new tools, which are mostly built from scratch, will not only include the next generation of the Spring Tool Suite (for Eclipse) called STS4, but will feature new and lightweight editor-centric alternatives, for editors such as Atom and Visual Studio Code. In each environment the new tools make it easier to develop Spring Boot applications, deploy applications to Cloud Foundry, develop CI pipelines for those apps, and more.
In this session we will show all of these in action using live coding. The session will include writing, running, testing, and debugging Spring boot applications using Spring Tool Suite, Eclipse, Atom, and Visual Studio Code. We will live code a CI pipeline for them, deploy them to Cloud Foundry, and see how running applications feed information back into your coding environment to further help you understand, debug, and develop your Spring Boot applications.
We will also look at the underlying technology that enables us to create tooling just once and make it available easily across a variety of editors and IDEs."
Fast 5 Things You Can Do Now to Get Ready for the CloudVMware Tanzu
SpringOne Platform 2019
Fast 5 Things You Can Do Now to Get Ready for the Cloud
Speaker: Robert Sirchia, Practice Lead, Magenic Technologies
YouTube: https://youtu.be/WLw82cV0Lwk
Cloud Foundry Services on PKS with No Extra Code, "We Bosh So You Don’t Have ...VMware Tanzu
SpringOne Platform 2018
Cloud Foundry Services on PKS with No Extra Code, "We Bosh So You Don’t Have To!" (Kibosh)
Jeenal Shah, Pivotal; Joe Eltgroth, Pivotal
Lattice: A Cloud-Native Platform for Your Spring ApplicationsMatt Stine
As presented at SpringOne2GX 2015 in Washington, DC.
Lattice is a cloud-native application platform that enables you to run your applications in containers like Docker, on your local machine via Vagrant. Lattice includes features like:
Cluster scheduling
HTTP load balancing
Log aggregation
Health management
Lattice does this by packaging a subset of the components found in the Cloud Foundry elastic runtime. The result is an open, single-tenant environment suitable for rapid application development, similar to Kubernetes and Mesos Applications developed using Lattice should migrate unchanged to full Cloud Foundry deployments.
Lattice can be used by Spring developers to spin up powerful micro-cloud environments on their desktops, and can be useful for developing and testing cloud-native application architectures. Lattice already has deep integration with Spring Cloud and Spring XD, and you’ll have the opportunity to see deep dives into both at this year’s SpringOne 2GX. This session will introduce the basics:
Installing Lattice
Lattice’s Architecture
How Lattice Differs from Cloud Foundry
How to Package and Run Your Spring Apps on Lattice
Cloud Configuration Ecosystem at IntuitVMware Tanzu
SpringOne Platform 2017
Marcello de Sales, Intuit
"Configuration management at Intuit has been reshaped over the last 18 months since the adoption of Spring Cloud Config Server. This work represents a breakthrough in configuration management practices that are changing how Intuit implements configuration management since the company’s inception over 20+ years ago. In essence, any application ranging from desktop and service monoliths started their migration to the cloud without breaking their own DNA: configuration was still part of the binary built on Continuous Integration to be deployed in different data centers. As a consequence, we were still facing the same old challenges: what happens when a new configuration change is required for the entire fleet on multiple private data centers and the cloud? The new answer lies in the adoption of the Spring Cloud Config Server as our One Intuit Configuration Service using the SaaS model, which represents a new shift from manual Operational changes to the simple Pull Requests on related Github Enterprise repositories.
Needless to say, ranging from small internal services to the giants of TurboTax and Quickbooks that are used by millions of users worldwide, there are amazing results with the adoption of this Configuration practice and service such as the decreased time to change configuration from hours to minutes without involving Operations team while getting consistent configuration across a fleet of services. On the other hand, the strong adoption rate brought up a set of new challenges for us to support this new approach in the Enterprise: how to properly architect Spring Cloud Config to be deployed as a SaaS application in the Enterprise? how can we guarantee that users are pushing valid configuration properties to their repo? How can we help them debug their properties consistently, but without relying solely on Github Pull Requests? Finally, what if we need to replicate this solution for Mobile clients? Do we need to deploy hundreds of Configuration servers in the Cloud, and consequently, take the bite on cost?
Overall, the solutions to the questions above are comprised of SaaS deployment of the Spring Cloud Config with some enterprise tweaks for security and performance. Then, we have created a Github Pre-receive hook called Spring Cloud Config Validator to validate user’s config repositories and a web application called Spring Cloud Config Inspector that helps users debug their config keys as associated values, secrets, etc. Lastly, our Spring Cloud Config Publisher solution allows users to use their applications to console a subset of their config properties from an Amazon S3 bucket that the publisher will be publishing to at every new valid commit.
Slides of talk given at Spark Conference:
Modularity reduces software complexity. In this session we’ll present an OSGi based technology stack that can be used for building scalable and modular web applications in Java with standards such as JAX-RS, dependency injection and websockets. We’ll also show you how HTML5 and JavaScript based frontends can be developed and deployment alongside the backend supporting its modularity.
Introduction to the Eclipse Bundle Recipe project and how to generate OSGi bundles for any library in Maven Central or in a Maven repository behind corporate walls.
Slides of a tutorial given at EclipseCon 2012. The slides are just introductory. The code is available at https://github.com/eclipseguru/eclipsert-tutorial.
Senior Project and Engineering Leader Jim Smith.pdfJim Smith
I am a Project and Engineering Leader with extensive experience as a Business Operations Leader, Technical Project Manager, Engineering Manager and Operations Experience for Domestic and International companies such as Electrolux, Carrier, and Deutz. I have developed new products using Stage Gate development/MS Project/JIRA, for the pro-duction of Medical Equipment, Large Commercial Refrigeration Systems, Appliances, HVAC, and Diesel engines.
My experience includes:
Managed customized engineered refrigeration system projects with high voltage power panels from quote to ship, coordinating actions between electrical engineering, mechanical design and application engineering, purchasing, production, test, quality assurance and field installation. Managed projects $25k to $1M per project; 4-8 per month. (Hussmann refrigeration)
Successfully developed the $15-20M yearly corporate capital strategy for manufacturing, with the Executive Team and key stakeholders. Created project scope and specifications, business case, ROI, managed project plans with key personnel for nine consumer product manufacturing and distribution sites; to support the company’s strategic sales plan.
Over 15 years of experience managing and developing cost improvement projects with key Stakeholders, site Manufacturing Engineers, Mechanical Engineers, Maintenance, and facility support personnel to optimize pro-duction operations, safety, EHS, and new product development. (BioLab, Deutz, Caire)
Experience working as a Technical Manager developing new products with chemical engineers and packaging engineers to enhance and reduce the cost of retail products. I have led the activities of multiple engineering groups with diverse backgrounds.
Great experience managing the product development of products which utilize complex electrical controls, high voltage power panels, product testing, and commissioning.
Created project scope, business case, ROI for multiple capital projects to support electrotechnical assembly and CPG goods. Identified project cost, risk, success criteria, and performed equipment qualifications. (Carrier, Electrolux, Biolab, Price, Hussmann)
Created detailed projects plans using MS Project, Gant charts in excel, and updated new product development in Jira for stakeholders and project team members including critical path.
Great knowledge of ISO9001, NFPA, OSHA regulations.
User level knowledge of MRP/SAP, MS Project, Powerpoint, Visio, Mastercontrol, JIRA, Power BI and Tableau.
I appreciate your consideration, and look forward to discussing this role with you, and how I can lead your company’s growth and profitability. I can be contacted via LinkedIn via phone or E Mail.
Jim Smith
678-993-7195
jimsmith30024@gmail.com
Artificial intelligence (AI) offers new opportunities to radically reinvent the way we do business. This study explores how CEOs and top decision makers around the world are responding to the transformative potential of AI.
The case study discusses the potential of drone delivery and the challenges that need to be addressed before it becomes widespread.
Key takeaways:
Drone delivery is in its early stages: Amazon's trial in the UK demonstrates the potential for faster deliveries, but it's still limited by regulations and technology.
Regulations are a major hurdle: Safety concerns around drone collisions with airplanes and people have led to restrictions on flight height and location.
Other challenges exist: Who will use drone delivery the most? Is it cost-effective compared to traditional delivery trucks?
Discussion questions:
Managerial challenges: Integrating drones requires planning for new infrastructure, training staff, and navigating regulations. There are also marketing and recruitment considerations specific to this technology.
External forces vary by country: Regulations, consumer acceptance, and infrastructure all differ between countries.
Demographics matter: Younger generations might be more receptive to drone delivery, while older populations might have concerns.
Stakeholders for Amazon: Customers, regulators, aviation authorities, and competitors are all stakeholders. Regulators likely hold the greatest influence as they determine the feasibility of drone delivery.
Specific ServPoints should be tailored for restaurants in all food service segments. Your ServPoints should be the centerpiece of brand delivery training (guest service) and align with your brand position and marketing initiatives, especially in high-labor-cost conditions.
408-784-7371
Foodservice Consulting + Design
The Team Member and Guest Experience - Lead and Take Care of your restaurant team. They are the people closest to and delivering Hospitality to your paying Guests!
Make the call, and we can assist you.
408-784-7371
Foodservice Consulting + Design
W.H.Bender Quote 65 - The Team Member and Guest Experience
Running a Succesful Open Source Project
1. Copyright ⓒ 2016, 2017 The Eclipse Foundation and Salesforce.
Made available under the CC-BY-3.0
Running a Successful
Open Source Project
Wayne Beaton,
Gunnar Wagenknecht
2. Copyright ⓒ 2016, 2017 The Eclipse Foundation and Salesforce.
Made available under the CC-BY-3.0
Who we are and why we are here!
Wayne Beaton
@waynebeaton
Director of Open Source Projects
Eclipse Foundation
Gunnar Wagenknecht
@guw
Principal Member Technical Staff,
Salesforce
3. Copyright ⓒ 2016, 2017 The Eclipse Foundation and Salesforce.
Made available under the CC-BY-3.0
Define “Successful”
4. Copyright ⓒ 2016, 2017 The Eclipse Foundation and Salesforce.
Made available under the CC-BY-3.0
Understand Open Source
(at least a little)
5. Copyright ⓒ 2016, 2017 The Eclipse Foundation and Salesforce.
Made available under the CC-BY-3.0
A Typical OSS
Project
Is there such a thing?
Transparency
Openness
Meritocracy
Vendor Neutrality
Code and Documentation
Rules
...
6. Copyright ⓒ 2016, 2017 The Eclipse Foundation and Salesforce.
Made available under the CC-BY-3.0
People!
Community Roles
Owners
Leaders
Developers/Committers
Contributors
Community Members
… and more
7. Copyright ⓒ 2016, 2017 The Eclipse Foundation and Salesforce.
Made available under the CC-BY-3.0
Outreach
Brand
Culture
(Moral) Support
…
The values of
communities
Or why do we have them?
8. Copyright ⓒ 2016, 2017 The Eclipse Foundation and Salesforce.
Made available under the CC-BY-3.0
Open Source
Foundations
Why move your project to a
Foundation?
Vendor neutrality
Governance model
Resources and Services
Marketing
...
9. Copyright ⓒ 2016, 2017 The Eclipse Foundation and Salesforce.
Made available under the CC-BY-3.0
Build Your Community
10. Copyright ⓒ 2016, 2017 The Eclipse Foundation and Salesforce.
Made available under the CC-BY-3.0 Image, CC BY 2.0
https://www.flickr.com/photos/jakerust/16811692146/
11. Copyright ⓒ 2016, 2017 The Eclipse Foundation and Salesforce.
Made available under the CC-BY-3.0
Facilitate Success
● Establish participation rules
● Operate transparently
● Be open to new ideas
● Make building easy
● Make reporting issues easy; respond
● Lower barriers
Stop asking “where’s the patch”
with a snarky tone.
12. Copyright ⓒ 2016, 2017 The Eclipse Foundation and Salesforce.
Made available under the CC-BY-3.0
Listen
Image, CC BY-SA 2.0
https://www.flickr.com/photos/alanstanton/14712867237/
Don’t use Twitter to
report bugs. Just Don’t.
13. Copyright ⓒ 2016, 2017 The Eclipse Foundation and Salesforce.
Made available under the CC-BY-3.0
Conferences
Image, CC BY-SA 2.0
https://www.flickr.com/photos/33725200@N00/7018540027/
14. Copyright ⓒ 2016, 2017 The Eclipse Foundation and Salesforce.
Made available under the CC-BY-3.0Participate in discussions Image, CC BY-SA 2.0
https://www.flickr.com/photos/33725200@N00/416219171/
15. Copyright ⓒ 2016, 2017 The Eclipse Foundation and Salesforce.
Made available under the CC-BY-3.0
Contribute Code
16. Copyright ⓒ 2016, 2017 The Eclipse Foundation and Salesforce.
Made available under the CC-BY-3.0
Code
… is about more than code
Bug fixes, new functionality
Coding conventions
License
Intellectual property, copyright
3rd party libraries
...
17. Copyright ⓒ 2016, 2017 The Eclipse Foundation and Salesforce.
Made available under the CC-BY-3.0
Select your license…
… carefully.
18. Copyright ⓒ 2016, 2017 The Eclipse Foundation and Salesforce.
Made available under the CC-BY-3.0
Manage Copyright
● Who owns the code?
○ The owner may be the author’s employer (check your contract)
○ Do you assign ownership when you contribute?
● The project itself is likely not a legal entity
● State the license (use SPDX code)
/*******************************************************************************
* Copyright (c) 2017 The Eclipse Foundation, and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Eclipse Public License v1.0
* which accompanies this distribution, and is available at
* http://www.eclipse.org/legal/epl-v10.html
*
* SPDX-License-Identifier: EPL-1.0
*
* Contributors:
* Wayne Beaton - initial API and implementation
*******************************************************************************/
19. Copyright ⓒ 2016, 2017 The Eclipse Foundation and Salesforce.
Made available under the CC-BY-3.0
Establish Guides and Conventions
● Put a Contribution guide in your repository
● Coding conventions
● Source code formatting
● Patch size
● Unit tests
● Code comments
● Separate commits/changes (avoid fixing B while working on A)
● Communication & expectations
20. Copyright ⓒ 2016, 2017 The Eclipse Foundation and Salesforce.
Made available under the CC-BY-3.0
Track Intellectual Property
● How is the project code licensed?
● Who owns the code you wrote?
● Are you allowed to contribute?
● Are you allowed to (re-) license the code you are submitting?
● Use a Contributor (License) Agreement (CLA/CA)?
● Define an intellectual property management process
● What about third party content?
21. Copyright ⓒ 2016, 2017 The Eclipse Foundation and Salesforce.
Made available under the CC-BY-3.0
Intellectual Property Due Diligence is Hard Work
● License
○ Are the licenses in the contribution compatible with the project license?
● Provenance
○ Did the people who claim to have authored the code actually author the code?
● Integrity
○ Are the license statements valid?
○ Has the license changed?
○ Has code been inappropriately copied?
22. Copyright ⓒ 2016, 2017 The Eclipse Foundation and Salesforce.
Made available under the CC-BY-3.0
Require a Contributor Agreement/Certificate of
OriginGenerally some combination of:
● The contributor wrote the code
● Contributor has necessary rights to submit the code
● Provided under the terms of the project license
● A public record of the contribution is maintained indefinitely
23. Copyright ⓒ 2016, 2017 The Eclipse Foundation and Salesforce.
Made available under the CC-BY-3.0
Protect Your Trademark
● Who owns the project/product name?
● Should you register a trademark?
● Foundations hold the name on behalf of the community
○ Prevent any single vendor/individual from dominating the project
● Trademark usage guidelines
● Leverage the brand/grow the value of the brand
24. Copyright ⓒ 2016, 2017 The Eclipse Foundation and Salesforce.
Made available under the CC-BY-3.0
What we Didn’t Talk About
● Testing
● Support (end user vs. adopter vs. internal)
● Business drivers for getting involved
● Diversity and longevity
25. Copyright ⓒ 2016, 2017 The Eclipse Foundation and Salesforce.
Made available under the CC-BY-3.0
Why should you care about all of this?
26. Copyright ⓒ 2016, 2017 The Eclipse Foundation and Salesforce.
Made available under the CC-BY-3.0
Thank you!