IT infrastructure was the number one priority amongst ICT decision-makers in our survey this year, and it’s clear why. Companies struggle with any number of possible ways to assemble their IT architecture – creating a real jigsaw puzzle!
What is the best choice, and how do you decide which way to go: cloud, on-premise or hybrid? And how solid can a 'cloud-first' strategy be?
In this users-only event, we first heard the ins, outs and realities of cloud. Then we discovered a real-life case about the journey to cloud industrialisation. And we concluded with an interactive discussion about our members’ experiences, concerns, questions, challenges and decisions.
The presentations from the N-sight are available for our members (after login). Takeaways will be published soon.
Hybrid orchestrated cloud architecture: from strategy to realisation
When considering cloud, start by building a carefully thought-out strategy for a solid architecture, Peter Retera, CTO – Benelux & the Nordics at Atos, emphasised at the start of his talk. Cloud, and more specifically a multi-cloud, sets the basis for a true digital transformation (slide 4).
Next, Peter zoomed in on what exactly 'cloud-native architecture' is: one of the key conditions to avoid lock-in and to achieve portability (slide 7). 'Hybrid cloud' can mean different things, he continued: public vs. private or traditional vs. native.
He then showed us the key drivers for a cloud placement & model:
Public cloud is a lot safer than most private clouds, he added.
To conclude, Peter shared the story of transformation at the Olympic games: a journey from a long-time legacy to a multi-cloud (slides 15-17).
Case: Cloud industrialisation for enterprises
Next, we turned to the real-life experience of Melexis with Koen Bosmans, End User Computing and Cloud Expert at this semiconductor manufacturing company. The main motivation to go to cloud was the company’s fast growth, he explained. With cloud, IT can keep up with that growth.
Koen based his talk around seven ‘ground rules’ for cloud.
The first was ‘manage the fear'. Talk to people about cloud, give it the time it needs, and find a common ground. A cross-functional team was responsible for this stage, and discussed their plans from many different angles:
Another of Koen’s rules was 'play with the new tools'. Let your team explore the tools, and provide guidance where needed. This gives people the opportunity to build trust and discover the capabilities.
‘Set up rules and guidelines’ was another rule, including, for instance:
Of course, these guidelines are continuously up for optimisation.
Koen gave us a clear overview of the differences in style between development before cloud at Melexis, and now, where projects are approached as services (slide 18).
To wrap up, Koen shared the existing architecture at Melexis (slides 19-21). This strategy is not perfect, he admitted: it needs continuous improvement. But it is highly useful, he concluded, especially when adding as much automation as possible in the architecture, which simplifies and speeds up the projects.
Share the experiences - Interactive discussion
After the break, we opened the discussion to a dynamic discussion, in which our members exchanged their knowledge and their views, asked each other questions and inspired their peers. Exactly what Beltug is about!
Without proper guidelines, pre-industrialisation projects fail. @Bokky_com shares the @Melexis_Sensors story #DigitalTransformation #ITarchitecture #CloudStrategy #HybridCloud #ArchitectureStrategy #KnowledgeSharing pic.twitter.com/WFeabi2szK— Beltug (@Beltug) November 12, 2019
Access to more information about this topic and/or to download the paper is easy and fast, but exclusively for Beltug members (just login to get access).
Beltug gathers a lot of information. Here you find the advantages of Beltug membership
The Beltug Team
Click here to login