A key reason for me joining DigIO is the opportunity to influence and shape the direction of a new business. I want to work with great people who take pride in their craft, and want to create a culture of learning and sharing. But there is more than building a great culture. I want DigIO to be a voice in the technology community and take an active role in determining the direction that our organisation and our clients take. We will never pretend to have all the answers, however we want the opportunity to share and discuss our ideas. In this and subsequent postings, I’d like to explore ideas that are meaningful to us.
Here are some of the areas I’d like to explore:
- The evolution of cloud offerings, strengths and points of differentiation between providers, and when it makes sense to leverage the best aspects of each provider vs. “going all in” with a single provider. Focus areas will include infrastructure capabilities, serverless/PaaS, data processing, analytics, machine learning, and IoT.
- How to pursue a “NoOps” strategy in order to spend more time on creating value and less time on plumbing. What constraints do fully managed solutions impose? Where does each sit on the proprietary vs. open scale and how much does that matter? Whether to pick serverless vs. container-based offerings for building applications. How to build data lakes to support an entire organisation. How do these changes affect the mix of skills required to develop and operate solutions?
- With a move to microservice-based architectures built by decentralised and empowered delivery teams, integrating services and sharing datasets becomes more challenging. How do concepts such as service meshes and control planes help? How can data be made more broadly available, both for regular analytics and reporting as well as for development of machine learning models and adhoc exploration?
- How to strike a balance between empowered, autonomous teams, and improving leverage via common platforms. Platform is a nebulous term, but can encompass common tooling and infrastructure, identity management, shared datasets, re-usable APIs, and UI styles and components.
The above areas are intentionally light on specific technologies and I look forward to delving into them in more detail in subsequent posts. By doing this, I hope that the community will come to know us, DigIO, a little better.