What is on the way?

-

 What is the next technology that will change our lives? 

In year 2000 Java was supposed to take over the world. Vision at that time was to have Java in all devices and it will be interconnected. Your fridge can maintain grocery list and you can place an order from fridge. Your heater can be turned on when you start for your home. Lights can be controlled remotely. 

Some of these vision are reality now. It took more than 10/20 years for them to be a reality. There is one more technology coming our way which will change the technology landscape. I am not sure when it will be widely available. I am talking about 5th generation of mobile network. 

If we go by the earlier generation it might take more than 10 years. So it might be 2030 when technology based on 5G will be a reality. It took us 10 years to move from 3G to 4G. From the challenges 5G imposes bigger challenge. It requires more cells than 4G. It is harder to have same availability indoors. I think it will be prudent for me to skip the challenges and leave them to cell companies.

With latency in range of 20-30ms promise of 5G is huge. Many of the recent innovations like VR, or lens will work with 5G. We don't need to do lot of computing in the device. It can be done in the server and rendered to the device. Experience in devices like chrome book will be lot better. 

Will 5G change the experience with netflix or spotify. Probably no. To some extent yes. But it will be a small improvement in experience. You might be able to stream better quality videos. Interactive experience will be better with 5G.

If you look closely lot of these ideas which will be a reality with 5G are not new. They were busted dotcom ideas. Lot of recent success were sold in different shape in early 2000. They went bust because they were not ready.

We will be seeing lot of new technology as 5G catches up. It may not be IOT as hyped. But there is lot of hope. Same time there can be a different tech that will upstage it.

Comments

Post a Comment

Popular posts from this blog

Greedy computing with API

-
Image
 We all know computing resources have a cost. Memory, long term storage, transportation and computing all have their own costs. There are lot of scenarios where your API end point won't be able to respond in time. These are scenarios where you need to use more resources to provide a response. Let us be greedy with our resources and explore different patterns which can solve this. Polling  This is a commonly used pattern where the caller initiates a process. Then keeps on checking if the process is complete. If the process is complete then the caller reads the data needed.  This is a good pattern when both systems are part of the same organization. At least developers of caller and callee should be able to discuss this implementation.  Call back This is an improvement over polling pattern. Here the caller supplies a call back URL to the long running process. Once the process is complete it calls the callback URL and informs the caller that process results are availabl...
Read more

ChatGPT for cavemen

-
Image
I heard a lot about ChatGPT and thought to come out of my cave to find out what the hype is about. Is it going to eat all my lunch or eat me for lunch?  Like any product I gave it all my details and signed up. I asked it about quantum computing an it gave some answer. So far so good. Next day I wanted to check its blogging skills. So I opened chatGPT and I got this . I checked throughout the day and it is still down. So it won’t eat me till it is fed few more servers.  Continuing after it was up.  I asked it to write a blog about itself. Here is what was generated by chatGPT.
Read more

Event driven architecture for micro services

-
This is a work in progress. I am designing an event driven architecture to be used in systems using micro services. Micro service architecture is popular because it solves few problems in development process. While it solves some problems it also brings in new problems to the table. Bad designs impact micro services harder than monoliths. But this is thought is for another time.  How micro services talk to each other. In a monolith you have one gigantic database, or you can easily call another component to process the information. In a microservice you can use a Que (or event bus) to pass the information. This is the problem I want to discuss. Main issue with que is it is not designed for this scenario. There are few products which give a good solution by providing a subscription-based approach. But these are large implementations. Using these is similar to bringing an excavator to plant a sapling in your garden. Yes, many people go with using these large implementations to resolve...
Read more