Avoiding Enterprise Web Scale Pitfalls
An explanation of what web scale is, how tools like Kafka and Storm distill the best practices of companies like Google, and how it all affects Enterprise Architecture
Join the DZone community and get the full member experience.Join For Free
not too long ago, it was little more than a cost center – do more with less, keep the lights on, and struggle for relevance in an era when it didn’t matter. the world of enterprise it comprised legacy systems, physical servers, and inflexible architectures.
then along came google. and amazon. and ebay. eventually facebook, netflix, and scores of other technology-based companies joined in, rethinking what it was all about. many of these twenty-first century darlings drove innovation in hardware, networks, software, and the architectures that made everything work.
welcome to the world of web scale .
in spite of these astounding advances in technology capability, the denizens of enterprise it continue to struggle with legacy systems, legacy software, legacy…everything. their world still centers on constrained resources – not enough speed, not enough scale, not enough money to go around. keep the lights on and maybe – just maybe – you’ll get to do a bit of innovating as well.
the web scale world is just the opposite. these companies had cracked the nut — speed and scale in abundance, with no ball-and-chain legacy in sight. not coincidentally, their pace of innovation has reached unprecedented levels, as web scale market caps surpass those of traditional enterprises, many of whom spent decades to grow to their current size.
web scale, therefore, represents both the technology itself, as well as a way of thinking about how to manage and grow an innovative business at scale.
enterprise executives around the world are now thinking to themselves: we need that. now we know it works. how do we bring the world of web scale to the enterprise?
as enterprises progress with their digital transformation initiatives, they typically implement elements of web scale within their it organization. however, you can’t take a century-old bank and expect to turn it into google — nor would you want to.
fundamentally, web scale means something different to a traditional enterprise than to the web scale companies themselves. we call this perspective enterprise web scale .
web scale companies, of course, had the luxury of being able to architect their environment for web scale from the beginning. enterprises, however, are not so lucky. such companies scale by adding new capabilities onto existing ones, as retiring legacy assets is rarely practical or cost-effective.
architecting enterprise web scale
the capabilities enterprises are likely to add to their environment to build out enterprise web scale capabilities are likely to come from a set of relatively new open source projects. perhaps the best known of these is hadoop , but hadoop was merely a harbinger.
today we have a plethora of open source initiatives that one way or another distill the best practices of web scale companies like google, salesforce, and others. on this list: cassandra nosql database, kafka message broker, solr enterprise search server, and storm real-time event computation system, among others (all from the apache foundation).
the four apache projects above are in varying stages of maturity, with work going on at a frenetic pace. as a result, enterprises have largely taken a wait-and-see approach to them up to this point.
however, that wait-and-see attitude is rapidly changing, as enterprise decision makers increasingly realize that the risks of not taking advantage of enterprise web scale as their organizations become software-driven is perhaps greater than the risks inherent in implementing such still-maturing technologies.
as a result, enterprise architects must step up to the table as advisors for all things web scale. they must not only keep tabs on the progressing capabilities of each package, but understand how any web scale technology under consideration fits into the existing it landscape.
furthermore, becoming web scale for an enterprise typically means integrating web-scale capabilities with existing on-premise assets. this reality presents two core challenges eas should be prepared to address: first, they must understand the subtleties of integration in the context of web scale to on-premise, and second, they must maintain the big picture of the overall strategy goals of the it organization and the enterprise at large.
the integration challenge presents what we might call an ‘impedance mismatch’ — connecting fast to slow, or more precisely, integrating elastic, asynchronous infrastructure with existing traditional apis, and database interfaces.
perhaps an enterprise leverages a public or private cloud in addition to existing on-premise capabilities. another common pattern is for a company to build out big data capabilities (either in-house or in the cloud) that must now integrate both with the sources of data as well as with the business intelligence, visualization, or other analytics tools that consume and display the results of the big data processing.
leveraging older integration technologies like etl or esbs to solve these modern integration challenges is more likely to cause performance bottlenecks and other issues. instead, consider integration technology like snaplogic’s , which is designed to support integration in enterprise web scale environments.
driving end-to-end digital with enterprise architecture
integration, however, isn’t the only challenge that eas are well-positioned to address. simply adding web scale technologies to an existing environment is the recipe for additional silos – both technological as well as organizational.
however, in spite of the silos so typical of any large enterprise, the digital priorities of the organization are end-to-end . all elements of a customer-facing app, from the user interface all the way to the underlying systems of record, must perform all the time, and at top speed.
in fact, the end-to-end requirement – both technological and organizational – is perhaps the most transformative aspect of digital transformation for many organizations. as a result, eas should spearhead the effort to avoid making the situation worse by treating newer web-scale efforts as a separate silo.
the secret: eas must always circle back to the underlying business driver for any it investment, web scale or otherwise. in the context of today’s digital initiatives, such business drivers are usually customer-focused – and customer needs will not be met by creating a separate web scale silo.
in the final analysis, enterprise web scale requires more than simply adding new technology. it requires both modern integration approaches as well as an end-to-end organizational context that enterprise architects are well-suited to lead.
snaplogic is an intellyx client. at the time of writing, no other organizations mentioned in this article are intellyx clients. intellyx retains full editorial control over the content of this article. image credit: ryan hodnett .
Published at DZone with permission of Jason Bloomberg, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
Building A Log Analytics Solution 10 Times More Cost-Effective Than Elasticsearch
Send Email Using Spring Boot (SMTP Integration)
RAML vs. OAS: Which Is the Best API Specification for Your Project?