Download to read offline
Uploaded byJared Roberts
Engage 2018 - What About the Apps? A Domino Modernisation Story
The document discusses the modernization of Domino applications. It notes that applications have become separated from email and mobile devices are ubiquitous. Consumer apps have set high expectations for user experience. The key disruptors are mobile usage, cloud platforms, consumer-like UX, and social/cognitive intelligence. The document recommends developing an app modernization strategy through analysis of usage and business needs. Applications can be retired, maintained, modernized by iterative updates, or replatformed to new systems like cloud. Domino 10 will make modernization easier through support for newer frameworks. Starting the process now is important to keep applications relevant.
More Related Content
Similar to Engage 2018 - What About the Apps? A Domino Modernisation Story
![Coded Agents – with UiPath SDK + LangGraph [Virtual Hands-on Workshop]](https://cdn.slidesharecdn.com/ss_thumbnails/codedagentsdeck-251215155422-5497c599-thumbnail.jpg?width=640&height=640&fit=bounds)
Engage 2018 - What About the Apps? A Domino Modernisation Story
- 1. What About TheAPPS? The Domino App Modernisation Story 1#engageug Jared Roberts, ISW @jazzaroberts
- 2. Jared Roberts 2#engageug • SeniorSoftware Engineer/Consultant • Melbourne, Australia • Admin/Consultant/Pre-Sales/Techie – most ICS areas • IBM Champion • Fan of the User • Dad of 2 • Not great at sports • Drummer for Desecrator • Heavy Metal - Melbourne, Australia • The best band you’ve never heard of • We tour a lot (30000km in the last year) • I wrote abstracts for this conference from a tour bus! • Lifelong music nerd (play drums, guitar, bass, sing) • …hence not great at sports
- 3.
- 4. State of theApplication: 2012-2014 • We are at an Application crossroad! • Email is becoming a commodity • Email and Applications are starting to become separated • Smartphones are commonplace and Tablets at work are growing • New Application platforms are being introduced and disrupting the ‘old way’ of developing, testing and delivering Applications • An increasing need for continuous delivery of Application capability is desired 4#engageug Time Warp…
- 5. State of theApplication: 2015-2017 • Email is a commodity • Email and applications are increasingly being separated • New and fast application platforms are getting traction • DevOps methodology and continuous delivery is becoming a 1st choice standard • Smartphones are commonplace, tablets are starting to outpace laptops • Younger workforce wants consumer app experiences at work • The separation between consumer and enterprise is disappearing 5#engageug Time Warp… again
- 6. State of theApplication: Today • Email and Applications are totally separate • User Experience is the focus of App Design • Mobile/Tablets are everywhere and are now 1st choice • Everyone wants consumer app experiences at work • Businesses want cognitive focused intelligent apps that are easy to build, deploy, manage and secure • PaaS - Platform As A Service owns the application whitespace with containerisation allowing seamless movement between on-premises and cloud (Docker) 6#engageug Here and now…
- 7. The Application Disruptors 7#engageug Whathas happened? MOBILE UX SOCIAL & COGNITIVE INTELLIGENCE CLOUD CONSUMER APPS
- 8. Mobile 8#engageug The Application Disruptors MOBILEUX SOCIAL & COGNITIVE INTELLIGENCE CLOUD CONSUMER APPS
- 9.
- 10.
- 11. Cloud 11#engageug The Application Disruptors MOBILEUX SOCIAL & COGNITIVE INTELLIGENCE CLOUD CONSUMER APPS
- 12. Cloud • Cloud hasbecome a huge disruptor and enabler for modern apps • Platform as a Service dramatically removes the up front infrastructure costs that historically were needed to build and deliver apps • DevOps enables the rapid deployment and provisioning of app releases – Agile • Containerisation via Docker – Continuous Deployment, Version Control, Portability, Isolation & Security 12#engageug The Application Disruptors
- 13.
- 14. UX 14#engageug The Application Disruptors MOBILEUX SOCIAL & COGNITIVE INTELLIGENCE CLOUD CONSUMER APPS
- 15. UX • Your usersare used to this at home… 15#engageug The Application Disruptors
- 16. UX • And this… 16#engageug TheApplication Disruptors
- 17. UX • And we(sometimes) ask them to use this at work… 17#engageug The Application Disruptors myCompany
- 18. UX • And this… 18#engageug TheApplication Disruptors
- 19. UX • Do youreally think they will be happy and productive with this…? 19#engageug The Application Disruptors
- 20. UX • or this…? 20#engageug TheApplication Disruptors
- 21. UX • Users wantto work with something like this… 21#engageug The Application Disruptors
- 22. UX • Users wantto work with something like this… 22#engageug The Application Disruptors Visual, Intuitive, Quick, Productive.
- 23. Consumer Apps 23#engageug The ApplicationDisruptors MOBILE UX SOCIAL & COGNITIVE INTELLIGENCE CLOUD CONSUMER APPS
- 24. Consumer Apps • Consumermobile apps have set the bar high for what employees, customers and partners expect • Intuitive • Pervasive • Contextual • Dynamic • Intelligent • Users want these experiences at work • Simplicity and ease of use • Proliferation and variety • Speed and instant gratification 24#engageug The Application Disruptors
- 25.
- 26. Social & CognitiveIntelligence 26#engageug The Application Disruptors MOBILE UX SOCIAL & COGNITIVE INTELLIGENCE CLOUD CONSUMER APPS
- 27. Social & CognitiveIntelligence • Apps within social platforms • Acting on tasks in context • Cognitive computing • IoT • Content AI • Search • Security • Natural language, intent 27#engageug The Application Disruptors
- 28. Social & CognitiveIntelligence 28#engageug The Application Disruptors
- 29.
- 30. Where to start...? •Developing Application Strategy • First, start with your whole business • Do you even have an App strategy? • Analysis! • Data, data, data – is where the answers lie… 30#engageug App Modernisation Strategy
- 31. Where to start…? •Key term: TRANSFORMATION • Define what you’re trying to do: modernise/migrate/update/upgrade • Apply analysis data + business process review • Usage and code review is critical – but what does your app actually do? • Categorise the Apps into: • Retire • Maintain • Modernise • Replatform 31#engageug App Modernisation Strategy
- 32. Analysis • Create and/orupdate your Application portfolio documentation 32#engageug App Modernisation Strategy + ApplicationInsights DataMiner
- 33. Analysis - ApplicationInsights •Easily surface critical data on usage, design complexity • Analyse code to gain insights on design similarity, platform dependencies and cloud/web readiness 33#engageug App Modernisation Strategy
- 34. Analysis - DataMiner •Get answers to specific questions from the ApplicationInsights data • Export to csv, Excel or json to import into other reporting systems to visualise the data your way 34#engageug App Modernisation Strategy
- 35. Business Process Review •What does this application do? • Workflow analysis: end to end review of the data input and output • Does it currently meet the needs of the business? • How much does it cost to maintain? • Can this be replaced with an ‘off-the-shelf’ solution? 35#engageug App Modernisation Strategy
- 36. Outputs of analysis •Application Usage: • Design complexity: • Code analysis: • Answers to specific questions: • Qualified application capabilities vs business needs: • Opportunities to optimise infrastructure • Opportunities to optimise licensing • Save $$$ 36#engageug App Modernisation Strategy
- 37. 37#engageug So…. Again… What now? OK– got the data Answered my questions…
- 38.
- 39. Classifying Applications: RETIRE •Apps that don’t or won’t provide ongoing business value • Used for content retention 39#engageug Retire
- 40. RETIRE how? 40#engageug Retire • Archived(read-only) • Exported to csv/text • Surfaced in browser (read-only) • Deleted *
- 41. Classifying Applications: MAINTAIN •Apps that are still needed • Won’t grow or innovate (too complex or rarely used) 41#engageug Maintain
- 42.
- 43. Classifying Applications: MODERNISE •Apps that need renewed investment and have continued value • Very complex back-end processing – may be too expensive to migrate 43#engageug Modernise
- 44. MODERNISE how? 44#engageug Modernise • Modernisedoesn’t mean migrate • Big-bang approach (all apps in one move) • Too expensive • Too complex • Too disruptive • One App at a time • Too disruptive • Too complex • Takes too long
- 45. MODERNISE how? 45#engageug Modernise • Iterativeapproach • Little to no disruption • Almost always less expensive • Works with a strategy to maintain or migrate underlying components (Infrastructure/database/security) • Use agile methodology • DevOps • Containersiation on Cloud • PaaS – IBM Cloud (BlueMix/SoftLayer), Azure, AWS
- 46. MODERNISE how? 46#engageug Modernise Material Design,Carbon, Fluent devOps database cache application UI
- 47. MODERNISE before 47 Modernise #engageug • Notesdatabases accessed only via Notes client (in this case a suite of 3 separate but inter-dependent applications)
- 48.
- 49. MODERNISE after 49#engageug Modernise • ‘onepane of glass’ for 3 separate apps • Surfaced in context (ie – IBM Connections) • New features/innovations • Back-end processing in Notes as normal (no disruption)
- 50. Classifying Applications: REPLATFORM •Apps that need to be migrated to Cloud • Apps that need to be migrated/surfaced in other platforms 50#engageug Replatform
- 51. REPLATFORM how? 51#engageug Replatform • Iterativeapproach • Same as Modernisation approach • Little to no disruption • Front end capability can be delivered independently of data migration • Data migration optional: can be done later or not at all! • Domino security model: considerations to reproduce in other platforms • Use agile methodology • DevOps • Containersiation on Cloud • PaaS – IBM Cloud (BlueMix/SoftLayer), Azure, AWS
- 52. REPLATFORM how? 52#engageug Replatform #engageug Material Design,Carbon, Fluent devOps database cache application UI
- 53. REPLATFORM before 53#engageug Replatform • Notesdatabases accessed only via Notes client (in this case a suite of 3 separate but inter-dependent applications)
- 54. REPLATFORM after 54#engageug Replatform • Seamlessintegration into O365 • NoSQL database (Domino)
- 55. REPLATFORM before 55#engageug Replatform • Notesdatabases accessed only via web browser
- 56. REPLATFORM after 56#engageug Replatform • Moderninterface based on Google’s Material UI • NoSQL database (mongodb)
- 57. 57#engageug The Domino AppModernisation Story What’s new! • Domino 10 • Support for nodeJS, LoopBack and more modern frameworks • Continuous delivery/improvement/support • Apps that depend on mail/calendar will be easier to modernise
- 58. 58#engageug The Domino AppModernisation Story Summary • Your Domino apps have served you well for years and have critical & historical business value • Users don’t want clunky old Notes databases running in in a heavy client that have huge amounts of mouse clicks and keystrokes to get things done • You need to start making decisions NOW about reinvigorating your Domino Apps • Analysis is the key. Start NOW • Modernising/Replatforming the Apps is the way forward • IBM will make it easier to deliver these outcomes within Domino – starting with v10 • No rush to do any of this….. • But do it NOW • RIGHT NOW!
- 59. 59#engageug The Domino AppModernisation Story Q & A ?
- 60.
Editor's Notes
- #32 Unfortunately – where we are night now – is THAT is the term that I myself mostly need to use when it comes to talking anything Domino.
- #39 Unfortunately – where we are night now – is THAT is the term that I myself mostly need to use when it comes to talking anything Domino.
- #47 DevOps - Jenkins Data – Domino, mongodb Cache – Redis Application – Docker, Kubernetes, NodeJS, Express UI – React, Material Design (Carbon, Fluent)