Information Technology Broadcasting - اطلاع‌رسانی فناوری اطلاعات
410 subscribers
13.9K photos
41 videos
505 files
489 links
Information Technology, Cloud computing, Digital transformation, IoT, Edge computing, IT governance, Fog computing, IT security, IT regulation, IT trends, Programming، Big data, Monitoring, Databases, Api, Service
Download Telegram
What Does “Real Time” Mean? Less than 30 Milliseconds

Real‑time transaction processing and analytics have become an important building block for compelling digital experiences. How do we characterize what real‑time is? Research suggests real‑time has to be less than 30 milliseconds (ms).

Consider these proof points:

13 ms for humans to process images.According to a study by neuroscientists at MIT, the human eye can process and identify entire images in as little as 13 ms.Researchers asked subjects to identify a series of six to twelve images, each presented for between 13 and 80 ms. The fastest rate at which subjects identified these images was 13 ms.

20 ms to synchronize video. An IEEE paper about using ‘Media fingerprinting’ technology to prevent loss of synchronization between image and sound when delivering video content states that the tolerable limit for latency is between 6 and 20 ms.

30 ms to deliver wireless data. Ubiquitous connectivity is on the horizon with the introduction of 5G technologies, which promises peak speeds of up to 1 Gbps and latency of less than 30 ms. Why such low latency? Because 5G needs to be that fast to replace in‑home WiFi and wireline broadband like fiber and cable modems.
Cloud Migration

Phase 1: Audit and Rationalize

Identify which of your mission-critical applications should be prioritized for your migration, and which should be deprecated or replaced by cloud-native applications. For example, should your custom-built legacy application running on Java really be migrated to the cloud, or could the business see benefits from moving to a software-as-a-service (SaaS) solution?

Phase 2: Optimize

Once you have a clear vision of which applications you’re prioritizing, think about how moving them to the cloud might create opportunities for improvement. For example, could you put in place a new security framework to protect access to your application and data? 

Phase 3: Enhance

Seek out elements of your application (or the services to it) that could be enhanced without having to fundamentally change it. Could you take advantage of cloud-native storage capabilities like Cloud Spanner to replace the aging database that your application runs on, for example?
Phase 4: Modernize

Later, you’ll have the opportunity to fundamentally change your application to be fit for the cloud by “modernizing” it with cloud-native services. These will likely provide better functionality than your existing environment. For example, could the part of your application that allows users to add and manage metadata in documents be replaced by a machine-learning engine that does that automatically and requires human intervention only for exceptions? How quickly could you break up existing applications into microservices and APIs with individual components that could be iterated upon and deployed independently of each other, thereby rapidly increasing your development velocity, while reducing cost and risk?