Once the above questions have been answered, the objectives are clear and when the problem is well defined it is then much easier to choose the correct technology to address the problem. From there you can dive deeper into the specific data requirements and resource needs to use that technology. If you are interested to find out more about mastering your data, we are running an AI and data country email list focused event on 10 March 2022 that includes a roundtable on this topic and more. The key takeaways will be:
Find out more about the event and sign up here or you can find out more about our managed cloud solutions here.
The good old time
To find out more about the OVHcloud Startup Program, or to sign up for free credits and technical suppor . The good old time Many years ago I was a SysAdmin. Do you remember this old job? Let me remind you of a few recurring scenarios: Sure, it was a bit more complicated than a few command lines, but I think you know what I mean. Oh, and does this one sound familiar to many …Let’s say you have a data a win for fair use is a win for libraries problem… Maybe you want to extract some value from your data, for example to give your app an advantage in the market. You look at all the data you have stored, and at the moment it looks like the inside of your house during lockdo
I spent my time deploying and maintaining systems, building resilient architectures, and debugging or fixing failing servers. It was the good old days!
Sounds like a new adventure begins
A few years ago I switched to more customer facing jobs, like product marketing management and technical evangelism, where I used my knowledge to promote products with a good technical approach.
But now guess what? Things has changed. No seriously, when I have to put my fingers on a terminal, a lot of things are different. It’s not that has been replaced by and no one is using screen anymore, but the way of thinking about deployments and resilient architectures is totally different.
Of course I’m not totally out of it, as I used to play around with OpenStack and understand microservices architectures on paper. But it takes a bit more practice to be comfortable speaking with real customers about real applications, deployed with a scalable architecture or in a cloud-native way on Kubernetes.
Leaving pets village
For those unfamiliar with the pets vs cattle analogy, let’s say we’re in a village. Each villager has a handful of animals, not many of them. And each animal requires a lot of time from its owner to feed it, take care of it, play and educate it. They are pets, almost members of the family. And of course, our villagers invest affect and more into each animal. Therefore, losing a pet is really critical as it is unique and cannot be replaced.
Coming back to IT, in the past we deployed applications and servers with the same idea. We spent time on installation, maintenance. One server had very little in common with the others and for critical services we invest so much time in building HA (high availability) architectures with voting solutions united states business directory like quorum devices, fencing tools like STONITH (Shoot The Other Node In The Head) drivers, or dormant resources with active/passive components.
