Opening Remarks: Choosing Correctly in an adapt-or-die world
Simplicity is dead. At least, that’s what never-ending stream of constantly changing software platforms would lead you to believe.
Should you use function-based cloud computing? Platform-as-a-service? What about containers, or is it container orchestration? And this is all before you even get to the software itself, and the layers upon layers of abstractions and packages that need to be considered before even thinking about writing code that serves the business.
We’re in the middle of development technology paradigm shift, living in an adapt-or-die world. But there are a lot of key decisions to make, and I’ve seen a lot of organizations make the wrong decisions and end up down a pretty grave path.
Ultimately, they end up with mission-critical systems that are too brittle to change, and too broken not to. The clever engineers that design the systems eventually leave, and no one else is willing to fix the mess. What seemed like a nice technological win just ended up leaving the organization struggling to maintain the systems, while competitors run laps with better, easier-to-maintain systems.
In this talk, I’ll show how, by continuing to partner with Inedo, you can not only avoid becoming a casualty of this paradigm shift, but how you can out-innovate and demonstrate to the powers-that-be that your software platform will let them run laps around their competitors.
I’ll also talk about my vision for Inedo’s future, including our product roadmap and how we’ll continue helping organizations address constantly emerging technology.
Sneak peek: it’s all about getting back simplicity and creating real value by building software
Outline/Structure of the Keynote
In this talk, I’ll show how, by continuing to partner with Inedo, you can not only avoid becoming a casualty of this paradigm shift, but how you can out-innovate and demonstrate to the powers-that-be that your software platform will let them run laps around their competitors.
I’ll also talk about my vision for Inedo’s future, including our product roadmap and how we’ll continue helping organizations address constantly emerging technology.
Learning Outcome
In this talk, I’ll show how, by continuing to partner with Inedo, you can not only avoid becoming a casualty of this paradigm shift, but how you can out-innovate and demonstrate to the powers-that-be that your software platform will let them run laps around their competitors.
I’ll also talk about my vision for Inedo’s future, including our product roadmap and how we’ll continue helping organizations address constantly emerging technology.
Target Audience
Everyone
schedule Submitted 2 years ago
People who liked this proposal, also liked:
-
keyboard_arrow_down
Mark Johnson - Provision and Manage Servers w/Otter, DSC, Git, and Chocolatey
45 Mins
Presentation
Intermediate
In this session, we will take a journey through the lifetime of a Chocolatey package across Windows servers in the enterprise. Some of the questions we will answer:
- How can we publish a Chocolatey package and have it automatically deployed across different environments using Otter and PowerShell DSC?
- How can we use Git to promote Chocolatey package configuration changes to different environments?
- How can Otter detect Chocolatey package version drift and automatically remediate it?
- How can we use Otter to take inventory of all installed Chocolatey packages? -
keyboard_arrow_down
Robert Vandehey - Using Proget and SynchroFeed to drive componentization and automation
45 Mins
Presentation
Intermediate
At Alkami, we have been componentizing our monolith application by breaking it down into packages. These packages are nuget packages for .NET libraries and choco packages for microservices and widgets. Proget is our package server which is fed artifacts from our Bamboo server. We then use a product we open sourced called SynchroFeed to validate packages and mirror packages to our external feeds. This presentation will highlight Alkami's CI/CD architecture using Bitbucket -> Bamboo -> Proget -> Whitesource -> SynchroFeed -> Team City for deployment and how it allowed us to handle the explosive growth in microservices.