Cyber Security Predictions for 2017

2016 was a big year in the annals of Cyber Security, and 2017 promises to eclipse it.

Creating an Enterprise Data Strategy

An introduction to the process of developing comprehensive strategies for enterprise data manangement and exploitation.

A Framework for Evolutionary Artificial Thought

Let’s start at the beginning – what does this or any such “Framework” buy us?

The Innovation Dilemma

What things actually promote or discourage innovation? We'll examine a few in this post...

Digitial Transformation, Defined

Digitial Transformation is a hot topic in IT and big money maker for consultants - but what does it really mean?.

Showing posts with label Cloud. Show all posts
Showing posts with label Cloud. Show all posts

Saturday, October 19, 2013

3 Common Cloud Challenges

Like all new technology trends, Cloud Computing brings with it both opportunities and challenges. Unfortunately, the current hype cycle across the IT industry hasn't done the best job of defining either very well (at least not yet). Most of the information out there tends to portray the Cloud as a the ultimate (latest) silver bullet technology.

So, is it?  From my perspective - it could only be viewed as a a conditional, evolutionary improvement - and only if - the organization adopting it fully understands the implications of the technology. Which brings us to a discussion of common Cloud challenges...



Before we jump into that though, let's quantify what we're talking about a little better. There are several types of Cloud-related capability that an organization can pursue; these include:

  • Construction of one's Clouds
  • Exploitation of 3rd party Clouds (Amazon, Rackspace, Google etc.)
  • Adoption of (limited) 3rd party Cloud services or software (SAAS)
  • or some type of Hybrid solution
We shouldn't get too bogged down in the differences between Infrastructure, Platform and Software as a Service or Public versus Private Clouds at this point because the challenges we're examining today cut across most of these distinctions. 


Common Cloud Challenges:

  1. Proliferation and Governance
  2. Automation
  3. Integration

Now if any of these seem familiar, they should. These are all challenges that first became apparent during the explosion of  "legacy" data centers for distributed computing back in the 90's and early 2000's. Let's look closer...

Proliferation: Just because you can provision a completely new environment rapidly doesn't mean that you really need to or some cases even should. The model that Amazon uses to serve millions of different customers shouldn't be the same as the model you use for a single enterprise. The more environments (virtual or otherwise) that you have to create, the more you have to manage. Growing these exponentially is a particularly bad idea (although knowing that you can is somewhat cool). This is where Governance should come into play. However Cloud Governance is a practice that's running about 2 to 3 years behind deployment and provisioning - not good...

Automation: It took about 15 years to begin to get the traditional data centers running smoothly - much of that was due to the introduction of network and system administration automation tools. The explosion of Cloud solutions over the last 3 or 4 years has led to the creation of mountains of custom code and glueware to help run IAAS, PAAS and SAAS solutions. This is a serious problem and one that can be remedied soon given that nearly every major automation vendor has now re-architected their solutions for Cloud environments.

Integration: The last issue bleeds into this one. What happens when you introduce a Cloud, or multiple Clouds into your organization? Does all of the legacy capability go away? How do you control data, security, performance and interfaces across hosting platforms? Integration is the number one challenge facing Cloud adopters today and will remain so for quite some time. There is only way to solve the Cloud Integration dilemma - that's through the introduction of comprehensive Cloud Architecture. We will define that in our next post...



Copyright 2013, Stephen Lahanas

Wednesday, June 19, 2013

Joomla versus Wordpress

Deploying and maintaining websites used to be quite the ordeal, especially if you had content intensive requirements or clients who wanted to be able to update key design features such as navigation on a regular basis. While approaches for how to manage that process improved from the early 90’s through to early 2000’s there was still a great deal of manual coordination and update required. Changes in scripts deployed inline needed to be adjusted in every page deployed. Also, sometimes the pages design rendering was inconsistent from one section of a site to another - this too required polishing to get just right. The addition of CSS (cascading style sheets) and external scripts helped but pre-CMS website development was still a significant challenge – and this was for sites with relatively simple expectations for application or database support.

Old Timey Web development has a strange connection to Married with Children - there may be a similar link between Mobile development and Modern Family...

