Operations | Monitoring | ITSM | DevOps | Cloud

Fiber optic cables carrying massive amounts of information on pulsating beams of light are a critical part of the physical infrastructure supporting our digital society. By their nature, these cables are highly exposed, spanning huge distances in territories beyond the control of a network operator whether underground, under water or on aerial cables, and popping up in equipment huts.

A networking problem can come from almost any fault within the infrastructure, whether it’s a bandwidth bottleneck, configuration issues, or a faulty networking component. But more than half of IT system outages are caused by hardware failure. The ability to quickly identify and resolve hardware issues goes a long way toward ensuring optimized performance. While this may seem like a simple solution, there are many, many potential hardware failure points, each of which can contribute to a slowdown.

One benefit of the lockdown triggered by the coronavirus epidemic has been a renewed enthusiasm for working at home. Forced to let millions of employees work from home to avoid contagion, companies that had been hesitant about taking this step have concluded they can benefit from moving to a remote workforce.

During the Data World event, Erwin Halmans, Project Manager of Data-Driven Network Operations & Assurance at T-Mobile Netherlands, Shounit Lax-Swisa, CEO of Company Booster, and Anodot Chief Data Scientist and Co-Founder Ira Cohen got together to discuss the future of network monitoring.

During Anodot’s week-long Data World event, I hosted a panel with tech leaders Amiram.

Welcome to part one of our five-part “AWS Well-Architected Framework in Serverless” series. In this article, we’ll give you a short introduction to the AWS Well-Architected Framework and dive deeper into the Security pillar to explain it and some actionable ideas related to it. To learn more about the AWS Well-Architected Framework (WAF) through the serverless lens and how to build Well-Architected architectures, make sure to attend our upcoming webinar on Friday, 27 November.

When you complete your big cloud migration project, by all means celebrate, but don’t party too hard. The job’s not done. Digital transformation is never finished. Technology will progress. Customer expectations will evolve. The competition will advance. And your business must grow. This means that the transition to hybrid and multi-cloud is not a one-time event—it’s an ongoing process.

We’re a little late to the party. Fashionably late. By now the world knows that DockerHub has removed the free, untraceable goodness of anonymous pulls. How dare they? How dare they build a revolutionary technology, open-source it and give it away for free at a substantial cost to themselves. It’s worth calculating what a couple of petabytes of CloudFront bandwidth would cost, even with a substantial discount. It’s mind-blowing.

Application developers are turning to Node.js as one of the most popularly used Javascript frameworks for microservice development. Node.js tops the list of most utilized frameworks amongst the developers worldwide in 2020 by 51.4 percent. With the increasing demand for Node.js technology, it has become crucial to monitor the performance of the applications, servers, and other metrics.

Kubernetes and robotics make a great match. However, as we have seen, robots running ROS 2 can be tricky to set up on Kubernetes. This blog series has explored running ROS 2 on Kubernetes, set up a simple talker and listener, and distributed that demo across three machines. The configurations presented may not quite fit your implementation, and you may want to dig a bit deeper into network traffic when troubleshooting.