apidays LIVE Australia - Leveraging DevOps to visualize your digital ecosystem by Mark Crawshaw
•Download as PPTX, PDF•
0 likes•116 views
apidays LIVE Australia - Building Business Ecosystems Leveraging DevOps to visualize your digital ecosystem Mark Crawshaw, Founder of Aplas
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to apidays LIVE Australia - Leveraging DevOps to visualize your digital ecosystem by Mark Crawshaw
Similar to apidays LIVE Australia - Leveraging DevOps to visualize your digital ecosystem by Mark Crawshaw (20)
More from apidays
More from apidays (20)
Recently uploaded
Recently uploaded (20)
apidays LIVE Australia - Leveraging DevOps to visualize your digital ecosystem by Mark Crawshaw
- 1. Leveraging DevOps to visualize your digital ecosystem apidays Australia 2020
- 2. Tech Complex Software Systems
- 3. Tech Complex Software Systems
- 5. “The capability of staff to understand software impacts their ability to improve software”
- 8. Large
- 9. Massive
- 10. Two Problems
- 11. Collection • No shortage of documentation • No shortage of point-in-time audits • Process requires documentation • Information spread across multiple systems
- 12. Collection > Software Indexing • High-level – reference detail rather than record • Workflow agnostic – data only / multi-purpose • Accessible • Interoperable
- 13. Presentation • Excel, SharePoint, CIDB, Architecture Tools, Whiteboard, Visio • Finding information is hard • Some systems complex • Visualization breaks at scale • Visualisation hard to keep up-to-date
- 14. Presentation > Mapping + Publishing • Separate the index from how it is interacted with by publishing different “interfaces” • Software map to provide consistent place • Map styles to tell different stories with the same map • Published interfaces for different audiences • Updates automatic/real-time from index
- 15. Demo
- 17. Tracking the challenges of our customers… Growth of systems Highly integrated Cloud usage Development patterns Tech staff Ways-of-working Communication
Editor's Notes
- Hi, I’m the founder and general manager of Aplas. If you’re wondering, Aplas it an atlas for software. I’m very excited to talk a little about the challenges our customers face in understanding their software environments and how we work with them to deliver a very unique capability. So what is the problem? Why do we want to visualize your digital ecosystem? How can DevOps contribute to this? We’re going to run through all of it here… The solution I’m going to talk about here is software indexing and mapping… A way to improve our ability to find an understand information about complex systems of software… Something that sits at the intersection of lots of code, documentation, whiteboards, Visio diagrams, and your brain. So let’s start with just that…
- So on the left we have us... Software operators, engineers, architects… and the right the complex software networks we build and manage… We spend a lot of time thinking about software, how to code it, how to architect it, how to support it, and what common platforms we need…
- But we spend a lot less time considering how people think about about software… How we find information about our software, how we quickly we can reason about complex networks, and how effectively we can communicate about the challenges we face every day.
- Now, you might say, we already have a system that helps with this… But ask yourself… Who has access to this system? How simple is it? How many tech staff actually use the system day-to-day? And what we find is big divide between people who understand and those that don’t. And in most companies the staff that are not empowered with this information greatly out way those that do.
- All of our customers understand one thing… “The ability for staff to understand software impacts there ability to improve their software” Some companies have hit a breaking point between with the vast numbers of people needed to manage their software, and the vast complexity of that software. There are now so many people My background is running large integration competency centres with many thousands of systems and integrations, all managed by a single team… What if we could give the people involved altering and operating software more a significantly better understanding of their software… It has to do with scale and the the efficiency of people
- Before we discuss how we can help achieve this goal, let’s jump straight in and see what the end result looks like… Aplas is an atlas for software and it allows anyone to understand software at scale.
- So this is a software map, it is a breakthrough visualization technique that allows anyone to understand complex software networks. A software map sits at the intersection and people and software… The islands/continents represent the business structure, while the nodes and lines represent the software architecture. It is also designed to be as rigid as practical, so each time you come back to the map it is familiar. As the data that drives the map changes, the map is able to stay as … (CLICK) This particular map includes 100 systems and 500 integrations. This is on the smaller end for our customers…
- A larger map including 500 systems and 2500 integrations. Just like geographic maps, we are able to zoom out and the map abstract what we are looking at, and zoom in to see much detail in a particular area.
- A massive map… This includes 2000 applications and 10000 integrations. Often useful to groups of companies or governments where the complexity of integrated systems is considerable. It’s no surprise that such organizations struggle to deliver cross-cutting software change.
- Before we dive in and have a look at a software map in more detail, let’s consider the problems we are trying to solve… There are 2 distinct problems we must face to solve to improve software knowledge… Collection - How do we gather information from multiple sources and keep it up-to-date… Presentation - How do we display information so it is useful to different audiences… But it’s not a one-way stream… From collection to presentation… Experience shows that the more people consuming software information, the more likely they are to improve its quality… There is most definitely a feedback loop for software asset metadata. And today, we are releasing some big new functionality that helps make this feedback loop as short as possible…
- What information are we looking for? Initially just the basics for application and integration, including links for more detail. Fortunately we are really good at documenting and auditing these things… Though most organizations struggle to gather this information centrally. The first point to make, is that it’s not for a lack of trying… We already spend a huge amount of time documenting and auditing, just that
- The solution is an index. Just like Google indexes the web, Aplas indexes business software. And index by definition is about references other material, not storing it, is focussed on indexing, not other workflows, accessible, and interoperable.
- Current state makes acquiring and comprehending asset metadata challenging No shortage of systems, Excel… Finding anything is a serious uphill battle. Some systems are too specialised for general use. Visualization is very hard to keep up-to-date, especially at scale.
- The solution is the flexibility to publish many interfaces from our single software index.
- So now, let’s jump into the product, create an index, build a map, publish some interfaces, then hook it all up to GitHub so we can update it all in real-time. Basic setup (*)Create index Open the software index and explain at a high-level how it works (*)Create software map Explain the process of generating a map in the background using physics simulation models (*)Create 2x publications We have a growing number of interfaces… (*)Review 2x publications Metasearch is the Google of software Metamap is the the Google Maps of software Real-time setup One common use-case for Aplas is bringing information in from existing DevOps processes. Many of our customers who have hundreds or thousands of applications use this technique to bring there developers into the software indexing process. (*)Create GitHub connection It is also possible to bring information in from Confluence and we are currently working on a ServiceNow connector. (*)Edit aplas.json, copy application + integration + CHANGE THE CATEGORY TO “ftp” (*)Commit & push to remote (*)Review updates in real time Showing a engineer how they can contribute to the organizations software map from their existing tools with instant feedback is a really powerful way to improve quality.
- Thanks, our vision here at Aplas is to empower as many people to contribute… Whether that is the CEO, to a junior developer who as just started in the organization. If your interested in to learn more, please jump onto our site and reach out or create a trial account. Thanks.
- I used to run large middleware platforms… So I have an interesting perspective on IT… Really sitting on top of all the complexity of our software, while attempting to drive out efficiency in delivery… So let’s talk about some of the challenges our customers face… System count large & growing Huge amount of integrations, many now configured between SaaS applications Cloud increasing growth Maintaining many dev patterns Tech staff increasing Ways-of-working changing Communication challenging So if it was just one of these challenges, we could cope… But most of our customers have many or all of these challenges and they compound against each other… Often significantly slowing the capability for business to adapt and change…