In the late 1990s and early 2000’s, SharePoint and a whole slew of commercial portal products hit the market, targeted primarily at enterprise users. These types of products offered the chance to build sites without quite so much manual design, but the products soon became fairly specialized in their support for integration with larger back-end systems. That specialization and the cost involved with this class of system made them unappealing or unrealistic for the majority of website developers. At the same time all of this was occurring, the web development community had amassed an ever greater array of applications that could be plugged into site development. Many of these apps at first were built using CGI and later PHP became the standard (although many languages have been used including .net). By 2005, there were several groups that had effectively combined a number of these apps into coherent platforms – those platforms shared the same core characteristics:
  1. Holistic control panel interfaces (not unlike those used by web hosting providers).
  2. Content management features – this was focused around page publication and abstraction of content development from page deployment.
  3. Style blocks – the ability to segment off panels or blocks to position specific content or application features.
  4. Application support – development of core code and APIs for interaction.
  5. Shared data structure – single instance DB to support platform and all applications.
Perhaps most importantly, this new breed of Web Content Management Systems (WCMS) became community-based and open source. This had two immediate and powerful effects:
  • First, it made these platforms universally available to all and any web developers for any purpose they could imagine.
  • It ensured a growing set of application plugins designed to run on that platform would be available. For anyone who had worked with the more expensive portal software or even SharePoint, this difference is striking. The lack of a community to tends to translate into limited capability and an overall high cost of ownership as most added features end up being custom coded.
So, what is a WCMS anyway? At first glance the title seems a bit inaccurate – in 95% of the cases – a WCMS is not used as a Content Management System. A WCMS is more like a web publishing platform that happens to support CMS features (to facilitate content development and deployment). Not too long ago there was another class of software that was referred to as Web Publishing – it dealt primarily with management of complex magazine like sites (software such as Interspire). Most of those packages have come and gone and now the definition of what constitutes "Web Publishing" has more or less merged with social media (Twitter and Blogs are considered web publishing as well yet management of these is in the Cloud at the host, and less complex).

For our purposes though, Web Publishing within the WCMS involves very comprehensive features (some might say almost limitless) for design control and application extension. So, for all intents and purposes, the platforms have become ubiquitous for web development – supporting just about any Use Case that you can think of – everything from a simple site, to a community forum, to a magazine or an online store. You can do all that and more, and in a fraction of the time it previously required.

Value Proposition of the WCMS

Why is all of that important? Well, adoption of a WCMS translates into the following value proposition for most web developers:
  1. These platforms support rapid prototyping – getting the site up and running actually becomes easier than the style-sheet work – although with the superstructure up – it becomes feasible to highlight many more design options simultaneously.  
  2. Using these platforms allows smaller shops or teams to handle more simultaneous work (in most cases).
  3. Using a WCMS allows for plug and play application features (and potentially this could extend to all application features of a site). Custom configuration may still be required but the level of effort is an order of magnitude smaller. 
  4. Setting up training and maintenance processes for any sites developed using these platforms can be consolidated to one effort (e.g. the first manual and training class you prepare becomes the template for all others with relatively little rework required).
  5. The mobile strategy and main site can be planned and rolled out in tandem. 
Now, that we've talked ourselves into a WCMS, what next? Well, the obvious next question is which one ought to be used. There are quite a few WCMSs out there, but the vast majority of all users have adopted one of four (open source) tools right now:
  • WordPress (most popular)
  • Joomla (second most popular)
  • Drupal (probably third)
  • DotNetNuke (in the running).
So, we've already narrowed down the options based on the first criteria, popularity. Popularity is important when considering open source software for the reasons we mentioned previously:
  1. It implies a more dynamic community which means the software will keep getting better and more comprehensive.
  2. It also implies that we will have an ever growing pool of new (plugins or extension) apps to choose from.  
For the purposes of this article, we’re going to make the first round selection based entirely on that criteria and now the choice is narrowed to the top two; Joomla versus WordPress.

WordPress – This WCMS began life as blog platform in 2003. The first CMS features were deployed across two releases in 2005 and by 2008 WordPress had shifted from being primarily blog focused to be a full-featured CMS. One of the key differences between WordPress and Joomla historically had been that many of the WordPress blogs / sites began life within WordPress's hosting environment (what we’d now call the Cloud). WordPress is used in 60 million websites (although a good percentage of those are purely blogs with little functionality used – more or less equivalent to blogger.com).

