Why is Artificial Intelligence important?

Image
The AI learning adventure explores intelligence and its connection to engineering and technology.  Using ideas about human intelligence and intelligence more broadly, engineers can create “artificial intelligence,”; that is, impart “human” intelligence into machines or technology (Classical AI) or design technology that can itself “create” intelligence (future AI).  In fact, understanding how the brain works—”reverse-engineering the brain”—and understanding how engineers design intelligent machines—machines that replicate human intelligence—is one of the “Grand Challenges of Engineering” as set forth by The National Academy of Engineering (NAE). The implications and benefits of understanding the brain are many.  In addition to advances in the treatment of brain injuries and diseases and advancements in communications technology and computer simulations, understanding the brain will allow the design of intelligent machines with even more signicant societal impacts.  Already, mac

Top 10 companies working on DevOps | NIIT digiNxt


DevOps a few year old concept has captured the whole market.All top companies have carted from traditional to digital approach.It has multitudinous benefits including shorter development cycles,increased deployment frequency and time to market.    



DevOps killing Top 10 companies


1.      Amazon
Initially, Amazon worked to dedicated servers. They faced provocations in predicting how much equipment to buy to meet traffic demands. As a result, about 40 percent of Amazon's server capacity was wasted
When Amazon carted to AWS (Amazon Web Services) cloud , it allowed engineers to scale capacity up or down incrementally. Within a year Amazon moved to AWS and allowed engineers to deploycode every 11.7 seconds, on average.
The agile approach also reduced both the number and duration of outages, resulting in increased revenue.
2. Netflix
When Netflix evolved its business model from shipping DVDs to streaming video over the web, it waded into uncharted waters. There weren't any commercial tools, so it turned to open source solutions. it created the Simian Army, a suite of automated tools that stress test Netflix's infrastructure and allow the company to proactively identify and resolve vulnerabilities before they impact customers.
Nteflix uses automation and open source and today engineers deploy code thousands of times per day. The rate at which this entertainment game-changer has adopted new technologies and implemented them into its DevOps approach is setting new standards in IT.

3. Target
Inside Target,several groups are into DevOps.These days DevOps not only powers the development of projects like Cartwheel, Target's mobile savings app, but also has transformed the organization's culture. Target now hosts DevOpsDays for its internal teams, featuring demos, open labs, lightning talks, breakout sessions, and guest keynotes. It also continues to spread the good word through the business community by sponsoring Minneapolis DevOpsDays meetups.
4. Walmart
While Walmart is the king of big box retailers in the American heartland, online it has always struggled in the shadow of Amazon. To gain ground, it assembled a cutting-edge team through several tech acquisitions and founded WalmartLabs, the retailer's technology innovation and development arm, in 2011.
WalmartLabs then adopted DevOps to compete in market.It incorporated OneOps cloud-based technology, which automates and accelerates application deployment. It has also created several open source tools, including Hapi, a Node.js framework for building applications and services that allows developers to focus on writing reusable application logic instead of spending time building infrastructure. More recently, it deployed more than 100,000 OpenStack cores to build its own private cloud, and it continues to evolve its agile approach.
5. Nordstrom
Its still working on waterfall model, big batch releases, and lots of shared services when it undertook rewriting its in-store clienteling application. When it finally launched the program two and a half years later in 2011, it was already irrelevant.Nordstrom's customer mobile app team was the groundbreaker for its DevOps makeover. After surfacing the reasons behind mobile's 22- to 28-week lead time, the team broke down the divide between dev and product support and organized squads around value. The company also migrated to continuous planning and moved to a single backlog of work. As a result, bugs went down, throughput went up, and releases went from twice per year to monthly. More importantly, Nordstrom realized these methods could work for any team, and it's continuing to apply them across the organization.

6. Facebook
Facebook changed the whole concept about software development. Many of the tenets it adopted early on, including code ownership, incremental changes, automation, and continuous improvement, were DevOps in all but name. Its approach has matured over the years, and it recently migrated its entire infrastructure and back-end IT to the Chef configuration management platform (and made some of its cookbooks available to the public).
Its recently announced bi-weekly app updates effectively served notice that constant, rapid refreshes for mobile apps are the new normal, and any company that can't keep up risks getting left behind.
7. Etsy
Initially, Etsy struggled with slow, painful site updates that frequently caused the site to go down. In addition to frustrating visitors, any downtime impacted sales for Etsy's millions of users who sold goods through the online marketplace and risked driving them to a competitor.
With the help of a new technical management team, Etsy transitioned from its waterfall model, which produced four-hour full-site deployments twice weekly, to a more agile approach. Today, it has a fully automated deployment pipeline, and its continuous delivery practices have reportedly resulted in more than 50 deployments a day with fewer disruptions. And though Etsy has no DevOps group per se, its commitment to collaboration across teams has made the company a model of the DevOps framework.

8. Adobe
Adobe's DevOps transformation began five years ago when the company moved from packaged software to a cloud services model and was suddenly faced with making a continuous series of small software updates rather than big, semi-annual releases.
To maintain the required pace, Adobe uses CloudMunch's end-to-end DevOps platform to automate and manage its deployments. Because it integrates with a variety of software, developers can continue to use their preferred tools, and its multi-project view allows them to see how a change to any one Adobe product affects the others.

9. Sony Pictures Entertainment
Sony Pictures Entertainment's Digital Media Group (DMG) faced significant provocations in delivering a software system to manage entertainment assets for end users. Manual processes and other hurdles typically resulted in a months-long delay between completion of software development and delivery.
To smooth out this "last mile," DMG implemented an automated cloud delivery system composed of open source tools and SaaS solutions. Since embracing a continuous delivery model, DMG has cut down its months-long delivery time to just minutes. This allowed developers to focus on adding features and reduced idle resources and associated costs.
10. Fidelity Worldwide Investment
Like other enterprises, Fidelity Worldwide Investment had several business units developing software applications. Apps were deployed manually across hundreds of servers, with each app requiring customization. Manually introduced errors frequently broke the process.
When it came time to develop a critical trading application with a firm launch date, the organization knew its error-prone manual process would jeopardize the project. Fidelity used the opportunity to embrace a DevOps approach and implement an automatedsoftware release framework that would enable it to meet the rollout schedule.
That solution resulted in more than $2.3 million per year in cost avoidance for that app alone. Since then, the Fidelity team has automated the release of dozens of applications, reducing release times from two to three days to one to two hours and decreasing test-team downtime. The process has also made it easier to display regulatory compliance and has enabled predictable release schedules that stakeholders can rely on.


Comments

Popular posts from this blog

Innovate your business through Test and Learning Approach

Waterfall vs Agile and Scrum Methodology

How to identify the right DevOps tools | NIIT digiNxt