For many enterprises, publishing API docs is a lot like herding cats. In this talk, we’ll show you how VMware herds cats at scale with a framework that delivers developer portals as-a-service and provides developers ubiquitous access to API docs and other resources on the web and in VMware products.
Dirigible powered by Orion for Cloud Development (EclipseCon EU 2015)Nedelcho Delchev
This BoF is focused on one of the development models "In-System Programming", that can be used in combination with cloud platforms. It leverages also content-centric architectural style by using centralised repository, dynamic languages and multi-container runtime.
The main goal is achieving the shortest development turn-around time ever.
Microservices are the new black. You've heard about them, you've read about them, you may have even implemented a few, but sooner or later you'll run into the age-old conundrum: How do I break my monolith apart? Where do I draw service boundaries?
In this talk you will learn several widely-applicable strategies for decomposing your monolithic application, along with their respective risks and the appropriate mitigation strategies. These techniques are widely used at Wix, took us a long time to develop and have proven consistently effective; hopefully they will help you avoid the same battle scars.
Azure provides cloud services for consumers, students, educators, and researchers. For students, Azure offers limited access to services through DreamSpark. Educators can apply for grants providing broader access for classroom use. Researchers can apply for grants from Microsoft Research depending on their project type and goals.
Decoupled Drupal: What This Means for DevelopersAcquia
Recently, decoupled content management has been taking the front-end world by storm as developers seek new ways to leverage battle-tested back ends alongside more flexible, extensible front ends. JavaScript frameworks with ever-quickening advances and native applications can integrate seamlessly with "headless" back ends such as Drupal by bypassing the theme layer completely.
What are some of the implications of this newly decoupled world for front-end Drupal developers and designers? In this webinar, gain insight into the trends and new ideas emerging on the topic of decoupled Drupal. Also learn about decoupled Drupal against the backdrop of the rapidly changing front-end ecosystem, taking into consideration the impacts in areas such as Web Components, abstract DOMs, Drupal’s theme layer, and presentation.
Designers, front end developers, and Drupal themers of all skill levels will benefit from this webinar. Attendees will learn:
- Advantages and disadvantages of going headless, as well as for going with a JavaScript framework
- Managing content and headless Drupal - what this means for developers
- How to integrate with frameworks and native applications
- The future of markup and the theme layer, as well as the future of the front end and Drupal
Mendix Maker Meetup - London (2019-10-17)Iain Lindsay
Automating the boring stuff
Using the Mendix Platform and Model SDK to automate repetitive tasks. Presented by Alistair Crawford and Iain Lindsay at the Mendix Maker Meetup in London on 17th October 2019
This document discusses starting microservices with .NET. It begins with an introduction to microservices and the benefits of using them, such as improved scalability and resilience. It then covers common microservice patterns and technologies like API gateways, messaging, CQRS/DDD, and containers. Specific .NET tools are presented, including Ocelot for API gateways, RabbitMQ for messaging, MediatR for CQRS/events, and Docker for containers. The document emphasizes building microservices with failure in mind using techniques like retries, circuit breakers, and exponential backoff.
Building Cloud Native Architectures with SpringKenny Bastani
Cloud-native architectures are an emerging practice of software development and delivery. This deck was presented at the Pivotal Cloud Native roadshow and teaches developers how to build modern cloud-native applications using the popular JVM-based application framework: Spring Boot. You'll be provided with a walk through from the monolith application architecture into the more modern microservices architecture. Two open source reference architectures are introduced for building cloud-native microservices. Learn the basics of cloud native platforms and also the approaches for integrating and strangling legacy systems.
https://pivotal.io/event/pivotal-cloud-native-roadshow
Architecting Cloud Computing Solutions with Java [1.1]Otávio Santana
This document discusses cloud-native concepts and architectures using Java. It begins with an introduction to the speaker, Otavio Santana, and his background. It then covers topics like cloud types, cloud native approaches, and how they apply concepts like microservices, containers, and orchestration. It also discusses Java optimizations for cloud environments and projects like Eclipse MicroProfile that help build cloud native Java applications. It concludes with a demonstration of Platform.sh's polyglot platform as a service that aims to simplify developing, deploying and managing cloud applications.
Dirigible powered by Orion for Cloud Development (EclipseCon EU 2015)Nedelcho Delchev
This BoF is focused on one of the development models "In-System Programming", that can be used in combination with cloud platforms. It leverages also content-centric architectural style by using centralised repository, dynamic languages and multi-container runtime.
The main goal is achieving the shortest development turn-around time ever.
Microservices are the new black. You've heard about them, you've read about them, you may have even implemented a few, but sooner or later you'll run into the age-old conundrum: How do I break my monolith apart? Where do I draw service boundaries?
In this talk you will learn several widely-applicable strategies for decomposing your monolithic application, along with their respective risks and the appropriate mitigation strategies. These techniques are widely used at Wix, took us a long time to develop and have proven consistently effective; hopefully they will help you avoid the same battle scars.
Azure provides cloud services for consumers, students, educators, and researchers. For students, Azure offers limited access to services through DreamSpark. Educators can apply for grants providing broader access for classroom use. Researchers can apply for grants from Microsoft Research depending on their project type and goals.
Decoupled Drupal: What This Means for DevelopersAcquia
Recently, decoupled content management has been taking the front-end world by storm as developers seek new ways to leverage battle-tested back ends alongside more flexible, extensible front ends. JavaScript frameworks with ever-quickening advances and native applications can integrate seamlessly with "headless" back ends such as Drupal by bypassing the theme layer completely.
What are some of the implications of this newly decoupled world for front-end Drupal developers and designers? In this webinar, gain insight into the trends and new ideas emerging on the topic of decoupled Drupal. Also learn about decoupled Drupal against the backdrop of the rapidly changing front-end ecosystem, taking into consideration the impacts in areas such as Web Components, abstract DOMs, Drupal’s theme layer, and presentation.
Designers, front end developers, and Drupal themers of all skill levels will benefit from this webinar. Attendees will learn:
- Advantages and disadvantages of going headless, as well as for going with a JavaScript framework
- Managing content and headless Drupal - what this means for developers
- How to integrate with frameworks and native applications
- The future of markup and the theme layer, as well as the future of the front end and Drupal
Mendix Maker Meetup - London (2019-10-17)Iain Lindsay
Automating the boring stuff
Using the Mendix Platform and Model SDK to automate repetitive tasks. Presented by Alistair Crawford and Iain Lindsay at the Mendix Maker Meetup in London on 17th October 2019
This document discusses starting microservices with .NET. It begins with an introduction to microservices and the benefits of using them, such as improved scalability and resilience. It then covers common microservice patterns and technologies like API gateways, messaging, CQRS/DDD, and containers. Specific .NET tools are presented, including Ocelot for API gateways, RabbitMQ for messaging, MediatR for CQRS/events, and Docker for containers. The document emphasizes building microservices with failure in mind using techniques like retries, circuit breakers, and exponential backoff.
Building Cloud Native Architectures with SpringKenny Bastani
Cloud-native architectures are an emerging practice of software development and delivery. This deck was presented at the Pivotal Cloud Native roadshow and teaches developers how to build modern cloud-native applications using the popular JVM-based application framework: Spring Boot. You'll be provided with a walk through from the monolith application architecture into the more modern microservices architecture. Two open source reference architectures are introduced for building cloud-native microservices. Learn the basics of cloud native platforms and also the approaches for integrating and strangling legacy systems.
https://pivotal.io/event/pivotal-cloud-native-roadshow
Architecting Cloud Computing Solutions with Java [1.1]Otávio Santana
This document discusses cloud-native concepts and architectures using Java. It begins with an introduction to the speaker, Otavio Santana, and his background. It then covers topics like cloud types, cloud native approaches, and how they apply concepts like microservices, containers, and orchestration. It also discusses Java optimizations for cloud environments and projects like Eclipse MicroProfile that help build cloud native Java applications. It concludes with a demonstration of Platform.sh's polyglot platform as a service that aims to simplify developing, deploying and managing cloud applications.
This document discusses opportunities for indie game developers on Windows platforms. It notes that Windows 8 allows for touch-first, full-screen experiences across tablets, hybrids, and all-in-ones. Windows Phone 8 shares a common programming model with Windows 8, allowing for code reuse. Several case studies show high download numbers for games on these platforms. The document promotes resources and programs from Microsoft to help developers, including free developer accounts and tools, Microsoft Ventures accelerators, and the Made in Creative UK campaign to showcase UK developers.
This document discusses strategies for evolving existing applications to take advantage of cloud computing capabilities. It outlines four main strategies - lift and shift, containerization, modernization, and building cloud-native applications. Lift and shift involves minimal changes and moves applications to the cloud as-is. Containerization packages applications and dependencies for portability. Modernization utilizes cloud platform services and refactors some components. Cloud-native applications are built from the ground up to be scalable and efficient in cloud environments using microservices and other modern techniques. The best strategy depends on available resources and business priorities, with an emphasis on gradually evolving applications over time to gain cloud benefits.
This document discusses the journey to cloud computing and cloud native applications. It covers evolving from on-premise servers and monolithic applications to distributed architectures like microservices, containers, and serverless functions. The key steps are assessing applications to determine readiness, prioritizing workloads based on business value, and establishing centers of excellence to help teams migrate applications incrementally through pilots while learning from others' experiences. The goal is to maximize cloud advantages like elastic scaling and continuous delivery while navigating technical challenges along the path to cloud native.
QCObjects is the next generation framework for modern software development. This slide is an overview of what you can do with the framework, describing its main features, its license model and impact.
Mastinder Singh has over 9 years of experience in systems automation and complex integration roles using Linux and Windows. He has expertise in deployment tools like Weblogic, Jboss, Jenkins and scripts. His responsibilities have included implementing monitoring solutions using Nagios and Splunk, migrating projects between application servers, and writing scripts for automated deployment and monitoring. He is skilled in DevOps tools like Atlassian, Jenkins, Bamboo, Chef and Puppet.
Cloud Native is more than a set of tools. It is a full architecture, a philosophical approach for building applications that take full advantage of cloud computing and a organisational change. Going Cloud Native requires an organisation to shift not only its tech stack but also its culture, processes and team setup. In this talk I'll dive into possible operating models for Cloud Native Systems.
CloudWorld: What Does Cloud-Native Mean Anyway?Grace Jansen
Terms cloud-native & microservice architecture have been used interchangeably for years. Microservices have benefits, but also bring challenges, so are they really the go-to solution in all cases? Better understanding & some failed projects led to an evaluation of the suitability of microservices, and resulted in new interest in the various architecture styles in the cloud. We'll look at microservices and monoliths in the context of cloud-native.
Architect your app modernization journey with containers on Microsoft AzureDavide Benvegnù
Modernize your application with containers has never been easier! Discover how Azure helps providing all the services you need.
This slides deck has been created for the Microsoft Azure Developer Camp in HK
SPFx allows developers to build client-side SharePoint solutions using open-source tools and modern web technologies like React, Angular, and Knockout. It provides components like Node.js, npm, Gulp and TypeScript to build and run applications that work with both SharePoint Online and on-premises. SPFx solutions can be developed locally using the SharePoint Workbench and deployed to SharePoint as web parts.
MS Insights Brazil 2015 containers and devopsDamien Caro
Talking about DevOps and containers at MS Insights Sao Paolo 2015.
Talking about containers being or not the solution to implementing DevOps practices ? This talk includes a demonstration that show the integration between Visual Studio Online, Docker Hub and GitHub for continuous integration and automated deployment.
Arquitetando soluções de computação em nuvem com JavaOtávio Santana
O Cloud Native se tornou uma grande palavra de ordem em todo o mundo, um termo que é praticamente usado por todos em todos os momentos. Mas o que isso significa? Quais são as vantagens que ele traz ao seu aplicativo e ao seu dia como desenvolvedor ou arquiteto de software? O que há de novo no mundo Java e quais são as etapas a seguir para um aplicativo em nuvem nativo? Esta apresentação é um guia passo a passo que praticamente o guiará na implementação de serviços de computação em nuvem de maneira eficaz e eficiente.
WaveMaker - Spring Roo - SpringSource Tool Suite - Choosing the right tool fo...martinlippert
This document compares and contrasts three tools for developing Spring applications: WaveMaker, Spring Roo, and SpringSource Tool Suite. WaveMaker is a visual tool for quickly creating standard web apps without coding. It generates a Spring-based backend and uses JavaScript for the frontend. Spring Roo scaffolds Java and Spring code to reduce boilerplate. SpringSource Tool Suite is an Eclipse-based IDE that enhances the Java experience for Spring projects. The document recommends combining WaveMaker for frontend development and Spring Roo/SpringSource Tool Suite for backend development, and making it easy to use both tools together on the same project.
DevOps brings together people, processes and technology, automating software delivery to provide continuous value to your users. With Azure DevOps solutions, deliver software faster and more reliably—no matter how big your IT department or what tools you are using
SpringOne Platform 2016
Speakers: Kevin Hoffman; Advisory Solutions Architect, Pivotal & Chris Umbel; Advisory Architect, Pivotal
With the advent of ASP.NET Core, developers can now build cross-platform microservices in .NET. We can build services on the Mac, Windows, or Linux and deploy anywhere--most importantly to the cloud.
In this session we'll talk about Cloud Native .NET, building .NET microservices, and deploying them to the cloud. We'll build services that participate in a robust ecosystem by consuming OSS servers such as Spring Cloud Configuration Server and Eureka. We'll also show how these .NET microservices can take advantage of circuit breakers and be automatically deployed to the cloud via CI/CD pipelines.
What the Gradle team have shipped since Gradle 3.0, featuring performance features like compile avoidance, user experience features like the Kotlin DSL, and brand new tools like the Java 9 support
The document outlines the twelve-factor app methodology for building software-as-a-service apps. It discusses factors such as using one codebase per app, declaring and isolating dependencies, storing configs in environment variables, treating backing services as attached resources, writing logs to stdout, separating build and run stages, keeping development and production in parity, running processes using a stateless architecture, binding to ports, following the UNIX process model, and designing for robustness and disposability. The goals are to enable automation, a clean contract, deployment scalability with minimal changes, and minimizing divergence across environments.
This document provides information about Devoteam's Google Academy program for students in Serbia from March to June 2022. The summary includes:
1) The Google Academy will provide a 3-month internship for students to prepare for Google Cloud certifications, work on a graduation project, and the top 10 students will be selected for employment with Devoteam G Cloud.
2) Mentors from Devoteam G Cloud teams in the UK, Sweden and Serbia will provide weekly consultations and help guide students' certification preparation and graduation projects.
3) Upon completion, the top 10 students will continue their G Cloud career path with Devoteam through an onboarding process working on a Devoteam G
Microservices, Containers, Docker and a Cloud-Native Architecture in the Midd...Kai Wähner
Microservices are the next step after SOA: Services implement a limited set of functions. Services are developed, deployed and scaled independently. Continuous Integration and Continuous Delivery automate deployments. This way you get shorter time to results and increased flexibility. Containers improve these even more offering a very lightweight and flexible deployment option.
In the middleware world, you use concepts and tools such as an Enterprise Service Bus (ESB), Complex Event Processing (CEP), Business Process Management (BPM) or API Gateways. Many people still think about complex, heavyweight central brokers here. However, Microservices and containers are relevant not just for custom self-developed applications, but they are also a key requirement to make the middleware world more flexible, agile and automated.
This session discusses the requirements, best practices and challenges for creating a good Microservices architecture in the middleware world. A live demo with the open source PaaS framework CloudFoundry shows how technologies and frameworks such as Java, SOAP / REST Web Services, Jenkins and Docker are used to create an agile software development lifecycle to realize “Middleware Microservices”. It also discusses other modern cloud-native alternatives such as Kubernetes, Docker, Mesos, Mesosphere or Amazon ECS / AWS.
Microservices pattern language (microxchg microxchg2016)Chris Richardson
My talk from http://microxchg.io/2016/index.html.
Here is the video - https://www.youtube.com/watch?v=1mcVQhbkA2U
When architecting an enterprise Java application, you need to choose between the traditional monolithic architecture consisting of a single large WAR file, or the more fashionable microservices architecture consisting of many smaller services. But rather than blindly picking the familiar or the fashionable, it’s important to remember what Fred Books said almost 30 years ago: there are no silver bullets in software. Every architectural decision has both benefits and drawbacks. Whether the benefits of one approach outweigh the drawbacks greatly depends upon the context of your particular project. Moreover, even if you adopt the microservices architecture, you must still make numerous other design decisions, each with their own trade-offs.
A software pattern is an ideal way of describing a solution to a problem in a given context along with its tradeoffs. In this presentation, we describe a pattern language for microservices. You will learn about patterns that will help you decide when and how to use microservices vs. a monolithic architecture. We will also describe patterns that solve various problems in a microservice architecture including inter-service communication, service registration and service discovery.
Convert your Full Trust Solutions to the SharePoint Framework (SPFx)Brian Culver
This is a live walkthrough where we convert a common full trust solution to a SharePoint Framework solution. May the demo Gods be kind to me. Really, we will do it. Does not cover all possible scenarios, but I will show you the general workflow for converting your full trust solutions to SPFx solutions. I show you the proper configuration for your development environment. We walk through building the SPFx solutions and deploying it to Office 365. Lots of DO’s and DON’Ts will be shared. I’ll show you some of my scars too. From this session forward, you will want to hone your skills in modern SharePoint and convert everything to SPFx solutions.
Attendee Takeaways:
1. Understand the why, the how, and what make up the SharePoint Framework (SPFx).
2. Discussion where we compare common Full Trust Solutions and options for converting to the SharePoint Framework (SPFx) in less than 1 hour.
AWS CodeStar is a service that allows users to easily set up continuous integration and continuous delivery pipelines on AWS. It provides project templates for common configurations, integrates with source control via AWS CodeCommit and issue tracking with JIRA. The pipelines are built using services like CodeBuild, CodeDeploy and CodePipeline. CodeStar also provides a centralized dashboard to monitor builds, deployments and issues. It aims to simplify and accelerate the DevOps process on AWS.
This document discusses opportunities for indie game developers on Windows platforms. It notes that Windows 8 allows for touch-first, full-screen experiences across tablets, hybrids, and all-in-ones. Windows Phone 8 shares a common programming model with Windows 8, allowing for code reuse. Several case studies show high download numbers for games on these platforms. The document promotes resources and programs from Microsoft to help developers, including free developer accounts and tools, Microsoft Ventures accelerators, and the Made in Creative UK campaign to showcase UK developers.
This document discusses strategies for evolving existing applications to take advantage of cloud computing capabilities. It outlines four main strategies - lift and shift, containerization, modernization, and building cloud-native applications. Lift and shift involves minimal changes and moves applications to the cloud as-is. Containerization packages applications and dependencies for portability. Modernization utilizes cloud platform services and refactors some components. Cloud-native applications are built from the ground up to be scalable and efficient in cloud environments using microservices and other modern techniques. The best strategy depends on available resources and business priorities, with an emphasis on gradually evolving applications over time to gain cloud benefits.
This document discusses the journey to cloud computing and cloud native applications. It covers evolving from on-premise servers and monolithic applications to distributed architectures like microservices, containers, and serverless functions. The key steps are assessing applications to determine readiness, prioritizing workloads based on business value, and establishing centers of excellence to help teams migrate applications incrementally through pilots while learning from others' experiences. The goal is to maximize cloud advantages like elastic scaling and continuous delivery while navigating technical challenges along the path to cloud native.
QCObjects is the next generation framework for modern software development. This slide is an overview of what you can do with the framework, describing its main features, its license model and impact.
Mastinder Singh has over 9 years of experience in systems automation and complex integration roles using Linux and Windows. He has expertise in deployment tools like Weblogic, Jboss, Jenkins and scripts. His responsibilities have included implementing monitoring solutions using Nagios and Splunk, migrating projects between application servers, and writing scripts for automated deployment and monitoring. He is skilled in DevOps tools like Atlassian, Jenkins, Bamboo, Chef and Puppet.
Cloud Native is more than a set of tools. It is a full architecture, a philosophical approach for building applications that take full advantage of cloud computing and a organisational change. Going Cloud Native requires an organisation to shift not only its tech stack but also its culture, processes and team setup. In this talk I'll dive into possible operating models for Cloud Native Systems.
CloudWorld: What Does Cloud-Native Mean Anyway?Grace Jansen
Terms cloud-native & microservice architecture have been used interchangeably for years. Microservices have benefits, but also bring challenges, so are they really the go-to solution in all cases? Better understanding & some failed projects led to an evaluation of the suitability of microservices, and resulted in new interest in the various architecture styles in the cloud. We'll look at microservices and monoliths in the context of cloud-native.
Architect your app modernization journey with containers on Microsoft AzureDavide Benvegnù
Modernize your application with containers has never been easier! Discover how Azure helps providing all the services you need.
This slides deck has been created for the Microsoft Azure Developer Camp in HK
SPFx allows developers to build client-side SharePoint solutions using open-source tools and modern web technologies like React, Angular, and Knockout. It provides components like Node.js, npm, Gulp and TypeScript to build and run applications that work with both SharePoint Online and on-premises. SPFx solutions can be developed locally using the SharePoint Workbench and deployed to SharePoint as web parts.
MS Insights Brazil 2015 containers and devopsDamien Caro
Talking about DevOps and containers at MS Insights Sao Paolo 2015.
Talking about containers being or not the solution to implementing DevOps practices ? This talk includes a demonstration that show the integration between Visual Studio Online, Docker Hub and GitHub for continuous integration and automated deployment.
Arquitetando soluções de computação em nuvem com JavaOtávio Santana
O Cloud Native se tornou uma grande palavra de ordem em todo o mundo, um termo que é praticamente usado por todos em todos os momentos. Mas o que isso significa? Quais são as vantagens que ele traz ao seu aplicativo e ao seu dia como desenvolvedor ou arquiteto de software? O que há de novo no mundo Java e quais são as etapas a seguir para um aplicativo em nuvem nativo? Esta apresentação é um guia passo a passo que praticamente o guiará na implementação de serviços de computação em nuvem de maneira eficaz e eficiente.
WaveMaker - Spring Roo - SpringSource Tool Suite - Choosing the right tool fo...martinlippert
This document compares and contrasts three tools for developing Spring applications: WaveMaker, Spring Roo, and SpringSource Tool Suite. WaveMaker is a visual tool for quickly creating standard web apps without coding. It generates a Spring-based backend and uses JavaScript for the frontend. Spring Roo scaffolds Java and Spring code to reduce boilerplate. SpringSource Tool Suite is an Eclipse-based IDE that enhances the Java experience for Spring projects. The document recommends combining WaveMaker for frontend development and Spring Roo/SpringSource Tool Suite for backend development, and making it easy to use both tools together on the same project.
DevOps brings together people, processes and technology, automating software delivery to provide continuous value to your users. With Azure DevOps solutions, deliver software faster and more reliably—no matter how big your IT department or what tools you are using
SpringOne Platform 2016
Speakers: Kevin Hoffman; Advisory Solutions Architect, Pivotal & Chris Umbel; Advisory Architect, Pivotal
With the advent of ASP.NET Core, developers can now build cross-platform microservices in .NET. We can build services on the Mac, Windows, or Linux and deploy anywhere--most importantly to the cloud.
In this session we'll talk about Cloud Native .NET, building .NET microservices, and deploying them to the cloud. We'll build services that participate in a robust ecosystem by consuming OSS servers such as Spring Cloud Configuration Server and Eureka. We'll also show how these .NET microservices can take advantage of circuit breakers and be automatically deployed to the cloud via CI/CD pipelines.
What the Gradle team have shipped since Gradle 3.0, featuring performance features like compile avoidance, user experience features like the Kotlin DSL, and brand new tools like the Java 9 support
The document outlines the twelve-factor app methodology for building software-as-a-service apps. It discusses factors such as using one codebase per app, declaring and isolating dependencies, storing configs in environment variables, treating backing services as attached resources, writing logs to stdout, separating build and run stages, keeping development and production in parity, running processes using a stateless architecture, binding to ports, following the UNIX process model, and designing for robustness and disposability. The goals are to enable automation, a clean contract, deployment scalability with minimal changes, and minimizing divergence across environments.
This document provides information about Devoteam's Google Academy program for students in Serbia from March to June 2022. The summary includes:
1) The Google Academy will provide a 3-month internship for students to prepare for Google Cloud certifications, work on a graduation project, and the top 10 students will be selected for employment with Devoteam G Cloud.
2) Mentors from Devoteam G Cloud teams in the UK, Sweden and Serbia will provide weekly consultations and help guide students' certification preparation and graduation projects.
3) Upon completion, the top 10 students will continue their G Cloud career path with Devoteam through an onboarding process working on a Devoteam G
Microservices, Containers, Docker and a Cloud-Native Architecture in the Midd...Kai Wähner
Microservices are the next step after SOA: Services implement a limited set of functions. Services are developed, deployed and scaled independently. Continuous Integration and Continuous Delivery automate deployments. This way you get shorter time to results and increased flexibility. Containers improve these even more offering a very lightweight and flexible deployment option.
In the middleware world, you use concepts and tools such as an Enterprise Service Bus (ESB), Complex Event Processing (CEP), Business Process Management (BPM) or API Gateways. Many people still think about complex, heavyweight central brokers here. However, Microservices and containers are relevant not just for custom self-developed applications, but they are also a key requirement to make the middleware world more flexible, agile and automated.
This session discusses the requirements, best practices and challenges for creating a good Microservices architecture in the middleware world. A live demo with the open source PaaS framework CloudFoundry shows how technologies and frameworks such as Java, SOAP / REST Web Services, Jenkins and Docker are used to create an agile software development lifecycle to realize “Middleware Microservices”. It also discusses other modern cloud-native alternatives such as Kubernetes, Docker, Mesos, Mesosphere or Amazon ECS / AWS.
Microservices pattern language (microxchg microxchg2016)Chris Richardson
My talk from http://microxchg.io/2016/index.html.
Here is the video - https://www.youtube.com/watch?v=1mcVQhbkA2U
When architecting an enterprise Java application, you need to choose between the traditional monolithic architecture consisting of a single large WAR file, or the more fashionable microservices architecture consisting of many smaller services. But rather than blindly picking the familiar or the fashionable, it’s important to remember what Fred Books said almost 30 years ago: there are no silver bullets in software. Every architectural decision has both benefits and drawbacks. Whether the benefits of one approach outweigh the drawbacks greatly depends upon the context of your particular project. Moreover, even if you adopt the microservices architecture, you must still make numerous other design decisions, each with their own trade-offs.
A software pattern is an ideal way of describing a solution to a problem in a given context along with its tradeoffs. In this presentation, we describe a pattern language for microservices. You will learn about patterns that will help you decide when and how to use microservices vs. a monolithic architecture. We will also describe patterns that solve various problems in a microservice architecture including inter-service communication, service registration and service discovery.
Convert your Full Trust Solutions to the SharePoint Framework (SPFx)Brian Culver
This is a live walkthrough where we convert a common full trust solution to a SharePoint Framework solution. May the demo Gods be kind to me. Really, we will do it. Does not cover all possible scenarios, but I will show you the general workflow for converting your full trust solutions to SPFx solutions. I show you the proper configuration for your development environment. We walk through building the SPFx solutions and deploying it to Office 365. Lots of DO’s and DON’Ts will be shared. I’ll show you some of my scars too. From this session forward, you will want to hone your skills in modern SharePoint and convert everything to SPFx solutions.
Attendee Takeaways:
1. Understand the why, the how, and what make up the SharePoint Framework (SPFx).
2. Discussion where we compare common Full Trust Solutions and options for converting to the SharePoint Framework (SPFx) in less than 1 hour.
AWS CodeStar is a service that allows users to easily set up continuous integration and continuous delivery pipelines on AWS. It provides project templates for common configurations, integrates with source control via AWS CodeCommit and issue tracking with JIRA. The pipelines are built using services like CodeBuild, CodeDeploy and CodePipeline. CodeStar also provides a centralized dashboard to monitor builds, deployments and issues. It aims to simplify and accelerate the DevOps process on AWS.
Docker and containers - For Boston Docker Meetup Workshop in March 2015Jonas Rosland
Docker provides an open platform consisting of Docker Engine, Docker Hub, and an API for building, shipping and running distributed applications across any infrastructure. The Docker Engine is open source software that provides lightweight containers to package applications securely and consistently across any infrastructure from physical to virtual cloud servers. Docker Hub is a cloud-based registry where public, private and curated container images can be stored, shared and deployed. This allows applications to be built once and run anywhere while simplifying deployment, management and scaling of applications across infrastructure.
Docker provides an open platform for building, shipping, and running distributed applications. The Docker Engine and Docker Hub provide the core open source software and cloud services. Docker allows developers to build applications once and run them anywhere by packaging applications into lightweight executable containers that can operate consistently regardless of infrastructure. This enables faster delivery, easier deployment and scaling, and running more workloads.
Docker and Containers overview - Docker WorkshopJonas Rosland
Docker provides an open platform consisting of Docker Engine software and Docker Hub services to build, ship, and run distributed applications across any infrastructure. The platform includes tools to containerize any application and its dependencies into portable packages that can run on any infrastructure from physical and virtual machines to public and private clouds. This allows applications to be quickly and easily deployed and migrated between different computing environments.
WebFest 2011 Hosting Applications CR by David TangSpiffy
David Tang, a Product Marketing Manager at Microsoft Singapore, discussed how customers can expand their services from on-premise to hosted to cloud solutions using Microsoft technologies. He outlined scenarios for publishing a website and editing a live site remotely. The presentation promoted Microsoft's cloud computing landscape including Infrastructure as a Service, Platform as a Service and Software as a Service. It also covered emerging IT roles and skill sets needed for working with cloud technologies.
Brian Williams has over 20 years of experience as a principal software architect leading the design and development of enterprise and cloud computing solutions. He has expertise in areas such as software design, cloud computing, DevOps toolchains, microservices, Docker, AWS, Java, C#, and Agile methodologies. Previously he has held roles as a principal software engineer at companies including VMware, EMC, and Configuresoft, where he led teams and worked on projects involving endpoint management, distributed messaging architectures, and software integration.
Real World SharePoint Framework and Azure ServicesBrian Culver
Building Solution in Office 365 requires leveraging other cloud services, such as Azure Services. For those new to SharePoint and all SharePoint veterans, building cloud ready “Full Trust” solutions for Office 365 introduces a huge paradigm shift over the traditional on-premise full-trust development model.
In this session, we will look at a couple common full trust solutions and move them to Office365 and Azure. We will leverage various Azure services such as Azure Functions, Event Grids and WebJobs. See demonstrations on how event receivers become Azure Function and Event Grids, and timer jobs become Azure WebJobs. Learn about other useful Azure services for replacing full trust functionality. Don’t pass up this opportunity to learn skills and knowledge you need to build Office 365 Solutions leveraging Cloud Services
Attendee Takeaways:
1. Understand how to take Full Trust solutions from On-premise to the Office365.
2. Learn how to use Azure Functions, Event Grids, WebJobs and several other Azure Services.
3. See demonstrations of a couple common Full Trust Solutions converted to cloud solutions on Office365 and Azure.
Convert your Full Trust Solutions to the SharePoint Framework (SPFx) in 1 hourBrian Culver
This is a live walkthrough where we convert a common full trust solution to a SharePoint Framework solution. May the demo Gods be kind to me. Really, we will do it. Does not cover all possible scenarios, but I will show you the general workflow for converting your full trust solutions to SPFx solutions. I show you the proper configuration for your development environment. We walk through building the SPFx solutions and deploying it to Office 365. Lots of DO’s and DON’Ts will be shared. I’ll show you some of my scars too. From this session forward, you will want to hone your skills in modern SharePoint and convert everything to SPFx solutions.
Attendee Takeaways:
1. Understand the why, the how, and what make up the SharePoint Framework (SPFx).
2. A live demonstration where we take a common Full Trust Solutions and covert it to the SharePoint Framework (SPFx) in less than 1 hour.
3. I share lots of tips, DO’s and DON’Ts to save you hours and days of your life. Yes, you are welcome :)
Bahrain ch9 introduction to docker 5th birthday Walid Shaari
A hands-on workshop will go over the foundations of the containers platform, including an overview of the platform system components: images, containers, repositories, clustering, and orchestration. The strategy is to demonstrate through "live demo, and hands-on exercises." The reuse case of containers in building a portable distributed application cluster running a variety of workloads including HPC workload.
Infrastructure as Code in Large Scale OrganizationsXebiaLabs
The adoption of tools for the provisioning and automatic configuration of "Infrastructure as Code" (eg Terraform, Cloudformation or Ansible) reduces cost, time, errors, violations and risks when provisioning and configuring the necessary infrastructure so that our software can run .
However, those who have begun to make intensive use of this technology at the business level agree to identify the emergence of a very critical problem regarding the orchestration and governance needs of supply requests such as security, compliance, scalability, integrity and more.
Learn how The Digital.ai DevOps Platform (formerly XebiaLabs DevOps Platform) responds to all these problems and many more, allowing you to continue working with your favorite tools.
- Docker celebrated its 5th birthday with events worldwide including one in Cluj, Romania. Over 100 user and customer events were held.
- The Docker platform now has over 450 commercial customers, 37 billion container downloads, and 15,000 Docker-related jobs on LinkedIn.
- The event in Cluj included presentations on Docker and hands-on labs to learn Docker, as well as social activities like taking selfies with a birthday banner.
This document discusses Microsoft's web platform and tools. It highlights key capabilities of the Microsoft web platform including the Web Platform Installer, IIS extensions, servers, and technologies. It also discusses tools for developers, designers, and UX designers including SketchFlow for prototyping and Expression Blend for visual design. Silverlight 4 capabilities are summarized in areas of media, rich experiences, business applications, beyond the browser, and developer tools.
There are legacy enterprise Microsoft applications still running on premises, Microsoft SharePoint, Dynamics, Exchange, SQL server or .NET applications. To best realize the benefits of cloud, these applications must be modernized using cloud native approaches to become scalable, secure and fault tolerant. The webinar covers how to refactor and modernize Microsoft applications, explore methods to integrate with AWS managed services for identity federation, databases, monitoring and containers to achieve agility, security and elasticity.
Sriwantha Attanayake, Partner Solution Architect, Amazon Web Services
Application Modernization with PKS / KubernetesPaul Czarkowski
This document discusses strategies for modernizing applications and replatforming them using Project Kubernetes Service (PKS). It outlines how companies have different options for packaging and running workloads, such as using containers, microservices, serverless functions, and monolithic applications. PKS aims to provide the right runtime for each workload type. The document compares container orchestrators, application platforms, and serverless functions, noting that PKS aims to push workloads higher in the platform hierarchy for more flexibility and less enforcement of standards while lowering development complexity and improving operational efficiency. It provides recommendations for getting started with migrating workloads to PKS, such as lifting and shifting applications with minimal modernization, leveraging platform capabilities, and fully modernizing
The document discusses AWS CodeStar, a service that allows users to easily set up continuous delivery pipelines for applications on AWS. It provides templates for common programming languages and services like CodeCommit for source control, CodeBuild for building code, and CodeDeploy or Elastic Beanstalk for deployments. The document demonstrates how to create a project using CodeStar templates and set up a continuous delivery pipeline. It also describes how CodeStar allows for collaboration through user roles and integrated issue tracking with JIRA.
IBM Think 2020 Openshift on IBM Z and LinuxONEFilipe Miranda
IBM Think 2020 - Openshift on IBM Z and LinuxONE
#mainframe #openshift #kubernetes #modernization #ibm #devops #openshift4 #redhatopenshift #redhat #ibmz #linuxone #ibmer
Innovate Faster with Salesforce Heroku and AWS - CMP303 - re:Invent 2017Amazon Web Services
Salesforce and AWS are leading the next revolution in building engaging customer experiences. Behind every great experience is an app, and the power of the Salesforce platform lets you build apps fast. Adding to that experience is the AWS platform that extends the ability to rapidly deliver apps by offering developers a collection of purpose-built and ready-to-consume set of services. Salesforce Heroku—built entirely on AWS—enables developers to focus on building business apps fast instead of spending cycles on the monotonous heavy-lifting. In this session, you learn how Salesforce Heroku and AWS accelerate developer productivity and lower operational complexity to deliver solutions around Salesforce data integration, media delivery, web security, big data analytics and warehousing.
Session sponsored by Salesforce
Getting Started: How to Set Up Your "Data as a Feature" ProjectTIBCO Jaspersoft
This workshop series features a brand-new demo application—created by the TIBCO Jaspersoft team and projekt202—that illustrates and teaches you how to create answer-generating applications of your own. Over the course of 5 webinars, we will introduce you to the what and the why of data as a feature applications and how you can build your own.
Lesson #2 Agenda:
- Project Overview
- Defining the user experience
- Setting up the application environment
- Preparing data
Semelhante a VMware's Journey to Deliver Developer Portals as a Service (20)
By the time they're reading the docs, it's already too latePronovix
Your relationship with a developer begins before they even know your product's name. In fact, before they know they need a product like yours.
In this talk, Matthew will make the case that developer marketing, developer experience, and developer education are part of a continuum. And that if you're thinking of documentation as something that happens only after someone has signed-up for your API, then you're leaving it too late. He'll draw on pedagogical and marketing research to propose a model for the developer learning journey where traditional API documentation is just one stop along the way.
Attend this talk and you'll come away with practical ideas for how to start educating developers earlier in their product evaluation and learning journey.
Optimizing Dev Portals with Analytics and FeedbackPronovix
Making informed decisions on which features to prioritize in a developer portal can be a daunting task. In this session, we'll show you how to leverage experiments, data, and user feedback to evaluate their potential and refine your approach. We'll explore how testing ideas with minimal investment, akin to an MVP, can help you avoid building features that don't meet your users' needs.
Success metrics when launching your first developer portalPronovix
Building our a developer portal may seem easy at the onset with off the shelf options, but when you're building a custom portal to match the needs of your company, it's not as easy. In this session, we'll talk about our process in determining the right places to start with success metrics and features through an early stage feedback back before having customers. You'll see our intention is to tell a story with multiple facets for multiple people, developers, product managers, C suite decision makers etc... Stories around API usage, health, cost, errors and support to provide our users with an overall of their business performance through our APIs.
This document discusses challenges with API integration and proposes augmented approaches using AI. It notes that API integration takes a long time on average of 700 days due to difficulties understanding documentation, requirements, and ecosystems. Common obstacles include domain modeling, use cases, documentation quality, and access issues. The document advocates improving documentation to explain business and product aspects beyond technical references. It envisions next-gen integration using AI like NLP to help analyze APIs and generate integration code on demand. This could enhance documentation with interactive capabilities and help applications autonomously discover and connect APIs.
Making sense of analytics for documentation pagesPronovix
As content producers, we invest considerable time and effort in developing, packaging, and delivering content that we think our users need. After publishing the content, we hope that users find our content useful. And we often wonder how users really navigate and consume our content. Web page analytics can help us gauge the information needs of our customers, assess their content consumption behavior, and find opportunities to improve our content and how we deliver it.
Kumar explores the basics of web analytics, pitfalls of relying too much on web analytics for important decisions, the typical web analytics process, and he will share some guidelines for interpreting web analytics numbers.
Feedback cycles and their role in improving overall developer experiencesPronovix
Drawing from experiences from open source work and her time at Spotify, Serah’s talk cover the challenges, opportunities and hacks around proactive and reactive monitoring, processing, tracking and acting on stakeholder and community feedback, and argue for the centricity of well-defined feedback loops in improving the overall developer experiences for any product and features you are responsible for.
GraphQL Isn't An Excuse To Stop Writing DocsPronovix
The main goal of API documentation is to help developers understand how to use an API. With GraphQL, developers often assume it's self-documenting capabilities are sufficient for anyone that consumes their GraphQL API. But did you ever validate this?
Good API documentation offers both static and interactive ways to learn how to consume the API. API's that support GraphQL often only come with interactive documentation, in the shape of a GraphiQL Playground. However, the first time you (or your users) use a GraphQL API can be very frustrating as GraphQL APIs typically only have an interactive playground. it increases the complexity for newcomers to GraphQL as it assumes you’re already familiar with GraphQL. But with GraphQL, you’re not limited to just an interactive playground, as you can create static or interactive documentation next to having this playground. This talk explores which forms of documentation you can use and how they add value to your GraphQL API.
This document provides guidance for writing documentation about Web3 technologies. It begins with an introduction to the author and their background in technical writing. The document then discusses what Web3 is and how it differs from Web2. It emphasizes that Web3 documentation should use familiar formats from Web2, include detailed examples and code snippets, and use clear language to explain challenging new concepts. Constant research is important given the rapidly evolving nature of Web3 projects. The goal of documentation is to accelerate understanding and adoption of new decentralized technologies.
Why your API doesn’t solve my problem: A use case-driven API designPronovix
API docs frequently fail to address developers’ needs by omitting common usage scenarios and use cases. Let’s take a look at good and bad practices for documenting API use cases, and take steps to ensure that developers get from our API and docs what they really want.
You wrote an API specification, documented your endpoints, and published SDKs. Here’s a question, though: Does your API actually solve your users’ problems?
API providers often fail to address common use cases to solve users’ needs, or their assumptions don’t match the reality. This may end up in frustration and loss of users.
In this talk, we will take a peek into developers’ mindset. I will show how to better understand the developers’ needs by researching the usage patterns, existing libraries and 3rd party experience layers, provide examples of good and bad practices, and suggest actionable steps to improve developer experience for your API.
At times, you have to build docs that cover not only REST-y APIs but also frontend SDKs. What do you do, when you have to offer docs for multiple such SDKs, based on different frameworks, under rapid, uncoordinated development with multiple feature enhancements per iteration and at times, with breaking changes, but versioned and searchable?
Developing a best-in-class deprecation policy for your APIsPronovix
Nobody likes ambiguity—especially when it comes to the stability of APIs and the expectations for availability long term. Avoid common pitfalls and explore a critical area where trust is built with developers through thoughtful policy and the development of best-in-class documentation.
A good deprecation policy involves a lot of forward thinking and an awareness of how developers or end users are currently leveraging your capabilities, and how a given API or feature deprecation could affect them in the future. The hard-earned trust that you’ve built and maintained with these individuals is at risk with any type of policy or documentation that is unclear.
The road to developing a clear, trustworthy deprecation policy is a multi-faceted initiative with input from product, engineering, customer success and other cross-functional teams, as well as external market awareness.
Knowing which voices to have in the room, what the industry standards are, and formulating appropriate communication timelines will ensure a world class policy is developed and documented before it’s needed.
Join us as we dive into the nuances of this process and how to avoid the common pitfalls that come from lacking a strategic, thoughtful approach to documenting a deprecation policy for your APIs.
At MongoDB, we now generate REST API references for MongoDB Atlas from annotations in the product’s source. Our team’s writers proposed, planned, led, and implemented this project–and learned a lot along the way. We’ll share how we got buy-in from engineering and product stakeholders, coordinated the project across teams, implemented swagger-core annotations in Java, and drove positive change to benefit our team, the company, and our users.
What do developers do when it comes to understanding and using APIs?Pronovix
- The document discusses different approaches that developers take to learning APIs: the systematic approach, where developers want to be in control and fully understand what they are doing; the opportunistic approach, where developers quickly experiment and reuse examples; and the pragmatic approach, which combines elements of the first two.
- It also discusses the concept of "flow" in software development and lists some triggers for getting into a state of flow such as clear goals, immediate feedback, and a rich environment.
- The document concludes by asking questions about how to maximize the chance that developers experience flow when using documentation.
Inclusive, Accessible Tech: Bias-Free Language in Code and ConfigurationsPronovix
It's time to take the bias out of code, UI, docs, configurations, or our everyday language by ensuring we choose our words carefully to avoid harmful subtext or exclusion. We can do our part and take steps by examining assets from code to config files to API specifications to standards.
Heard of suss? You can suss out more information or you can find someone's information to be suss. "Suss" shows the flexibility of language. It’s an ongoing process to change how we use certain words. It's important to choose words carefully to convey the correct meaning and avoid harmful subtext or exclusion. Let's explore some of the tools and triage methods that it takes from an engineering viewpoint to make bias-free choices. How can you ensure that biased words do not sneak into code, UI, docs, configurations, or our everyday language?
First, let's walk through how to take an inventory of assets from code to config files to API specifications to standards. Next, by placing those findings into categories, prioritize the work to substitute with inclusive alternatives. Let's examine some examples using both API and code assets. Next is a demonstration of how to automate analyzing your source code or documentation with a linter, looking for patterns based on rules that are fed into the tool.
What's in the future for these efforts? Inclusive language should expand beyond English and North America efforts. To do so, let's organize the work with automation tooling, as engineers do.
Creating API documentation for international communitiesPronovix
How to create documentation and write code for an international audience, not just the people who speak and think like you. Make your APIs more useful for everyone on the planet.
Much of the documentation supplied by both Open Source and Close Souce projects assume the community have a good understanding of the English language and often North American culture as well. This creates barriers for many solution providers, who are the gateway to potentially huge markets for your project.
This talk discusses some of the cultural differences, particularly for people from Asia, in using English language API documentation. It suggests some strategies to help diverse audiences understand you APIs and create solutions using them.
The talk will cover not only differences in language but also other cultural differences that are often not obvious. For example:
Different expectations about publication formats, release processes, levels of support during the development process
Meeting and communications styles
Software development workflows, processes, and tools
Supporting people who are visually impaired will also be briefly discussed.
As well as discussing these issues, specific suggestions will be provided to make API docs accessible for as many people as possible.
This talk is based on Alec's work with customers in Europe, North America, Middle East, Asia, and Australasia. The last five have been spent as a developer evangelist working with PaperCut partners in China, Japan, Korea, US and Europe.
APIs in a modern enterprise are rarely uniform or all of the same type. The multitude of API types can be due to organic growth, mergers and acquisitions, or any number of other reasons. Regardless of their origin, APIs of all types need to be fully documented to facilitate a developer’s journey as they interact with your API ecosystem in order to develop useful applications. In this talk I will show examples of how we have augmented developer portals to document APIs that are not of the REST variety, such as AsyncAPI, GraphQL, SOAP, gRPC, and more, such that all API documentation can seamlessly live side-by-side.
Docs-as-Code: Evolving the API Documentation ExperiencePronovix
We are a software engineering team creating API docs. Docs are authored using Instructional Design principles to narrate use-cases and practical API implementations. This talk shares why & how we've applied software development practices to evolve our document tooling, creation, & delivery methods.
Our APIs describe asynchronous protocols used for embedded software (firmware) components in a digital 2-way radio communications system. The API is protocol data unit (PDU) based and its definition is described in a proprietary format; consequently, well-known API formats, such as Swagger/OpenAPI, or tools, such as doxygen, are not used.
Our product training and technical writing teams are very experienced in Instructional Design methods, but these teams have only written documentation for an end-user audience. Understanding software development processes is equally important as understanding two-way radio networks in order to successfully integrate with the APIs. This is the rationale for having a software engineering team develop the skillsets to write API documentation for a developer audience.
With a solid foundation of API documentation in place, regular examination of engineering efficiency and developer experience is appropriate. Repeated actions can be replaced by automation. Content can be modular and re-usable. Formats can be streamlined for easier consumption. Docs can be made portable and lightweight for faster delivery.
Developer journey - make it easy for devs to love your productPronovix
Ever wonder how some products are just lovable and easy to use while other are not? The good products have optimized onboarding into their ecosystem where you get the information served at the right time.
That’s thanks to developer journey and we will teach you how to get it right!
We will go through the basics such as how to analyze existing and non-existing developer touchpoints, set metrics and optimize them to increase the conversion.
Deliberate Complexity Conferences - 19 JULY 2022
Alicia Juarrero - Complexity is not complicatedness
Professor Alicia Juarrero, a leading complexity theory philosopher and academic, as well as the founder and president of VectorAnalytica, a technology company that specializes in large scale scientific data capture and real time analysis tools. Alicia's work in complexity theory is widely quoted by thought leaders in the technology space and referenced in many recent complexity-informed approaches for managing highly dynamic systems, as well as in knowledge management.
How cognitive biases and ranking can foster an ineffective architecture and d...Pronovix
Deliberate Complexity Conferences - Building Successful Platforms and APIs (29 June). Kenny Baas-Schwegler & Evelyn van Kelle - How cognitive biases and ranking can foster an ineffective architecture and design
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.
Ocean lotus Threat actors project by John Sitima 2024 (1).pptxSitimaJohn
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
UiPath Test Automation using UiPath Test Suite series, part 6DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?Speck&Tech
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
5th LF Energy Power Grid Model Meet-up SlidesDanBrown980551
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Show of hands, how many people know where these photos came from?
These are from the original vinyl press of the White Album … believe it or not, I found these under a bed while I was renovating a college dorm room. I recognized them immediately and snatched them up since their previous owner had departed.
I originally had all four prints, but you’ll notice that George Harrison is conspicuously absent …. His photo went missing a while back, and sometimes my friends and I like to quip about what the Beatles would be without him. I mean, technically John played guitar, so theoretically they could have have made it as a three-man band... But imagine what it would be like, sound like, without George. It would be a lot harder and the results probably wouldn’t be as good. Or better yet, imagine you’re a trio and someone said to you hey, what if you had a fourth Beatle? What could you do, or play, or accomplish that you wouldn’t even try otherwise?
Hi, I’m Richard Thomchick, the product manager for VMware {code}, and several months ago, at the outset of this project, I asked myself these same questions as I pondered what my team could do with an extra developer … not just any engineer… I’m talking about a rock star 10x developer …
2. in our case, his name is Max … he’s like the fourth Beatle on our engineering team, and the journey I’m going to describe today has a lot to do with enabling developers like Max – employees and ecosystem alike– to be more productive and spend more time doing what they do best: innovating.
In the 15 or so minutes we have together, I’ll briefly discuss the evolution of VMware APIs and why we needed to build Dev Center solution and major components such as API Explorer and Sample Exchange.
I’ll also walk you through the dev center experience on VMware Cloud, and give you a glimpse of where we are going next....
In the beginning, there was vSphere, and we had a SOAP API and a command-line interface ...
VMware grew a lot over the next few years, with new platforms and new ways for developers to extend and integrate, but vSphere was still the star of the show …
But then came along SaaS, public cloud, containers, and on and on and on … and so we shifted our focus the public cloud…
Today we are pursuing a hybrid cloud strategy and releasing co-developed solutions like Pivotal Container Service, VMware Kubernetes Engine, and VMware Cloud on AWS …
For developers, integrating VMware technology can be quite daunting …. What you see here is for a “basic” software-defined data center, but it looks a bit more like a flying spaghetti monster, doesn’t it? And many real-world integration projects are far more complex. ......Managing all the content that enables developers to do this integration work is no easy feat, either. In fact, this was one of the biggest challenges facing us at the outset of this project – how to manage the accelerating growth and complexity of our company and developer ecosystem.
For context, VMware {code} has seen tremendous growth since our initial launch in 2017 in terms of web traffic and memberships, and also in terms of the amount of content and the number of contributors we support.
This growth does have a cost. Content requests comprise a significant and growing percentage of our total help ticket volume, and GTIX engineering has seen content-related overhead climb steadily to the point where it takes nearly a full FTE of engineering time just to handle content requests. In fact, we now employ an offshore team of engineers in China just to focus on content.
This is a slide my boss likes me to show ... When we started projecting the expected rate of growth, based on the number of acquisitions and new products in the pipeline, and mapped it against our funding model and projected bandwidth, we realized we were quickly reaching a break point after which we would not be able to sustain operations … I naively thought this slide would get us more funding … but instead it spurred us to innovate, automate, and streamline our operations.
Our solution for managing this complexity at scale is called the Dev Center Framework…. In a nutshell, the Dev Center framework routes content through common API services and presents it to the user via a standardized look and feel …. Here is the basic content flow ….
Contributors – tech writers, engineers, product managers, etc. – add and update content via the DxPress self-service portal or directly from their build chains ….
The Dev Center framework automatically assembles that content into a developer portal via a set of API services, and makes it accessible to users on the website and in our products.
There are a lot of moving parts involved, but today I’m going to focus on three components:
API Explorer….
Sample Exchange ….
And our DxPress self-service portal for content management.
But first, let me show you what one of these portals looks like …
Our first go-to-market partner for the Dev Center Framework was VMware Cloud on AWS (which basically lets you run vSphere in the AWS public cloud) …. For this project we, embedded a ”developer center” into the VMC-AWS interface …
The first step in our journey was to create a single source of truth for VMware API documentation, and this really did feel like we were herding cats … every product team seemed to have their own approach to documenting their APIs and while their single-serving solutions worked well at first, many of the teams had built up some technical debt as they grew and converged with other …
For example, take vSphere, our flagship enterprise product … there are at least a dozen different public APIs … SOAP APIs for hardware access, REST APIs for automation, some open-source, some proprietary ….
Another example, vRealize Automation, is more like a litter of cats … they market a single API but in reality there are more than two dozen individual services, each one documented in a separate JSON file …
And then there’s Workspace ONE…other products may be colorful but these guys are the freaking rainbow
Many of these teams were accustomed to working in “startup mode” (silos), so it took a lot of wrangling to chase them down and add their docs to the service….
This an architectural overview of our API Explorer … the solution itself has an API that retrieves doc from multiple source repositories, and presents it to users via either Swagger UI or our own Angular library … the system supports Open API and RAML, as well as older SOAP APIs that were documented with Javadoc …there are even a couple of PDFs that we display as iframes….we also knew that we needed to architect the solution as a service that could consume all kinds of API docs from multiple repositories, and deliver the information not only to the website
what you’re looking at is here is the “product plugin” edition of API Explorer …. It’s essentially an Angular library that leverages an API to retrieve local and remote resources. One of the features I love the most is the live search and deep linking .... When you start typing in a path name, method description, etc., the system will show you the specific methods in each API that match your query, and link you directly to that section of the doc … developers really like this feature and it is something we are about to release on the website in the next sprint or two.
Here’s a look at the next rev of our API Explorer on the website … this is us iterating on our haystack … it’s still in testing but as you can see we are applying the features across the board so you can get that deep linking experience across all our APIs … this is especially useful for developers who may be working with multiple APIs, some of which do the same thing or have the same name …
The next component of the Dev Center framework is Sample Exchange for code samples and automation scripts from VMware and the community ….This project came about because our developer community asked for a better way to share their code samples, which they had previously been doing in forums and Slack…We wanted to enhance, not replace these tools, so we developed Sample Exchange as an API service that integrates with forums, Slack, GitHub, and so forth … With Sample Exchange, contributors can upload their content from a local directory, or link to existing code in any GitHub repository they have access to … the system automatically updates the content when changes are made to the repository so there is no need to continuously update this listing ...Once your sample is in the exchange, you can embed it in a blog article, forum post, or Slack conversation … The system is also integrated with our Jive community platform, so you also get Community points any other developers can bookmark, favorite, or download your samples, and other users can view the reputation and expertise of a sample author….
The next component of the Dev Center framework is Sample Exchange for code samples and automation scripts from VMware and the community ….This project came about because our developer community asked for a better way to share their code samples, which they had previously been doing in forums and Slack…We wanted to enhance, not replace these tools, so we developed Sample Exchange as an API service that integrates with forums, Slack, GitHub, and so forth … With Sample Exchange, contributors can upload their content from a local directory, or link to existing code in any GitHub repository they have access to … the system automatically updates the content when changes are made to the repository so there is no need to continuously update this listing ...Once your sample is in the exchange, you can embed it in a blog article, forum post, or Slack conversation … The system is also integrated with our Jive community platform, so you also get Community points any other developers can bookmark, favorite, or download your samples, and other users can view the reputation and expertise of a sample author….
One of the most important aspects of the Dev Center Framework is one that end-user developers don’t even know about: Streamlined self-service content management for developer resources that’s as easy as publishing a WordPress blog …
Here’s a quick walkthrough of the 5-minute process for publishing a API doc on VMware {code} ….
So, why did we build DxPress and why does it matter?
Prior to DxPress, it took about 2 weeks, 2 help tickets, 3 separate software interfaces, and at least 4 people to publish pretty much anything.
When we analyzed the actual tasks involved, we quickly realized that in addition to adding web pages, attaching assets, and reviewing the content, a LOT of time was being spent on engineering tasks and email queries ....
For example, to add a new SDK to the website with a download and a programming guide, I would need to file a minimum of two help tickets, and wait for the offshore team in China to respond each time … just this part can take almost a week, but it still doesn’t account for the other 6-8 days, even when you factor in ample time to create and review content …
So where was the time-suck coming from? Well, when we dug deeper, we found most users got stuck … a lot … and were filing tickets to get help almost every step of the way …
Which inevitably led to email exchanges with engineers before, during, and after the ticket is resolved …
Then after the problem is resolved, the user STILL has to contribute their own content … assuming the engineer hasn’t volunteered to do it on their behalf … again usually due to some corner case …
And then finally, we observed that this workflow caused users to review their work over and over again, which prolonged the process even further ….
NOW, with DxPress, we've cut this process down by an order of magnitude by making it fast and simple for users to publish their own content ...
Even when you factor in lengthy reviews and email chatter, the typical turnaround time is 1-2 days max....
Last month, we put DxPress to the test last month for a new release of the vSphere platform ...
here are the highlights of what we published .....
And here is the total overhead for our group to support the launch ...
So, what's next for the framework? Well, now that we’ve been able to validate the basic market fit, our next step is to unleashing it on the website.
code.vmware.com leverages Dev Center services to display APIs and sample code, but we are looking to have full integration to the point where the website a fully compliant best practices reference to showcase its capabilities and establish best practices for stakeholders who want to embed developer centers in their products and cloud services ....
What this means for developers is that they will get ubiquitous access to API docs and other resources with a consistent user experience on any device....
So with that in mind, here is a walkthrough of the {code} 2.0 prototype ...
Last but not least, I’d like to share with you some of the learnings, takeaways, and tips from our experiences along this journey … many of you may already be familiar with some of these, so the main point I want to make here is that even in a large enterprise like VMware, operating like a Lean startup can really help you get where you want to go faster:
Validated research: This is a very common practice in startup product management, and the basic premise is to fail forward fast by validating your assumptions upfront to make sure you’re talking to the right people, that you’ve correctly identified their most pressing problems, and that your value proposition actually addresses their problems. Making design prototypes is a great way to do this because you can quickly put ideas in front of people before you commit to coding …
Lean UX design: If you are familiar with user-centered design, you can think of Lean UX as UCD for lean startups ….. Basically how to do it faster … One of the concepts I really like but was ashamed to say out loud is “pain-driven design” which is about figuring out what is causing your users the most pain … this is very useful for brownfield projects where there are existing legacy tools as was the case with VMware, and believe it or not, this turned out to be my secret sauce at work … When I designed DxPress, I spent a lot of time with users but I also wanted to codify the results, so I made a survey but instead of sending it out and crossing my fingers, I actually went through the survey with each user, structured it as an interview and then charted the results in SurveyMonkey … there are some great books on Lean UX, UX Strategy, Running Lean et.
Stay in Constant Contact with stakeholders and users … this is probably the MOST important principle we followed … most of the people I interviewed at the beginning became design partners and eventually advocates for the system because we had invested so much time to make sure the solution worked for them…. Never forget that you are building relationships and not just software!!!
Automate all the things … because nobody has any bandwidth …even though we managed to automate 80% of the process, most of the product teams we talked to were even more stretched than our engineers, and a few of them scoffed at the notion of a 8-10 minute task “you can’t automate a task by giving it to someone else”)… even 3 clicks is 3 clicks too many. This led us to shift focus from pure contribution to curation …
Avoid Dependency hell … this is an issue that comes up a lot with open source software and microservices … in our case, we have a dependency on an Angular library that another VMware team developed as a fully branded alternative to the default Swagger UI look and feel … and to be honest with you I’m starting to regret it … once you commit to using an upstream library, you are now a customer you have to file issues like everyone else … and if that library itself has dependencies, things start to get complicated … its really important to have a firm handshake upfront with other teams in your organization to avoid issues down the road.
And last but not least … avoid over-engineering at all costs … if you look on the {code} website
this can be particularly challenging if you work in an engineering-led environment, but prioritizing features and focusing on MVPs is essential to staying agile, moving quickly, and ensuring high adoption rates ….