An example of a Joomla-based solution (circa 2011)
Joomla – Joomla began life as a commercial product called Mambo in 2000. Shortly, thereafter an open source version of Mambo was released and eventually the Mambo project forked into other projects including Joomla which launched in 2005. Mambo / Joomla was built to be a CMS from day 1. There have been approximately 30 million downloads of Joomla since 2005.

Both platforms support very large feature sets, although evaluation just on the competing lists doesn't tell the whole story – in other words, they both look equally impressive on paper. Before we can rate them however we’ll need to add our remaining criteria; those are:

  • Ease of Administration – this is generally typified by the admin console but can extend to other features or considerations.
  • Design Flexibility – This relates more to what is possible from a design perspective.
  • Design Ease of Use – This relates more to how hard is it to conduct those designs.
  • Content Management – Each CMS has its own idiosyncrasies.
  • Application Functionality (extensibility) and integration of that within the platform – Sometimes the same apps developed for WordPress and Joomla behave differently in either platform. Also, there are some apps you can find for one but not on the other.

So, given that popularity is already factored out, we could assign a 20% weight to each of the criteria listed above and we might rate each area from 1 to 5 (1 lowest, 5 highest). Here’s our score card:

Category
Joomla
WordPress
Ease of Administration
5
3
Design Flexibility
4
4
Design Ease of Use
5
3
Content Management
4
2
Application Functionality
4
3
Totals
22 (of 25) 88%
15 (of 25) 60%


There are those who might say ratings are determined in part by which tool you used first. In our case this doesn't apply, as over the past 15 years we've worked with more than a dozen different CMS and portal products and hundreds of similar scripts that were eventually pulled together to build these types of WCMS platforms. For us, the true measurement is how long does it take to build using one platform versus another and then how much of that is due to the platform itself (as opposed to unique requirements). For those of us in who work in IT and have had to evaluate dozens or even hundreds of different tools over our careers; we’re able to develop a certain level of objectivity when contrasting technology.

