Software Delivery and the Rube Goldberg Machine: What Is the Problem We Are Trying to Solve?

•

0 likes•71 views

The software delivery life cycle (SDLC) can be complicated. Depending on your architecture and your particular deployment environment, your team may find themselves cobbling together numerous different tools and frameworks, each with its own history and a particular set of challenges it's designed to solve. Sometimes teams find creative ways to use tools outside of their original purpose. It’s a cycle of continuous improvement (secure, deliver, monitor, reflect, make changes, and repeat) with the end goal of easing the process. In this session Melissa McKay, Developer Advocate at JFrog, discusses some of the common problems that teams face during the development and delivery process, and how organizations come together to address them. You will leave empowered and with a call to action to become part of the solution. Speakers: Melissa McKay

Software

▪ DEVELOPER!
▪ SPEAKER
▪ DEVELOPER ADVOCATE
▪ JAVA CHAMPION
▪ DOCKER CAPTAIN
@melissajmckay
linkedin.com/in/melissajmckay
BACKGROUND — MELISSA MCKAY

RUBE GOLDBERG, 1883-1970
Rube Goldberg’s “Self-Operating Napkin,” pen and ink, Collier’s, Sept. 26, 1931

www.rubegoldberg.org/rube-goldberg-contests/

● DevOps Methodology
● Source Control
● Containers
● Microservices
● Continuous Integration
● Package Management
● Securing Your Binaries
● Deployment
TOPICS:

● A lot of moving parts
SOFTWARE DELIVERY PIPELINES
≈
RUBE GOLDBERG MACHINES
● Ineﬃcient
● Tendency to be unreliable/unsafe

Poor evaluation
Lack of
agreement/planning
Missing feature(s)
Glue code maintenance
Loss of project focus
Settling for mediocrity

ARTIFACTORY
DISTRIBUTION XRAY
CI Servers
Remote Repositories
Build Tools/Dependency
Managers
QA/QC
Provisioning Tools
1
2
3
4 5
6
7 8
10
10
Version
Control
System
Take VCS
changes
Commit the
changes
Dev.
Team
Declare new
dependencies
Resolve
dependencies
Resolve
dependencies
Resolve
dependencies
Deploy module Artifacts
and Buildinfo BOM
Contribute
Metadata
Deploy to
Production
Roll out for Internal
Distribution
Production
Servers
Build
MSBuild
DRONE
External Data Sources
Upda
te
ARTIFACTOR
Y EDGE
ARTIFACTOR
Y EDGE
ARTIFACTOR
Y EDGE
Analyze
Build Tools/Dependency
Managers
9
MSBuild

RESOURCES
● https://www.nginx.com/blog/announcing-version-1-0-0-nginx-moder
n-apps-reference-architecture/
● https://landscape.cncf.io/
● https://landscape.cd.foundation/
● https://cd.foundation/community/
● https://jfrog.com/community/

OSGi Community Event 2016 Presentation by Robert Munteanu (Adobe Systems Inc) Microservices are definitely the hot topic du jour . Everyone ( and their dog ) is using microservices or migrating towards them. To make things more interesting, the OSGi community has been talking about microservices for 6 years now, so now we have two clashing definitions of the term. Besides the dreaded monolith and the famed microservices-based architecture there is plenty of room for a middle ground, where an API gateway mediates between a host of microservices and their consumers. Such a gateway solves multiple cross-cutting concerns, such as authentication, API standardisation, logging and decoupling the API evolution. As it turns out, OSGi is an ideal setting for building such an application. The API gateway implementation demoed is based on Apache Sling – an innovative web framework built on top of the Java Content Repository (JCR), that uses OSGi for its component model and fosters RESTful application design. Although we will use Apache Sling for examples, previous knowledge of Sling or its components is not required.

Of microservices and microservices

Robert Munteanu

Microservices are definitely the hot topic du jour . Everyone ( and their dog ) is using microservices or migrating towards them. To make things more interesting, the OSGi community has been talking about microservices for 6 years now, so now we have two clashing definitions of the term. Besides the dreaded monolith and the famed microservices-based architecture there is plenty of room for a middle ground, where an API gateway mediates between a host of microservices and their consumers. Such a gateway solves multiple cross-cutting concerns, such as authentication, API standardisation, logging and decoupling the API evolution. As it turns out, OSGi is an ideal setting for building such an application. The API gateway implementation demoed is based on Apache Sling - an innovative web framework built on top of the Java Content Repository (JCR), that uses OSGi for its component model and fosters RESTful application design. Although we will use Apache Sling for examples, previous knowledge of Sling or its components is not required.

PMBoK and Scrum: can we be friends?

Silvana Wasitova, Scrum & Agile Coach

Rebooting Software Development - OWASP AppSecUSA

Nick Galbreath

If we are ever going to get ahead of the whack-a-mole security vulnerability game, we, as security professionals need to start getting involved more in the development of software. Let's review the origins of the traditional software development, and what assumptions are made. Then we'll review if those assumptions still hold for modern web applications, and what problems they cause, especially for security. Continuous deployment helps address these problems and allows for faster, more secure development. It's more than just "pushing code a lot", when done correctly it can be transformative to the organization. We'll discuss what continuous deployment is, how to get started, and what components are needed to make it successful, and secure.

5 Quick JavaScript Performance Improvement Tips

Troy Miles

