The Israeli Tech Radar

Back to monorepo

Monorepo has become popular on frontend because it offers a way to share code between projects without having to link it between different repositories, and also can bring together all the resources for the developer to have her/his own environment running, including backend. Monorepos has gained more tools (lerna/ yarn WS / Nrwl Nx / BILT / Rush) however it affects ops complexity and may need a dedicated team to return to Silo mode.

Cloud-native runtime - DevEnv personal (k3s) or hybrid (containerd, skaffold, telepresence, Cloud IDE’s). Due to the increase in development and deployment with Kubernetes, we are increasingly identifying tools that come to support the developer environment in the process of development and debugging over Kubernetes. There are two prominent paradigms:

• Local Kubernetes (K3S, Minikube, Kind) whether using Skaffold for local CI/CD, allowed us to locally run micro-service, and debug it with the deployment environment in Kubernetes. It including all other microservices.
• Hybrid mode, such as Telepresence, which allow us to run the code locally from IDE integrate with other services in the cluster.

- Classic DevOps shift-left and DevOps split to categories of expertise (FinOps, DataOps, SecOps, MLOps) - Developer requires to know more: docker Image, K8s, Cloud Infra  - Personal devenv (k3s) or hybrid (containerd, skaffold, tilt, telepresence)

We Identify that some of the DevOps roles like the CI (build) and the CD (writing helm files) are more common practice and moving to the developers and from the other side the DevOps subdomain get special expertise and roles like FinOps, DataOps, MlOps and SecOps. The rise of such roles implicates the complexity of those subdomains, and the need for an employee to focus on it exclusively.

In the area of multiple technologies and tools, there is a need for special teams which specialize in software infrastructure. Those teams are in charge of creating infrastructure which simplifies application building. In startup companies usually a Full Stack team covers infrastructure development. However, when the company grows, the infrastructure becomes complicated. Building a platform team allowing application developers to focus on business needs, mitigating the complexity of the overall architecture. The platform teams focus on tools building, by researching the plethora of tools offered by the community and tailor the best solution for the company needs. Doing so, reduces time to market and increases ROI.  When the platform team grows to cover the growing needs of the company, there becomes a need to divide the team into sub-teams with focused specialties. For instance, a platform team for data management and another for application infrastructure.

The Covid-19 pandemic caused an unprecedented wave of tech adoption for businesses across all industries – as companies learned to work remotely and connect with customers virtually, they essentially crammed a decade’s worth of tech adoption and digital transformation into a single whirlwind year. Companies Must Get Creative – Fast – To Cultivate Tech Talent

• Upskilling employees.
• Reimagining training for tech talent.
• Turning to the global freelance economy.
• Getting creative in their benefits – offering the flexibility of remote work is a no-brainer