So what do these ratings really mean; here are some associated observations:

  • In the most important metric, time to develop / complete / deploy a site on Joomla on average took 25% or less time than WordPress.
  • The WordPress multiple blog (Network feature) is still not quite ready for prime time.
  • WordPress was built first for blogs and it shows, the design metaphor is little clunky and the widget (design blocks) can take on a life of their own – making design much more time consuming than it should be.
  • You’re more likely to run into application / widget compatibility issues on WordPress.
  • WordPress does though seem to be getting some apps that aren't being made available on Joomla, some of these are more focused towards the enterprise which is a serious long-term issue for Joomla (if it is to remain competitive).
  • In Joomla, management of page (CMS) taxonomy is definitely more complicated than WordPress, however this is a relatively small part of the overall web development effort and isn't too hard to get used to.
  • Both WCMSs have suffered major security flaws in the past, this will likely continue to be the case (but isn't nearly as complex as dealing with the Microsoft stack and SharePoint).
  • One of the biggest issues we ran into with WordPress was the embedded editing capability (and errors associated with it). The editors (which can be added as extensions to the administration consoles) seem to perform better on Joomla – this is a big deal from a content management standpoint.
  • Overall, we found it harder to achieve some of the core design functionality in WordPress than in Joomla (everything from placement of blocks to the ability to run content sliders etc.)
  • The application update notifications in WordPress are nifty, but don’t completely make up for other failings (in getting them to work properly for example).
  • The WordPress blog moderation console is pretty cool and shows where WordPress really excels. However, for many web Use Cases, this is unnecessary.

Bottom line – in the WordPress v. Joomla battle, Joomla wins in most categories (in situations where an organization hasn't already invested a lot of time in one or the other). How long this will remain the case is hard to tell, but based on our review it would probably require several major architectural changes in the core WordPress platform to complete the shift in its evolution from blog platform to WCMS.



Copyright 2013, Stephen Lahanas

Thursday, November 22, 2012

Enterprise Integration Maturity Levels


In the previous posts, we have defined the key concepts of:

Today we're going to explore a related topic - Enterprise Integration. Integration is involved to some extent in all of the above listed topics. We will first review some guiding principles for integration and then provide a high level descriptions for integration maturity levels. 


Integration Principles
Enterprise Integration Maturity Levels

Legacy Integration Level
This level represents organizations transforming from a silo maturity level. In these situations integration is tightly coupled and usually not comprehensive. Even still the legacy integration maturity level generally reduces operational and maintenance costs while enhancing capability. These cost reductions are realized by reducing redundant and laborious data entry processes and reducing batch cycles to transform and transfer the data from one system to another. From this transition the data is available on a with reliable delivery of data and automated data format conversion for the integrating systems. The transformation from structured programs to all modular also leverages re-usability of the code and help and re-usability and reduction of the software maintenance complexity since the software is more modular. The modular code increases readability of the code best reducing maintenance time.

Componentized Level
Organizations transforming from an integrated maturity level to componentized maturity level  benefit in preparing themselves to expose business functionality at more granular levels. The re-usability also matures to a business function level as compared to an application level. Enhancements and new functionality are achieved through re-factoring in existing applications into smaller reusable components. The dis-aggregation of the business logic in itself helps in reducing the complexities of systems and facilitates the analysis of the impact of componentized solution on new business models and business transformations. This componentization also helps the business in reducing the time to market and increases IT response to business changes.

Shared Consolidated Infrastructure Level
This involves the deliberate unification / consolidation of Data Center capabilities including:

  • Shared Hosting
  • Virtualization 
  • Process Integration (ITIL)

Service Level
The transformation from a componentized maturity level to a service maturity level evolves the organization into a service provider. The service provider role can serve other organizations within the enterprise as well as external organizations. Business services now become reusable as this maturity level reduces the need for redeveloping the same functionality for multiple systems by the provision of reusable business services called through a standardized interface irrespective of the technology platform on which the application is running. These business services can also offer access to data in a controlled timely manner which reduces inconsistencies in the data within systems that access and update the data. The investment of effort in service identification, specification, development, testing and implementation is paid back when new systems require the same service from the providing organization since the cost of infrastructure and maintenance of common functionality is reduced.

Composite Service Level
Organizations transforming from the Service maturity level to Composite Service maturity level have structured their business and IT support so that new business processes may be more rapidly constructed out of business services and provide new business functionality to different parts of the organization more efficiently. This maturity level is also associated with reduction of the time to market for new business models or capabilities. At this level transformation it is primarily a re-composition of the business services provided by different organizations within an enterprise of the value chain in the enterprise.

Software as a Service (SAAS) Level (Cloud)
Software as a service is the next logical maturity level. SAAS builds upon the shared (Cloud-based) infrastructure and shared enterprise capabilities developed in the previous maturity faces. SAAS allows organizations to provide capability as a commodity which either enhances existing revenue generation functions or creates new ones. In addition, systems may be reconfigured to achieve higher reliability without the consumers having to modify their code. Software as a Service enables organizations to better align business requirements with IT capabilities by building robust services that are highly flexible, manageable and scalable.


Copyright 2012  - Technovation Talks, Semantech Inc.

Monday, November 19, 2012

Understanding Enterprise Standardization

Just last week, we introduced the concept of Enterprise Transformation. Enterprise Standardization is often considered to be a part of Transformation, with special attention usually being given to data and shared service and infrastructure standardization. We can think of Standardization efforts as being the tactical elements of any given Strategy or (umbrella) Transformation initiative. Transformation is more EA focused, while Standardization must necessarily grapple with issues at the project level.


The ability to develop, harness and manage enterprise business capability begins with the ability to standardize the design process and with it the solution architecture. Standardization encompasses a number of different tactical areas including, but not limited to:

  • Business Process
  • The Data itself
  • Hardware / Infrastructure (this generally involves both process as well as data center consolidation)
  • Network Management
  • Application Lifecycle Management (ALM, this includes Agile)
  • Business Rules
  • Data Architecture
  • Security
  • Commercial Software (and COTS Lifecycle Management)

A shared services paradigm (based on SOA) usually traverses many of these areas and facilitates their integrated management within an Enterprise perspective. The idea here is that with all of the different design approaches available, there needs to be mechanisms in place to integrate them. (if you don’t or can’t integrate design approaches, how can you hope to integrate the solutions developed from them?)

Enterprise Transformation generally requires multiple Standardization efforts
We’ve alluded to the need for greater standardization both in the context of architecture / design as well as in solution management in order to support a wider Transformation. Standardization is thus applicable at many levels. In particular, standardization provides a mechanism to help move from IT silos to unified Enterprise solutions. In that sense it becomes both a means and an end goal.
Specific decisions that lead to standardization include things such as:

  • Adoption of standard software platforms. 
  • Adoption of standard hardware platforms.
  • Adoption of technical standards and best practices.
  • Adoption of standard enterprise processes.
  • De-conflicting of redundant logic, rules and systems.

Ultimately, the management of integration of heterogeneous IT environments and business models becomes the most expensive component of the business and the one most likely to add operational risk (w/o standardization). Thus, specific Standardization projects within a Transformation are likely to yield the highest return on investment - exactly which ones though hold the most value is usually determined on a case by case basis as every organization is somewhat unique.


Copyright 2012  - Technovation Talks, Semantech Inc.

Sunday, November 18, 2012

Key SOA Design Principles


SOA primarily refers to a set of architectural principles. These principles represent a design continuum that links software development to Cloud deployment and capability exploitation. To support those principles a variety of standards and products have been developed to facilitate implementation and maintenance of SOA solutions. These standards include but are not limited to the following:

  • SOAP - Simple Object Access Protocol
  • UDDI - Universal Description, Discovery and Integration
  • WSDL - Web service definition language
  • WS Policy
  • WS Security
  • WS Addressing

The core SOA Use Cases are dependent upon its architectural principles

The design principles most often agreed to as representing SOA include the following (and yes some of these principles are inherited from Object Oriented Design or expand upon it):
  • Standardized Service Contract – Services adhere to a communications agreement, as defined collectively by one or more service-description documents.
  • Service Loose Coupling – Services maintain a relationship that minimizes dependencies and only requires that they maintain an awareness of each other.
  • Service Abstraction – Beyond descriptions in the service contract, services hide logic from the outside world.
  • Service Re-usability – Logic is divided into services with the intention of promoting reuse.
  • Service Autonomy – Services have control over the logic they encapsulate.
  • Service Statelessness - Services minimize resource consumption by deferring the management of state information when necessary
  • Service Discoverability – Services are supplemented with communicative meta-data by which they can be effectively discovered and interpreted.
  • Service Composability – Services are effective composition participants, regardless of the size and complexity of the composition.
  • Service Encapsulation – Many services are consolidated for use under the SOA. Often such services were not planned to be under SOA.

The history, technical goals and expectations for SOA can be described thusly: “Service-oriented architecture (SOA) is an evolution of distributed computing based on the request/reply design paradigm for synchronous and asynchronous applications. An application's business logic or individual functions are modularized and presented as services for consumer/client applications. What's key to these services is their loosely coupled nature; i.e., the service interface is independent of the implementation. Application developers or system integrators can build applications by composing one or more services without knowing the services' underlying implementations.”


Copyright 2012  - Technovation Talks, Semantech Inc.

Friday, November 16, 2012

What is Enterprise Transformation?


by Stephen Lahanas

At the highest level, “Enterprise Transformation” simply represents the set of initiatives necessary for an organization to adopt new technologies, better facilitate processes and enhance core capability applied to achieve mission objectives. The main differentiation between enterprise and specific or domain level transformations is the scope of the effort. Once an organization moves to this type of effort it typically involves:

  • Enterprise-wide Analysis
  • Enterprise-wide Architecture Design
  • Sequenced or Concurrent Implementations
  • Evolution of Management & Governance


A conceptual visualization of the architectural implications of SOA
What tends to come out of such a transformation is an architecture better aligned to business objectives. Services Oriented Architecture or SOA represents a critical first step towards attaining that improved alignment but by no means represents the full scope of potential transformation opportunities; once movement to a services paradigm is achieved the following additional transformation activities may occur:

• Migration to Cloud Computing business models and architectures.
• Full integration across Data Architectures built atop a Semantic and MDM foundation.
• Migration to a holistic enterprise Cyber Security management paradigm.

Services Oriented Architecture represents an enabling capability for all of these other objectives mainly because it facilitates the move from stove-piped IT management to an enterprise perspective. SOA also provides in many organizations the first opportunity to enact a global governance approach that allows organization to coordinate management across the entire enterprise. While there are some forms of enterprise transformation that don't require a move towards a service-oriented paradigm, those solutions are becoming less and less common. Even ERP solutions are now being positioned as services, although the mechanism for deploying them is a more focused on large COTS software packages - but much of that too is moving towards the Cloud and being served from there.


Copyright 2012  - Technovation Talks, Semantech Inc.