We have also uncovered a few emerging trends that we would like to track in this space
Enabling multi-cloud shifts: As cloud infrastructure scales in complexity and size across org sizes, optimizing for performance and cost becomes a priority front and center. Multi-cloud infrastructure is more complex to handle owing to the increased risk of security risks, necessity to recruit specialists and added complexity with cost and performance optimization. Tooling that can cater to security, governance, config-management, would be pivotal to enable the cloud transformation that even legacy players are attempting to make.
API-first economies: As companies increasingly become API first, the tooling and platforms that exist to support collaborative tasks, governance, security, testing and deployment of APIs. Creating solutions that support API lifecycle management from design to observability for APIs designed in house and integrated from third party solutions would be critical
Even more shift-left paradigms will emerge: Shift left testing strategies were born out of the realization that the cost and impact of a bug as it moves further down the software development workflow increases exponentially. Similarly shifting security and compliance left are also themes that are emerging in companies like Jit, Ethyca.
Enhancing the edge development experience: As edge computing gains more adoption, emphasis on the tool stack that developers have there will also increase given the unique constraints that these environments pose. This includes the vast sprawl of CDNs and their corresponding configuration options, interoperability of edge runtimes across different platforms, managing the life cycle of applications across deployments.
A few interesting themes around this include:
- The use of automation to enable edge scalability and optimize on the basis of factors like traffic, usage, energy consumption.
- Moving AI to the edge using both hardware and software innovations, this addresses various privacy concerns and caters to the low latency requirements of some use cases
Leave a Reply