Slashdot Mirror


Gartner Reveals Top 10 Technologies For Next 4 Years

Dr. Jim writes "The good folks over at the Gartner Group have revealed the top 10 technologies that they believe will change the world over the next four years. The usual suspects including multi-core chips, virtualization, and cloud computing are on the list. Multicore servers and virtualization will mean that firms will need fewer boxes, and apps can be easily moved from box to box (and right out the door to an outsourced data center). Workplace social networks and cloud computing means that the need for a centralized IT department will go away. Firms will no longer need to own/maintain the boxes that they use to run their firm's apps. With no need to touch a box, there will be no need to have the IT staff co-located with the boxes."

1 of 163 comments (clear)

  1. Re:Forgetting one thing by laddhebert · · Score: 5, Interesting

    Cloud Computing while a cool CS Concept and can be used in some cases. The fact that most apps are single threaded design will not gain any benefit from this and most companies don't need that level computing power. They would wast money and get small benefit. Unless they do some massive computing. I had to reply to this.

    If you have a shop that has a very large compute farm that runs exclusively, batch jobs, then you can clearly understand where cloud computing can be a tremendous advantage. A lot of users of batch compute resources find creative ways to serialize and/or parallelize their overall process using scripts, multiple hosts, dependencies, etc. With cloud computing, all of this can be implemented automatically.

    That's a huge time and cost saver right there alone. Additionally, with our cloud computing solution (Electric Cloud), we get an additional advantage with the built in virtualization that comes along with the system. In the old days, we were forced to manage multiple development build stacks to satisfy the needs of multiple business units or departments. Now, we manage a cloud of hosts that are baseline installs, with bare minimal configurations, and the submit host's environment is replicated to the cloud nodes when a build is kicked off. This saves money on hardware resources, hardware resources, engineering resources, etc.

    You may think, well, most developers use the same build stack or tool stack - but that's an assumption that has been proven incorrect time and time again where I work. We work with embedded device developers and they have a very specific tool stack requirement, with specific versions, or may need a pristine build environment without the possibility of conflicts from various packages that may be installed on the build host.

    /-l

    --
    Don't Panic.