JavaScript is arguably the most important language in the world. It comes included in nearly every desktop and mobile browser. It powers the client-side of apps like Facebook and GMail. It is the language of choice for mobile development environments like Apccelerator's Titanium and Apache's Cordova (aka Adobe's PhoneGap). It is even on the server now in Node.js. Yet when programmer's run into performance issue with JavaScript their first inclination is to blame its interpreted nature, not realizing that simple changes in the structure of their code can result in sometimes significant improvements in performance. In this session I will show five quick changes you can make to your JavaScript code to improve its performance and explain why they work.

Why you really want SQL in a Real-Time Enterprise Environment

VoltDB

The SQL/NoSQL/NewSQL discussion isn’t a new one, and it continues to be a confused and confusing debate internally at many companies. In this webinar, VoltDB Director of Product Marketing, Dennis Duckworth, and David Rolfe, Director of Solutions Engineering EMEA, at VoltDB will discuss the importance and portability of using a standard, expressive programming language, and how ACID impacts concurrent actions and makes some things most of you are trying to do much easier. They also cover how SQL operational databases deliver correct answers - and why NoSQL can’t without significant cost (like, in performance). Last they will outline how VoltDB customers dramatically reduced the number of servers needed when they switched from open source DIY NoSQL stacks to VoltDB.

Microservices are definitely the hot topic du jour . Everyone ( and their dog ) is using microservices or migrating towards them. However, the initial enthusiasm for microservices is starting to fade, and for many scenarios monoliths still seem to fit the bill. Even more interesting, in many situations a pure approach of using either microservices or monliths is not enough. Instead a more careful, intermediate approach can be quite powerul. This talk introduces the concepst of an API gateway for microservices as a means to adopt microservices at a more convenient pace. This approach brings about most of the benefits of microservices, but removes large chunks of complexity. We will touch upon authentication, authorization, API standardisation and logging, The API gateway implementation demoed is based on Apache Sling - an innovative web framework built on top of the Java Content Repository (JCR), that uses OSGi for its component model and fosters RESTful application design. Although we will use Apache Sling for examples, previous knowledge of Sling or its components is not required.

Seven deadly wastes

Jez Halford

There are seven things that slow your software team down. Learning to conquer each of them is the key delivering faster. Originating in the Japanese manufacturing industry in the middle of the 20th century, the ideas behind the seven wastes are still hugely relevant to software development today. I explained each one and how it slows you down, then explained how you can defeat the seven wastes and deliver faster than ever before.

Cloud anti-patterns

Mallika Iyer

So we're going no-QA - how do we get the devs to do enough testing?

Steve Wells

Software craftsmanship

Agile in real life

Cloud anti-patterns

microservices.pptx

Responsive, adaptive and responsible - keynote at NebraskaJS

Christian Heilmann

Experience Converting from Ruby to Scala

John Nestor

Apache Sling as a Microservices Gateway

Robert Munteanu

Apache Sling as a Microservices Gateway --- Microservices are definitely the hot topic _du jour_ . Everyone ( and their dog ) is using microservices or migrating towards them. However, there is a gap between the enthusiam for microservices and the ability to create and maintain the infrastructure and culture to effectively use microservices. Apache Sling is an innovative web framework built on top of the Java Content Repository (JCR), that uses OSGi for its component model and fosters RESTful application design. And, as we will see, it is also perfect match for a microservices gateway. In this talk we will review the pros and cons of microservices and monoliths, and look for middle road that smaller organisations that follow to use services productively. One of the approaches we will outline and demo is an API gateway built on top of Apache Sling, used to adress the cross-cutting concerns that would otherwise be reimplemented by all microservices.

RSpec & Rails, an introduction

Utku Kaynar

Goodbye scope anxiety hello agility: Kanban implementation case study at amdocs

Yaki Koren

The main problem we were asked to help solve was scope instability: for years, the organization had been fighting to receive the entire scope upfront and, as time passed, this became less and less possible. Our customers’ (Telecommunication Service Providers) business required better responsiveness and flexibility. In the session we will describe our approach for the implementation: evolution. How we helped the managers to evolve and in parallel evolved our coaching practices. The session will show many examples of successful attempts at evolving and also of failures (which provide great opportunities for learning). The session should be a good kick-starter for lean agile implementation.

Effective entrepreneurship for developersCarlos Ble

Developer WeekDocker, Inc.

Where Do We Go From Here?

Matthew Broberg

Our industry as at a saturation point of buzzwords and it's mucky for those on the job hunt going forward. I'd like to take some time to preach how Open Source's history might be an opportunity to connect into a better future for us all and then map that to technical and career trends happening around us. Sysadmin skills might just be more valuable in the future than we realize. This talk also takes the theme from my favorite talk by John Rauser with his permission.

Experiences testing dev versions of MySQL and why it is good for you

Simon J Mudd

Presentation given at OpenExpo Europe 2018 in Madrid on 6th June 2018 Each new version of MySQL comes out with exciting new features, many of which we’ve been asking for for a long time. The first development or DMR versions are released to the public some time before the software is considered production quality. So who is going to test these new versions which might break at any time and lose all your data? booking.com does just this. The talk explains why we do it, what both we and the MySQL community gets out of it. If you’ve not considered doing such testing it’s very easy so come along and find out how. If you want to find out about some of the fun bugs we’ve seen then you’ll like this presentation too.

【NGINXセミナー】　Ingressを使ってマイクロサービスの運用を楽にする方法

Software Delivery and the Rube Goldberg Machine: What Is the Problem We Are Trying to Solve?

Recommended

Recommended

More Related Content

Similar to Software Delivery and the Rube Goldberg Machine: What Is the Problem We Are Trying to Solve?

Similar to Software Delivery and the Rube Goldberg Machine: What Is the Problem We Are Trying to Solve? (17)

More from NGINX, Inc.

More from NGINX, Inc. (20)

Recently uploaded

Recently uploaded (20)

Software Delivery and the Rube Goldberg Machine: What Is the Problem We Are Trying to Solve?