Feed aggregator

  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.
  • warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home1/stasocom/public_html/stevestaso/includes/unicode.inc on line 345.

Why Cloud Native is the Second Cloud Revolution

eWeek Cloud Computing News - Thu, 03/31/2022 - 13:44

Cloud native is of one of those terms that caught the wave of tech press hype. The term is so hot right now that some companies are “cloud native washing” their products and services to ride the cloud native wave.

Unfortunately, many of them don’t understand what cloud native is, or truly understand its core benefits. However, like sharks that can scent blood in the water, these companies do realize that a second cloud computing revolution could be upon us.

To begin, let’s address the confusion. Many take the term “cloud native development” just the way it sounds: The building of software systems that are native to a specific cloud provider such as AWS, Microsoft, or Google. Thus, they can leverage that provider’s native security services, governance services, database services, etc., and allow the application to get the most from that cloud provider.

In contrast, non-native systems would be decoupled from a specific cloud provider. While the systems can run and function, they don’t take advantage of native cloud services.  Therefore, they may cost a bit more to run, and they don’t take advantage of useful native cloud services that would make the application perform better. Because they don’t leverage services from the native cloud provider, you have to write or integrate the services yourself.

Despite those who take the term literally, there is a growing number of people and organizations that look at cloud native as an emerging architectural pattern.

Also see: Cloud Native Winners and Losers 

What’s the Value of “Cloud Native”?

The emerging definition of cloud native can be counted as the true revolution in how we design, build, deploy, and operate systems moving forward.  In other words, this new cloud native approach rethinks how we get more value out of the software systems we create, and how we leverage these approaches on all platforms, not just public clouds.

This new way of looking at the value of cloud native includes the Cloud Native Computing Foundation’s (CNCF) explanation: “Cloud native technologies empower organizations to build and run scalable applications in modern, dynamic environments such as public, private, and hybrid clouds.” Perhaps better put, cloud-native applications can be deployed across multiple cloud environments, including traditional platforms. This is core to the emerging cloud native proposition and defines what the fuss is all about.

The CNCF works with a larger idea: If you do cloud native right, you’ll provide dynamic and scalable application behavior on many platforms that include public clouds, private clouds, and even legacy systems. Most are taken aback by the support of legacy and even older private clouds. However, the idea is to promote a method of getting something done without focusing on the underlying technology.

Also see: Top Cloud Companies

Containers and Microservices

Typically, a cloud native approach requires the sophisticated use of containers, container orchestration, and microservices to avoid lock-in, which is a desirable outcome of going cloud native.

New cloud native systems usually define a common stack where the private and public clouds are the foundation that can reside on any platforms. These platforms would include legacy computing, edge computing, and any emerging platforms that may appear in the future. Again, the idea is to build things differently, with a focus on the “big picture” end goals of the system under development. If the focus was just on a particular technology, the value would be short-lived.

With all that said, we can define cloud native as an approach with the following advantages:

  • It leverages the architectural advantages defined by public clouds without having to run on specific clouds.
  • The architecture is a collection of independent microservices that can exist in a one or more lightweight containers.
  • The foundational platforms, including clouds, don’t typically provide services directly to the application, instead they use a layer of abstraction.
  • These cloud native containers allow simplified deployment to any platform, including legacy systems, cloud computing platforms, or even remote devices.
  • The cloud native containers can obtain common services supported by the platforms, to the limits of the platform, such as scalability.
  • Common services such as security, governance, and operations can be defined across containers, and can be leveraged with or without direct engagement with the host platform.
  • Cloud native containers may move from platform to platform, such as cloud-to-cloud or cloud-to-legacy, without significant disruption of the behavior of the software and the patterns of data storage.

Also see: Why Cloud Means Cloud Native

What’s the Cloud Native Revolution?

Many of the advantages listed above can be found in past architectural approaches, such as container development and orchestration, or in enabling technologies, such as services offered by most public cloud providers.

What’s new here is that we’re looking at cloud native as a concept of “how” and not “what.” Cloud native is not about technology; it’s about how we approach systems design, development, and deployment, no matter what technology and/or platform we deploy.

The focus of cloud native won’t be on the hottest new cloud technologies to build and deploy applications. Cloud native leverages several open technologies that, unto themselves, are not true solutions. However, when combined with the specific architectural patterns we’ve listed above, any number of technologies can be leveraged to live up to cloud native design patterns.

The goal of cloud native is to provide software systems that are more likely to solve the business problems at hand and be more durable moving forward than the more traditional approaches to application development. Cloud native also means that we no longer focus on the development technology or the platforms. One of the side effects of moving to cloud native development is that we now define how something is done, and not what technology to leverage.

Cloud native will be a perplexing conundrum for those vendors, cloud and not, that want to define their technology as providing a specific value that’s different from their competitors.  The cloud native approach will force many technology vendors and cloud service providers to figure out ways to work and play well together to allow for cloud native development and deployment, where many different technology configurations and solutions become part of the end-state cloud native solution.

Necessary Elements to the Cloud Native Revolution

This revolution only works if there are a few pieces that fall into place.

First, cloud native needs to be adopted by those charged with building and deploying systems. No matter how compelling cloud native is, the adoption factor will be the most difficult to achieve since the direction of the technology market is always difficult to predict.

Second, vendors and cloud service providers must work together to provide interchangeable and mostly open technologies. They can’t keep focusing on unique ways of doing things that fall outside the bounds of cloud native. Instead, they need to focus on how their customers would like to build the systems and the end-goals of those systems.

With those two pieces in place, the term “cloud native revolution” will take on its true meaning. Cloud native is a sea-change in how we build and deploy systems moving forward. Moreover, its focus is to remove technology dependency from the equation. That’s never been possible in the past. Let’s see if we can make cloud native work now so we can look forward to a brighter future.

Also see: Tech Predictions for 2022: Cloud, Data, Cybersecurity, AI and More

The post Why Cloud Native is the Second Cloud Revolution appeared first on eWEEK.

Categories: Cloud Computing News

California Privacy Rights Act and Enterprise Data Management: Key Updates

eWeek Cloud Computing News - Wed, 03/30/2022 - 13:56

California took bold steps to protect consumer data in 2018 with the California Consumer Privacy Act (CCPA), the first U.S. data privacy regulation that promised strict oversight and severe financial risk for businesses. This landmark legislation increased awareness about the need to protect consumer data and the individual rights of a user. It took steps toward greater transparency with how companies collect and use consumer data.

California voters showed they were completely on board with the law by recently voting to create the California Privacy Protection Agency and expand the CCPA through the California Privacy Rights Act (CPRA), which will take effect on January 1, 2023.

The new law broadens the existing CCPA definition of an individual’s sensitive data to include any information reasonably capable of being associated with a person. The new law also makes it easier for consumers to regulate the processing of sensitive information.

What this means is that companies are forced, once again, to take stock of their data management and cybersecurity processes and create best practices. This includes regular assessments of data across its entire lifecycle to evaluate the value of that information to the organization and to determine whether it should be appropriately sanitized or stored securely.

Also see: Best Data Analytics Tools 

Far-Reaching Privacy Law

There may be some confusion about CCPA compliance, but make no mistake, any business that meets certain criteria—no matter where it’s located—must comply with the law if it wants to do business in California. With a population of 39 million, the number one economy in the U.S., and with a growth rate only exceeded by China, California is a highly desirable market for businesses around the world.

Companies that must comply with the CCPA include those that operate for profit and that determine the purposes and means of data processing. Furthermore, they exceed at least one of the following three revenue/information processing thresholds:

  • Has annual gross revenues of $25 million (USD) or more.
  • Derives 50% or more of its annual revenue from selling or sharing California residents’ personal information.
  • Annually buys, sells, or shares the personal information of 100,000 or more California residents or households.

Also see: Top Business Intelligence Software 

Achieving CCPA Compliance Through Data Management Best Practices

One goal of the expanded law is to create greater trust among consumers by assuring that their data will not be mishandled. To accomplish this, the CPRA expands upon the CCPA by setting limitations on the collection, storage, and usage of personal and sensitive data beyond a certain time frame that’s been agreed upon with the consumer.

Some of the key changes to keep in mind include:

  • The collection, use, retention, and sharing of personal information must achieve the purposes for which the personal information was collected. This will require the regular assessment of data across its entire lifecycle to evaluate the value of the information to the organization and to determine whether it should be sanitized or securely stored.
  • A comprehensive audit trail of data across its lifecycle, from point of collection to sanitization, must be maintained. This will allow data to be accounted for in the unfortunate event of a data breach.
  • Consumers will have the right to correct inaccurate information and limit the use of sensitive personal information.
  • The new law also expands the right of access to cover information collected over a longer period of time and removes exceptions that allow businesses to refuse deletion requests.

Chances are that all of the above will require companies to adapt their current processes and implement best-in-class data management practices.

Also see: Data Mining Techniques 

Better Enforcement, Stiffer Fines

The consequences of non-compliance are stiff. The California Protection Agency in conjunction with the California Attorney’s Office will be empowered to bring both civil and administrative enforcement actions against any business suspected of violating the updated CCPA law, starting on July 1, 2023.

Business owners found in violation of the CCPA could face administration fines of up to $2,500 for each violation and up to $7,500 for each intentional violation. Penalties for misuse of a child’s information are especially heavy. 

Non-compliance related to processing a minor’s personal information, such as requiring opt-in consent from either the minor (if between 13 and 15 years of age) or their parent/guardian (if 12 or under), have tripled for negligent violations involving children aged 16 and under.

Also see: Real Time Data Management Trends

A Win for Consumers and Businesses

The bottom line is that the CCPA is a good thing for consumers. The measures in the original CCPA, as well as requirements associated with the new and improved version, are meant to protect consumers’ personal data. Together they give consumers a high level of control over how their data is used and what it’s used for, including its monetization.

Businesses benefit as well. Because the new CCPA will require many businesses to revise their data management and security practices, including how and when they implement regular sanitization as a preventative practice, they will reduce their threat attack surface and mitigate the risk of fines due to potential legal actions.

With less than a year to prepare for the expanded CCPA regulations, businesses must move now to create new policies that meet California’s new mandates. Organizations that take the original CCPA and the amended version of the law seriously by adapting their data management processes, including data sanitization and cybersecurity protections, will stay out of the crosshairs of the CPRA. Additionally, they will create strong customer relationships built on mutual trust and respect for consumer privacy.

Also see: Top Digital Transformation Companies

About the Author: 

Fredrik Forslund, VP of Cloud and Data Center Erasure, Blancco

The post California Privacy Rights Act and Enterprise Data Management: Key Updates appeared first on eWEEK.

Categories: Cloud Computing News

Dynatrace vs. Datadog: 2022 Software Comparison

eWeek Cloud Computing News - Wed, 03/30/2022 - 11:16

Both of these solutions, Dynatrace and Datadog, have emerged as leaders in the IT and application performance monitoring space. Both platforms deliver cloud-based Software-as-a-Service (SaaS) offerings that continuously gauge performance and identify issues before they become full-fledged problems.

And both help manage increasingly complex information technology (IT) frameworks – a growing challenge for companies. Organizations must ensure that servers, databases, applications and a vast array of other tools and resources are operating correctly and performing well at all times. Organizations that falter risk glitches, breakdowns and complete failures.

As a result, infrastructure and application performance monitoring tools like Dynatrace and Datadog have emerged as mission critical requirements. Solutions that address this space deliver deep visibility into various aspects of system performance by scraping data from various sources, including logs, tags, data flows, software code and devices. They identify relationships, gauge network behavior and spot problems.

Dynatrace and Datadog also tap data analytics, machine learning and other forms of artificial intelligence to deliver broad and deep insights. The result is a unified view of resources: what’s performing well and what’s underperforming. Let’s take a look at how these two applications compare.

Also see: Real Time Data Management Trends

Dynatrace vs. Datadog: Integration Comparison

The Dynatrace solution delivers visibility into more than 600 hundred products, services and technologies through a robust set of APIs. Monitoring capabilities encompass Active Directory, Adobe Analytics, AWS, Apache, Azure, Cisco, Citrix, Linux, Docker, Drupal, Google, IBM, Microsoft, Salesforce and Slack.

There’s also support for Kubernetes, Java and a vast array of other entities. Thanks to a broader set of integrations, Dynatrace holds a slight edge in this category, though both products are likely to accommodate virtually every requirement an organization can toss at them.

The Datadog platform delivers built-in support more than 500 integrations that extend across a broad mix of systems, apps and services. Datadog offers powerful auto-discovery features that can find almost every major solution and vendor.

The list includes Active Directory, Adobe, Cisco, SAP, Akamai, Alibaba Cloud, AWS, Azure, Google, Salesforce, IBM WAS, Oracle, Okta, Zoom and Zendesk. It also accommodates Kubernetes, Java and Linux components.

Dynatrace vs. Datadog: Compare Monitoring

The point of any monitoring solution is to deliver a comprehensive view of a technology stack. Dynatrace succeeds through robust real-time and synthetic tracking. It relies on a single agent per host to collect all relevant data and metrics continuously.

The platform delivers a view into the full stack—everything from the behavior of visitors at a website to technical factors such as performance of clouds, mobile and Web APIs, DevOps automation, container functionality and ecosystem integrations. The firm’s PurePath Technology also provides distributed and automated transaction tracing and code-level visibility. This makes it possible to analyze end-to-end transactions across every tier of the stack.

Datadog’s highly flexible and easy-to-use interface delivers high quality and visually appealing dashboards and notebooks that deliver a single place to view events and data, including container and API metrics. Datadog offers broad and deep visibility into the entire stack, with granular filtering and highly detailed logging for websites, applications and various other components.

The platform also delivers excellent customization through Dashboards, Timeboards and Screenboards that provide different visualizations. All of this makes infrastructure reviews and root cause investigations much simpler. It also helps DevOps teams identify bottlenecks and problems. Finally, Datadog offers a Session Replay feature that helps troubleshoot and fix UX and other problems.

Also see: Top Business Intelligence Software 

Dynatrace vs. Datadog: Performance Comparison

Dynatrace offers solutions designed for vertical industries, including airlines, healthcare, telecom, manufacturing, e-commerce, retail and financial services. It is available for Windows, Mac and Linux devices.

Because it’s a cloud platform, it’s also possible to access features from a web browser. Dynatrace provides advanced capabilities such as continuous and automated AI discovery across the full stack, including multi-cloud environments, microservices and containers. This includes automatic real-time topology and mapping with context, self-healing and automation features, and the ability to hyperscale the solution across hundreds of thousands hosts, millions of entities and even the largest and complex multi-cloud environments.

Dynatrace can be set up as either a managed or SaaS solution. It offers encryption capabilities to keep data secure. It also includes features for Internet of Things (IoT) monitoring and management.

The Datadog platform delivers live process infrastructure monitoring but also supports continuously historic records, including those for retired or defunct systems. Datadog, which supports Windows, Mac and Linux devices, accommodates tens of thousands of key metrics out of the box.

Its APM component delivers end-to-end distributed tracing with minimal latency and an ultra-low error rate. Datadog also offers AI capabilities that allow it to auto-discover new components and auto-track them. Machine learning helps identify false positives and false negatives that lead to irrelevant and unnecessary alerts. Datadog delivers a variety of features and capabilities focused on infrastructure, APM, security monitoring, network monitoring, synthetic monitoring and more. The platform supports data encryption. However, it lacks some of the network access and control features that Dynatrace provides.

Dynatrace vs. Datadog: Reporting Comparison

Reporting is a critical element in Dynatrace’s infrastructure and application performance management. The platform delivers deep insights through analytics tools and reporting. It’s possible to generate reports based on specific criteria and easily share the reports via email and other messaging tools.

A dashboard displays various applications and systems, and includes a score based on the percentage of problems and failures. Teams can use this data to diagnose and address various issues and problems. The platform also offers extensive real-time notifications and alerts—with filtering capabilities. However, it lacks a re-notification feature.

Datadog offers a flexible and robust reporting framework with drag-and-drop features, including widgets and pre-designed templates to accommodate most industries and use cases. The platform also provides tools for building custom reports. A Metrics Summary page displays key performance indicators for different time frames, including hours, days and weeks. Datadog also allows users to search on various factors and indicators using tags and other criteria. It offers robust notification and alerting capabilities, including the ability to re-notify people.

Also see: What is Data Visualization

Dynatrace vs. Datadog: Compare Service and Support

The widespread popularity of Dynatrace translates into a robust and highly rated online community. There’s also an extensive online knowledge base that aids in setting up and using the platform. Dynatrace offers standard tier Web and chat support on an 8/5 basis. Its Dynatrace One Premium tier includes live phone-based in-product assistance, a dedicated product specialist manager and 24/7 continuous support. The company has high user ratings for providing service and support in a timely and efficient manner.

Datadog operates a community forum and has a comprehensive online knowledge base available for users. The latter includes documents that cover almost every aspect of the platform and various products. Support depends on the version of the software an organization uses. Free and basic versions of the company’s products are typically backed only by a discussion group. Other offerings include chat and email support. More advanced offerings include priority phone support.

Dynatrace vs. Datadog: Pricing Comparison

Dynatrace offers a free trial. It has a tiered pricing model that covers different service needs. For example, a digital experience monitoring package starts at $11 per license per month billed annually. It covers AIOps along with digital business analytics.

Application security starts at $12 per month and covers automatic continuous runtime analysis. Open ingestion that monitors metrics, logs, traces in the context of a common data model costs $25 per month. Infrastructure modeling is $21 per month. It covers infrastructure monitoring, AIOps, and Digital Business Analytics.

Full stack monitoring runs $69 per month. It includes APM, infrastructure monitoring, AIOps, and Digital Business Analytics. Cloud automation starts at $0.10 per cloud automation unit. Although Dynatrace offers powerful capabilities, it tends to be pricy.

Datadog has a complex pricing model based on the specific service. For example, infrastructure has a three-tier pricing model. A free version supports up to five hosts and includes core collection and visualization features. However, it offers only a 1-day metric retention.

A Pro version costs $15 per month per host. It includes 500+ integrations, out-of-the-box dashboards and 15-month metrics retention. The Enterprise version (100 host minimum) includes machine learning-based alerts, live processes and premium support. Datadog also offers volume discounts for those requiring 500+ hosts per month. Overall, Datadog is more affordable than Dynatrace.

Also see: Top AI Software 

Dynatrace vs. Datadog: Conclusion

Clearly, both Dynatrace and Datadog offer a wealth of features and capabilities that make them highly appealing – both have an impressive roster of customers.

Nevertheless, it’s important to review the various connectors and features each offers before selecting a vendor and installing a solution. In addition, pricing plans can lead to significantly different costs, and support options may or may not fit your needs. As a rule, Dynatrace is more widely adopted by large enterprise, while Datadog tends to appeal more to small and medium-sized businesses.

The post Dynatrace vs. Datadog: 2022 Software Comparison appeared first on eWEEK.

Categories: Cloud Computing News

Scaling Deep Learning/AI Applications: 4 Best Practices

eWeek Cloud Computing News - Tue, 03/29/2022 - 16:55

A common lament among machine learning engineers is that, in general, productionizing machine learning (ML), deep learning (DL), and AI applications is problematic. Many engineers would attest that a large percentage – estimated at 90% – of ML models never see the light of the day in production.

Let’s examine four best practices to prevent these problems. Derived from industry trends, practitioner literature, and codified MLOps best practices, these four best practices will improve the process of deploying models in production.

Also see: Top AI Software 

1) Get Your Data Story Sorted

Data is complex and dirty. It’s complex because data varies in form and format: batch or streaming; structured, unstructured, or semi-structured data. It’s dirty because often, data has missing or erroneous values. No deep learning or AI model is valuable without voluminous, cleansed, and feature-engineered data.

You need a robust data store to process the big data needed to build accurate models. A modern data lake stores both structured and unstructured data. A modern data lake has the following data properties:

  • Provide ACID transactions so multiple readers and writers can update and read data without contention or conflict, allowing concurrent ETL (extract, transform, and load) jobs and constant inserts and updates.
  • Store data in an open format such as Parquet, JSON, or CSV, allowing popular deep learning frameworks to openly and efficiently access data.
  • Hold structured data as tables that can be versioned and adhere to a schema, allowing model reproducibility and accountability.
  • Offer fast and searchable access to the various kinds of data (labeled, images, videos, text, etc.), allowing machine learning engineers to fetch the right data sets for the right business problem.

A modern data lake as a data store.

Without a cohesive data store as the canonical reliable and cleansed data source to all your ML models for training and inference, you’ll stumble onto your first “data” pitfall. This is true no matter which deep learning framework you use — which brings us to the next consideration.

Also see: DevOps, Low-Code and RPA:  Pros and Cons 

2) Use Well-Adopted and Widely Used Frameworks

Just as good data begets good models, so do widely adopted deep learning toolkits and frameworks. No one would dispute among the ML/DL practitioners that PyTorch, PyTorch Lightning, TensorFlow, HuggingFace, Horovod, XGBoost, or MXNet are popular frameworks for building scalable deep learning models. Aside from being widely used, they have become the go-to framework to build sophisticated deep learning and AI applications.

Adopt these frameworks because:

  • They have a large supporting community, copious documentation, tutorials, and examples to learn from.
  • They support training and inference on modern accelerated hardware (CPUs, GPUs, etc.).
  • They are battle-tested in production (used by notable companies).
  • They are natively integrated with Ray, an emerging open-source general-purpose framework for building and scaling distributed AI applications.
  • They have Python API bindings, a de facto language for deep learning.
  • They have integrations with MLflow, KubeFlow, TFX, SageMaker, and Weights & Biases for model provisioning and deploying and orchestrating model pipelines in production.

ML/DL Framework integrations with Ray and Model Registries.

Not using the battle-proven frameworks well-integrated with popular open-source tools for model development cycle and management or distributed training at scale is a sure way to stumble onto another pitfall: wrong tools and frameworks. The need for a model development lifecycle leads us to why you want to track model training using a model store.

Also see: Data Mining Techniques 

3) Track Model Training with a Model Store

The model development life cycle paradigm is unlike the general software development lifecycle. The former is iterative, experimental, data and metric-driven. Several factors affect the model’s success in production:

  • Are the model’s measured metrics accurate? A model registry will track all the metrics and parameters during training and testing that you can peruse to evaluate.
  • Can I use more than one DL framework to obtain the best model? Today’s model registries support multiple frameworks to log models as artifacts for deployments.
  • Were the data sources reliable and sufficient in volume to represent a general sample? This is the successful outcome of getting the data story right.
  • Can we reproduce the model with the data used for training? The model registry can store meta-data as references to data tables in the data store. Access to the original training data and meta-data allows reproducing a model.
  • Can we track a model’s lineage of evolution — from development to deployment — for provenance and accountability? Model registries track versioning of each experiment run so that you can extract an exact version of the trained model with all its input and output parameters and metrics.

Tracking experiments for models and persisting all aspects of its outcome — metrics, parameters, data tables, and artifacts — gives you the confidence to deploy the right and the best model into production. Not having a data-and-metric-driven model for production is another pitfall to avoid. But that’s not enough; observing models’ behavior and performance in production is as important as tracking experiments.

Also see: Data Mining Techniques 

4) Observe the Model in Production

Model observability in production is imperative. It’s often an afterthought – but this is at your peril and pitfall. It should be foremost. ML and DL models can degrade or drift overtime for a few reasons:

  • Data and model concept drift over time: Data is complex and never static. The data with which the model was trained may change over time. For example, a particular image trained for classification or segmentation might have additional features unaccounted for. As a result, the model concept of inference may drift, resulting in errors, drifting away from the ground truth. Such detection of drifts requires retraining and redeploying a model.
  • Models’ inferences fail over time: Model predictions fail over time, giving wrong predictions, resulting from the above data drift.
  • Systems degrade over a heavy load: Though you account for reliability and scalability as part of your data infrastructure, keeping vigilant health of your infrastructure – especially your dedicated model servers during spikes of heavy traffic – is vital.

Also see: Tech Predictions for 2022: Cloud, Data, Cybersecurity, AI and More

About the Author: 

Robert Nishihara is the Co-Founder and CEO of Anyscale. He has a PhD in machine learning and distributed systems. 

The post Scaling Deep Learning/AI Applications: 4 Best Practices appeared first on eWEEK.

Categories: Cloud Computing News

3 Key Components of Secure Workload Access For Multi-Cloud

eWeek Cloud Computing News - Tue, 03/29/2022 - 15:56

The acceleration of digital transformation over the past two years has radically shifted the way enterprises need to protect themselves from today’s modern cybersecurity threats. In particular, the move from monolithic applications to a highly distributed modern application architecture is causing the number of workloads and communications within and across clouds to explode.

In fact, nearly two-thirds of global organizations have adopted the microservices model over the past two years. The ensuing shift in traffic patterns is giving resourceful cybercriminals the ability to target workloads to exploit security policy and control gaps to compromise applications. From there, they can move laterally from one application to the rest of the network.

Zero Trust is quickly gaining momentum among enterprises as a counter to these modern threats, providing a far more robust security posture that supports digital transformation instead of hindering it. Based on the principle of “never trusting, always verifying” before allowing access to applications and resources, Zero Trust removes the assumption of trust, limits access, and authenticates based on identity and context.

Also see: Top Cloud Companies

Limitations to a Legacy Approach to Zero Trust

Zero Trust is often only used for securing user access to enterprise networks rather than securing workload-to-workload communication. To protect these increasingly sophisticated, highly distributed applications, enterprise security teams need to secure the workloads themselves completely, without any security gaps or blind spots.

The problem is that traditional firewall solutions are primarily built for the perimeter, and require internal traffic to be backhauled to an appliance in the data center where security policies can be applied—a process that increases latency, saps bandwidth, and adds complexity to network infrastructure. This complexity forces security teams to select what traffic should be monitored and secured.

In a world where an enterprise’s security posture is only as good as its weakest link, this is an unacceptable choice.

Operationalizing Secure Workload Access

Enterprises need a way to operationalize secure workload access at cloud scale. This requires the simplifying of Zero Trust architecture through a software-based, distributed approach that delivers security directly into the hypervisor.

Being able to secure workload-to-workload communication accelerates the adoption of Zero Trust principles, reduces the attack surface, mitigates lateral movement by attackers, prevents advanced threats against applications and, ultimately, unleashes the full power of the multi-cloud, microservices world.

Also see: Top Edge Companies 

3 Techniques to Operationalize Secure Workload Access at Cloud Scale 1) Deliver East-West Controls Inside the Workload 

Instead of backhauling traffic to the data center where it is hair-pinned through appliances, enterprises need to take a distributed, software-based approach to security.

This allows security teams to create and manage application-aware policies from a central control point and automatically apply them to distributed workloads based on tags. Other security services can be delivered as well—including network traffic analysis (NTA), intrusion detection and prevention (IDS/IPS) and malware analysis with comprehensive network detection and response (NDR) capabilities.

In addition, this provides continuous visibility, security, and compliance for containerized applications from development to production in any private or public cloud environment.

2) Secure Cloud Boundaries and Environments 

This software-based, distributed approach to secure workload access also requires the ability to inspect all incoming and outgoing traffic at the cloud edge. This provides comprehensive protection against threats, including signature-based detection, behavior-based detection, network sandboxing and URL filtering as well as Transport Layer Security (TLS) decryption.

When deployed with a load balancer, a gateway firewall can provide multi-cloud load balancing, web application firewall (WAF) functionality, application analytics, and container ingress services. This allows enterprises to erect defenses at the boundary of each cloud deployment.

Also see: Secure Access Service Edge: Big Benefits, Big Challenges

3) Provide Authoritative Context for Secure Workload Access

Orchestrating all this requires a centralized network services platform that provides unified visibility, control, and governance of network identifiers to simplify management of network identities and provide a framework to implement secure workload access. This creates a complete inventory of all workloads that need to be secured using identifiers such as Internet Protocol (IP) address, Domain Name System (DNS), labels or certificates.

In addition to workload identity, authoritative context may include information about the workload such as the operating system, workload type, software version, known vulnerabilities and misconfigurations and anomalous workload behavior.

The IT stack is rapidly changing, and security needs to keep up. Protecting the digital enterprise from today’s highly sophisticated threat actors requires more than just endpoint or perimeter security. In the never-ending game of cat and mouse with cybercriminals, it is impossible to stay one step ahead all the time. A Zero Trust architecture that includes secure workload access is the only way to root out and stop these attacks.

This three-pronged approach requires the ability to deliver security controls as software to distributed workloads, the ability to erect defenses at the edge of each cloud environment and a centralized network services platform that provides unified visibility and control of network identifiers.

Also see: Tech Predictions for 2022: Cloud, Data, Cybersecurity, AI and More

About the Author: 

Vivek Bhandari, Sr. Director, Product Marketing, VMware

The post 3 Key Components of Secure Workload Access For Multi-Cloud appeared first on eWEEK.

Categories: Cloud Computing News

Alteryx vs. Tableau: 2022 Software Comparison

eWeek Cloud Computing News - Tue, 03/29/2022 - 14:14

Tableau and Alteryx are two well respected business intelligence (BI) and data analytics platforms. Such applications are seeing growing demand, as business are increasingly focused on data mining their vast troves of data – both cloud and on-premise.

Whether from relational databases, enterprise applications, unstructured data, social media, or other sources, there is more data than ever that is subject to analysis. Furthermore, data mining techniques are becoming ever more sophisticated, increasing the demands on platforms such as Tableau and Alteryx.

As two popular data analytics platforms, users often are forced to choose between Alteryx and Tableau. There are arguments for and against each. It is hard to say that you could go wrong with either data tool. But which is best for your organization’s data analytics needs?

Also see: Best Data Analytics Tools 

Tableau vs. Alteryx: Key Features Comparison

Tableau is very much focused on delivering analytics with artificial intelligence, data management, and collaboration. At the heart of Tableau is a proprietary technology called VizQL that makes interactive data visualization an integral part of understanding data. It differs sharply from traditional tools that require the user to analyze data in rows and columns, choose a subset of the data, and then create a chart from that data. In contrast, VizQL skips those steps and creates a visual representation right away, providing visual feedback as you analyze.

Tableau certainly excels at visualization, which has not been a strength of Alteryx. Instead, Alteryx’s strong point has been in cleansing data, so it has been more useful for analysts in ensuring data and visualization accuracy. Why visualize or analyze inaccurate data?

Alteryx is designed to extract, transform, and load (ETL) data from a great many data sources. It engages with data via workflows throughout the ETL process. Repeatability of processes saves a lot of time on manual processes and data reentry. Alteryx does well on data discovery and management tools, too. But reporting is limited. The platform does generate reports, but these are only for direct Alteryx BI users. Yet Analytic Templates help in loading data into third-party visualization platforms.

Latest Features and Updates

Tableau, of late, has been adding features like Ask Data in Slack (ask questions using natural language and automatically get data visualizations), Einstein Discovery in Slack (predictions in work flow), and Model Builder (collaboratively build and consume predictive models using Einstein).

Alteryx, meanwhile, just boosted its platform with the release of Alteryx Analytics Cloud, which extends its analytics capabilities to a much wider set of users across the enterprise. Users now only need a browser to gain access. An automated modeling solution has been added, too, which doesn’t require data science experts to code machine learning models. Further new features include the ability to find anomalies and insights hidden in data, and provide summaries and explanations focused.

Tableau wins in terms of depth of analysis and the kind of features that data scientists, analysts and power users look for. But Alteryx closed the gap with the cloud analytics features it recently unveiled.

Also see: Top Business Intelligence Software 

Tableau vs. Alteryx: Comparing Ease of Use

Newer users are likely to find Alteryx easier to use than Tableau. Some complain that Tableau has a steep learning curve; users should be well-versed in working with the R programming language, which is used heavily in statistical programming and data analysis.

But Tableau has been working to become easier to use. Its AI-powered analytics features lower the barrier to data science techniques. Tableau works really well when Excel and statistical data are used as sources. For other formats, ease of use can suffer.

Alteryx has never had a reputation for being difficult to use. But its new cloud version makes it even more accessible. Anyone with a browser can access the platform and setup can now be done in minutes. Its low-code/no-code capabilities also make it easier for any user to extract insights that help them tackle their toughest business problems.

The conclusion: Alteryx wins on broad usage by a non-technical audience, whereas Tableau wins with more technical and advanced users.

Tableau vs. Alteryx: Analytics Comparison

Tableau tries to differentiate itself with what it describes as an intuitive analytics experience, with richer capabilities based on its VizQL engine. It can connect to data live (performing queries in-database and returning results in real-time) or in-memory (ingesting data from source systems into Tableau). This allows users to control performance, cost, and data freshness. Tableau also scores very well on live query capabilities and extracts, helping analysts to query faster. Its use of the R language makes it the winner on statistical capabilities.

Alteryx was way behind on analytics capabilities until recently. Its newly released cloud version extends analytics beyond data scientists, IT, and data analytics departments to lines of business groups. Any user can use its Designer Cloud to prepare, blend, and output data in a visual, code-free way through a browser, including on Macs.

Tableau wins on analytics capabilities, but if Alteryx’s recently unveiled analytics capabilities live up to the promised functionality in company press releases, they will have closed the gap considerably. And due to ease of use, many users may find Alteryx a better option.

Also see: Top Data Mining Tools 

Tableau vs. Alteryx: Cloud and On-Premise

Both Tableau and Alteryx evolved from the on-premises world. And both platforms have been working to change that.

Tableau offers cloud-hosted solutions such as Tableau Online and Tableau CRM, but its strength lies in on-premises deployments and this is where much of its massive installed base resides. Thus, it can be challenging to scale out Tableau workloads in the cloud.

Alteryx just came out with its cloud-based platform, which probably puts it ahead for now. Its Designer Cloud is interoperable with Alteryx’s Designer Desktop product and users can easily collaborate and share workflows between both applications.

Tableau vs. Alteryx: CRM Comparison

CRM and BI often go together. With Tableau now owned by Salesforce, it has excellent marketing and enterprise product capabilities and is being integrated with Salesforce Einstein Analytics (known as Tableau CRM). An Einstein Discovery dashboard extension, for example, brings predictive modeling capabilities from Einstein to Tableau.

Alteryx doesn’t attempt to offer CRM, although its ETL and analytics capabilities can comfortably deal with data imported from CRM systems. But it stops short of CRM functionality. Thus, for those wanting integrated CRM, Tableau wins.

Also see: Top Digital Transformation Companies

Tableau vs. Alteryx: Comparing Integration

Tableau has its hands full in integrating with Salesforce. This creates a somewhat fragmented experience between Einstein Analytics and Tableau, but steady progress is being made in bringing both together. It likely won’t be long until those issues are resolved. As a result, Salesforce customers will be upsold to Tableau and vice versa.

Alteryx provides dozens of data connectors that make it easy to import and make edits to incoming data. Users can integrate Alteryx with other cloud applications, databases, and spreadsheets. Cloud storage connectors are available for platforms like Amazon S3, Google Drive, Office 365, and Snowflake.

Alteryx, then, is largely free of integration headaches. Its cloud-based approach simplifies its deployment and use. Alteryx wins here.

Tableau vs. Alteryx: Price Comparison

Tableau has a reputation for being expensive. By some estimates, it works out to about $75 monthly per user for decent analytics functionality. But those who only want to interact with some basic dashboards can get it much cheaper. That said, the addition of Tableau CRM for a list price of up to $150 monthly per user means newer functionality and Salesforce integration don’t come cheap.

Alteryx has a completely different pricing model, so it is hard to compare them. It offers annual subscriptions. Alteryx Designer costs $5,195 per year. Additional capabilities come for a hefty fee. It looks like Tableau comes out ahead for some bids, but not all. This one depends on the needs of each organization.

Tableau vs. Alteryx: Conclusion 

Tableau boasts a large and enthusiastic user base and a very loyal user community. Its profile in the marketplace is high. Tableau’s popularity is growing, too, partially through the distribution of a free platform known as Tableau Public. This is where people can share and explore data visualizations online. It contains over 3 million interactive visualizations. Yet it is in the data scientist, analytics specialist, and power user markets where its feature set wins the most plaudits. In these markets, it is likely to be favored over Alteryx.

Alteryx has a reputation for being easier to use. While it used to be more of an ETL and data cleansing platform, it has expanded its analytical capabilities to rival Tableau. Its new cloud platform will no doubt win it orders from Tableau. For those that want decent analytics capabilities without requiring heavy duty capabilities, Alteryx probably wins.

Note though, that Gartner did not include Alteryx in its latest “Magic Quadrant (MQ) for Analytics and Business Intelligence Platforms.” Tableau was graded Tableau as a leader. Gartner will wait to see what users say in its surveys to see if Alteryx’s new cloud capabilities merit entry into the MQ.

Also see: Top Cloud Companies

The post Alteryx vs. Tableau: 2022 Software Comparison appeared first on eWEEK.

Categories: Cloud Computing News

Hewlett Packard Buys Poly To Address Hybrid Work Requirements

eWeek Cloud Computing News - Mon, 03/28/2022 - 12:04

In a surprise move, Hewlett Packard announced a definitive agreement to acquire Poly, a vendor of workplace collaboration solutions for $3.3B in cash, which is inclusive of about $1.6B in debt.

This marks the end of an era for Poly, formerly Polycom, which was one of the pioneers of videoconferencing. The current Poly company is a combination Polycom business and Plantronics, which acquired the video vendor in 2018. Later that year, Logitech attempted to purchase Poly, but the deal fell apart at the 11th hour.

Also see: Digital Transformation Guide: Definition, Types & Strategy Hybrid Work Creates a Potential Uplift for Poly and HP

This week’s news combines the collaboration endpoint business of Poly with the office equipment, primarily printers and PCs, of HP. On paper, this makes sense as businesses will be looking to refresh their office equipment in preparation for hybrid work.

In the news release, Enrique Lores, President and CEO of HP, stated, “The rise of hybrid office creates a once-in-a-generation opportunity to redefine the way work gets done. Combining HP and Poly creates a leading portfolio of hybrid work solutions across large and growing markets.”

Breaking down this quote, I’m in full agreement that hybrid work creates an unprecedented opportunity to redefine the way people work. I’m less bullish that the combined company can capitalize disproportionally on this rising tide.

It’s important to note that it’s HP, Inc., and not HP Enterprise (HPE) that is acquiring Poly. HPE’s portfolio is strategic technology, comprised of network infrastructure via its acquisition of Aruba Networks, which includes Wi-Fi, 5G and SD-WAN, AI/ML and data analytics, data center infrastructure and a broad range of cloud services.

In contrast, HP is largely comprised of commodity hardware like printers, laptops, desktops, and peripherals. Poly has historically been known as a high-end, premium price vendor, although it has been trying to move down market.

In some ways, it might have made more sense for HPE to buy Poly, as it has oriented much of its network portfolio around hybrid work. Also, historically, collaboration has proved a better fit with networking gear than with PCs.

Also see: Top Digital Transformation Companies

Short Term Benefits are Obvious, Long-Term Value is Unclear

Again, on paper, the deal does have some short-term logic. HP can help Poly with supply chain and logistics, so I do expect some immediate synergies. Also, combining the channel should create broader distribution and an uplift in sales. But the two companies are currently partners and, based on channel feedback, this “1+1 = 3” scenario has yet to materialize.

I believe the biggest issue with the partnership and with the acquisition is that there aren’t many, if any, synergies between the products that can result in cross selling. Culturally, one company deals with value-based products and the other with premium prices, and that’s a tough combination to mix.

A few years ago, there might have been a conference room play, as Windows-based PCs were an important part of meeting room infrastructure as they powered video systems. Today, that’s largely changed with Android-based appliances becoming the standard.

Outside of meeting rooms, the low end of the Poly line is personal cameras and headsets offered as an add-on to PC sales. But Poly has historically derived much of its value from the high end, which is anything but an add-on sale. If the low end, peripheral business is what HP wanted, the $3.3B price tag is a steep one.

Good Exit for Poly Shareholders

The purchase price is a good exit for Poly shareholders, a company that has struggled since the acquisition by Plantronics as they were weighed down by debt. As mentioned earlier, the concept of creating a single company to sell a portfolio comprised of peripherals such as headsets, cameras, PCs, printers, monitors does have some logic, particularly in smaller companies where there might be a single buying center.

As one moves up-market, the IT pros responsible for the HP products are not the same as the ones buying Poly. If they were, the channel partnership would have already born more fruit. How customers of the combined organizations benefit is unclear outside of some supply chain improvements.

I could be wrong here, and HP consumes Poly and then drives the $500M in revenue synergies by 2025 as stated in the press release. But I have reached out to several industry colleagues and all of them seem to think this deal fits together about as well as a square peg and a round hole. The big winner out of this might be Logitech, which has completely revamped its products at the high end. It has already been taking share from Poly but could stretch its lead even more if the new integration hiccups at all.

Also see: Tech Predictions for 2022: Cloud, Data, Cybersecurity, AI and More

The post Hewlett Packard Buys Poly To Address Hybrid Work Requirements appeared first on eWEEK.

Categories: Cloud Computing News

Go Cloud Careers CEO Michael Gibbs on What Cloud Pros Must Know

eWeek Cloud Computing News - Thu, 03/24/2022 - 14:57

Michael Gibbs, CEO of Go Cloud Careers, discusses the personal and business skills that cloud computing professionals must master to truly succeed.

Among the topics we discussed: 

  • Let’s talk about the need for tech talent, and the scarcity. What are some trends driving the tech job market these days?
  • What advice do you give to job seekers? What are a few “must haves,” beyond the tech skills themselves?
  • Advice for companies in this competitive market for tech talent?
  • What about Go Cloud Careers? What’s the advantage?
  • The future of the tech job market?

Listen to the podcast:

Also available on Apple Podcasts

Watch the video:

 

The post Go Cloud Careers CEO Michael Gibbs on What Cloud Pros Must Know appeared first on eWEEK.

Categories: Cloud Computing News

To Pay or Not to Pay Ransomware? How to Face the Dilemma

eWeek Cloud Computing News - Thu, 03/24/2022 - 14:32

Ransomware attacks lead the headlines and strike fear in the hearts of executives who face crippling operational shutdowns and public relations nightmares. Yet too many executives are prepared to pay a ransom without considering other avenues as a means of business recovery, and place too much trust in insurance coverage and the honesty of criminal cartels. Paying ransoms don’t always lead to recovery.

The question, then, is assuming you can, should you pay the ransom? And perhaps more important, can you justify the decision to your board of directors, insurance carrier, and law enforcement?

The answer doesn’t fit nicely in a yes or no convention. Perhaps the closest answer is, it depends. The point is that ransom payment is often the only choice – but shouldn’t be the first one.

Cyber insurance and data back-ups have proven a partial solution. Yet the majority of insurance policies, when paid out, create major losses for the insurer. This means premiums will go up, coverage will go down, and more “good driver history” type enforcement will apply. In fact, insurance renewals are now measured in months, not days.

And back-ups designed in the days of business continuity weren’t designed to withstand intentional espionage – which is a staple tactic of ransomware gangs. You need more than a “fix-it-after” approach.

Also see: The Successful CISO: How to Build Stakeholder Trust Avoiding Ransomware Payment Demands

When asked how you can best avoid paying a ransom, the answer is to catch the cyberattack in its early stages. Criminals employ common tactics, techniques and procedures, which provide a breadcrumb trail for security experts, and can be caught in early stages with rapid detection and response.

The faster you identify the early stages of the attack (and there are plenty of indicators), the better chance you have of preventing your adversary from establishing a persistent connection that leads to a pervasive ransomware detonation.

Assuming you don’t catch the criminals in the act, then rapid recovery is preferable to payment. With resilient business continuity practices and disaster recovery programs in place, you can restore systems while mitigating prolific service outages. It doesn’t mean the criminals won’t be back, but the first score goes to you. And while criminals can shutter your operations in minutes, it might take you weeks or months to get back to business as usual.

The majority of firms that pay ransoms believed they were prepared. They didn’t see themselves as a target. They downplayed the risk or overestimated their ability to thwart the assault. Don’t let that be you.

Before You Pay Ransomware, Do Your Homework

The legal landscape of ransomware attacks and data breaches has changed significantly over the last couple of years. Once protected by attorney-client privilege, incident response documents, executive decisions and potentially damaging budget exclusions can lead to expensive lawsuits or insurance claim denials.

And many government agencies are pushing a “don’t pay” ethos backed by restrictions and even prosecution if you make a payment to a known terrorist of cybercriminal group. As such, you need to do your homework before you decide to pay.

When faced with this decision, no one is going to make it for you. No one will indemnify your decision or alleviate knock-on liability – that’s only limited by the creativity of the plaintiff’s lawyers. You need to engage experts who can help you plan and respond to a major incident like a ransomware attack. Know your obligations.

Also see: Secure Access Service Edge: Big Benefits, Big Challenges Before Paying Ransomware: Hard Questions

I often say this: You need specific information to make informed decisions that are designed to minimize any negative impact.

If you are faced with the untenable decision to pay a ransom, ask yourself these questions before you do:

  1. Can we recover without paying the ransom?
  2. Will paying the ransom accelerate the recovery?
  3. Is paying the ransom the only viable option?
  4. Can we pay the ransom without risk of legal penalty?
  5. Should we contact law enforcement and will that help if we violate a sanction?
  6. Will our insurer cover the ransom?
  7. Should we notify our clients, partners or employees?
  8. Are we required to notify regulators or state authorities?

When you answer those questions, like the issue of ransom payment itself, it’s not a yes or no exercise. Remember, of course, that you have to stand by your answers and possibly defend your decisions in court.

Also see: Best Website Scanners 

Preventing Ransomware 

At a cybersecurity event, I had the privilege of meeting Bruce Mathison, who was a star quarterback for the Buffalo Bills back in the 1980s. While trading a signed copy of my book for a signed copy of his rookie card, he gave me the best piece of wisdom for dealing with incidents out of your control.

He said, “You don’t practice until you get it right. You practice until you don’t get it wrong.” Sage advice from a veteran of the gridiron.

So how do you establish controls and programs – methods to practice – that detect and respond to a ransomware attack? Basic security controls drastically reduce the risk of a business disrupting ransomware attack, and provide quick recovery methods that don’t rely on paying extortion fees for decryption keys (these keys don’t always work, but that’s another topic).

Here are basic controls for your two main groups:

For Employees
  1. Require multi-factor authentication to access business systems.
  2. Protect remote connections with a Virtual Private Network (VPN) or equivalent service.
  3. Mandate user awareness training and testing that covers:
    • Job-based phishing lures, not generic examples.
    • Downloading files from untrusted sources.
    • Inspecting URLs and file extensions to ensure legitimate and intended content.
    • Prohibiting free versions of applications.
    • Compliance-based requirements.
For Administrative
  1. Employ least privilege for employees and remove administrative rights where possible.
  2. Disable Remote Desktop Protocol (RDP) when not in use.
  3. Segment network systems.
  4. Regularly patch systems based on a prioritized list of critical systems.
  5. Back-up all critical files and systems using segmented or offline designs and regularly test fail-over and recovery services.
  6. Restrict administrative access to critical systems with Privileged Access Management (PAM) or similar systems.
  7. Deploy Endpoint Detection and Response (EDR) agents on Domain Controllers (DC), centralized Logging systems and Active Directories (AD) and other critical systems frequently targeted by criminals.

While bad actors will likely continue utilizing new ransomware to target vulnerabilities, there are things you can do to shore up your fortress walls. And should those walls be breached, remember to tread thoughtfully in regard to next steps.

While paying the ransom may seem like the quickest, easiest way to move forward, there’s too much at stake without asking yourself some key questions first.

Also see: Tech Predictions for 2022: Cloud, Data, Cybersecurity, AI and More

About the Author:

Mark Sangster, Vice President and Industry Security Strategist, eSentire

The post To Pay or Not to Pay Ransomware? How to Face the Dilemma appeared first on eWEEK.

Categories: Cloud Computing News

Amazon Connect Previews New Contact Center Capabilities

eWeek Cloud Computing News - Thu, 03/24/2022 - 13:33

After two years, the Enterprise Connect show returned to an in-person format in Orlando, Florida. Enterprise Connect is typically a show that communications vendors use to announce new products and features – and Amazon Web Services (AWS) did just that.

Prior to the pandemic, AWS was a relative newcomer to the contact center industry. Indeed, it was just five years ago at Enterprise Connect that the company announced its Amazon Connect contact center as a service (CCaaS) solution.

So much has changed in the contact center industry in that period, and AWS has certainly legitimized itself in the past 24 months. Let’s look at the AWS news.

Also see: Digital Transformation Guide: Definition, Types & Strategy

New Optimization Capabilities for Amazon Connect

During his keynote, GM of Amazon Connect, Pasquale DeMaio, announced the company was adding native agent forecasting, capacity planning and scheduling to the product. DeMaio was clear that this wasn’t meant to replace the already integrated workforce optimization tools it has in Connect with partners like Verint and Callabrio, but to complement it and provide a native option for customers.

Like other Amazon Connect features, this is built from the ground up and available directly in the core system. Users can turn the feature on with a single click. Once the service is turned on, the system starts to crunch numbers in the background and then data is presented to the user automatically.

For example, in the analytics interface, once the capability is turned on, there is another option called forecasting. From there, the administrator can set up forecasting groups that can be populated by dragging and dropping queues into the group. Then different types of forecasts can be performed, such as average handle times, contact volume and more.

DeMaio said that beta customers saw about an average of 5% improvement in forecasting outcomes. People who are familiar with contact center workflows know that a 5% improvement is a massive benefit. In fact, businesses often go through extensive amounts of process redesign to improve by just a single percent.

A similar flow is used for capacity planning and scheduling, where the admin simply clicks a few buttons, drags and drops some queues, and machine learning does the rest.

Transforming Contact Center Operations

This release will certainly provide Amazon Connect customers incremental value by allowing better workforce efficiency. Furthermore, the integration into the contact center platform creates some interesting possibilities to transform contact center operations that can result in a much bigger step-up in value creation.

For instance, consider a customer on hold to talk to an agent. The system informs the customer that the wait time for voice is 15 minutes and the wait time for chat is one minute. At that point the customer can choose the faster chat or hold for a live person if the issue is complex. This adds another level of optimization as customers are given information to respond to and then decide what works best for them in the moment.

While this isn’t traditionally thought of as workforce optimization, it helps offset tasks from agents, which ultimately saves money.

Also see: Top Digital Transformation Companies

Forecasting Helps Remove Sticker Shock 

This set of capabilities helps AWS customers better predict spend, which has been an issue for some customers as they look at Connect.

The entire contact center as a service (CCaaS) industry, except AWS, uses the traditional pricing model of per user per month, and a multi-year contract. Customers typically buy for peak and then overpay for times when call volume is low.

Retail, for example, would provision for Thanksgiving to Christmas volume, yet come nowhere near that level in the early part of the new year. Amazon Connect uses a usage-based pricing model where customers can provision as many agents as they want and only pay for the transactions.

This is always more cost effective than provisioning for peak utilization. Some customers have told me they get sticker shock when the bills come in as they pay for what they used and sometimes face unusually high usage. The Connect platform’s forecasting capability can help customers predict what the spend will be, so they can better plan budgets.

Even after five years, AWS is a relative newcomer to an industry that’s done things a certain way for a long time. Through its focus on customer experience, AWS is introducing cloud principals to the contact center market such as pay per use and rapid innovation. AWS’s focus has been to use AI to remove much of the heavy lifting placed on agents and managers. And in this era of hybrid and remote work, this can help companies adapt while improving customer experience.

Also see: Data Analytics Trends 

The post Amazon Connect Previews New Contact Center Capabilities appeared first on eWEEK.

Categories: Cloud Computing News

5 Backup Practices to Protect Your Azure-Hosted Desktop

eWeek Cloud Computing News - Wed, 03/23/2022 - 14:04

As employees continue to work remotely, cloud-hosted virtual desktops have become a popular platform to securely deliver the data and applications they need to remain productive.

As a result, virtual desktops have become a mission critical component of many IT environments. Making them resilient, therefore, is an important design consideration when relying on the service for access to corporate applications and data.

Whether your business is starting out with cloud-hosted virtual desktops, such as Azure Virtual Desktop (AVD), or has deployed a desktop-as-a-service (DaaS) solution for a while, evaluating your security posture while also addressing resilience with data backup and recovery is advisable.

Here are specific practices regarding all the core components of a cloud-based virtual desktop in Microsoft Azure that help ensure data security:

Also see: Top Cloud Companies 1) Virtual Desktop Service

When hosting your virtual desktops in the cloud, the cloud provider, in this case Microsoft, manages the service. No additional steps need to be taken to keep this service operating in case of a regional Azure outage.

When an outage occurs in a region, the service infrastructure components will automatically fail over to the secondary location and continue functioning as normal. One can still access service-related metadata, and users can connect to available hosts. End-user connections will stay online if the tenant environment and hosts remain accessible.

2) Directory/Identity

Be certain to employ directory and identity best practices. The services responsible for identity management in Azure – Azure AD, Active Directory, or Azure AD DS – are critical components of an AVD environment, as they are responsible for authenticating user logons into domain-joined session host VMs.

It is recommended to use native Azure AD since Microsoft is responsible for keeping this service operational within the provided SLA. If using Active Directory, create multiple AD controllers in multiple regions, and back up the AD system state.

3) Desktop Images

When provisioning new session host capacity, desktop images are critical to the task. They are used to create new session host VMs or to update existing ones with Windows or software updates.

As a backup and recovery best practice, store images with ZRS (Zone Redundant Storage) which will be available during an availability zone failure. It is also wise to use the Azure Compute Gallery to enable geo-replication of desktop images should a single region outage occur.

Also see: How Database Virtualization Helps Migrate a Data Warehouse to the Cloud

4) Session Host VMs

Azure VMs are responsible for the delivery of users’ desktops and apps. They must be available for users to be able to connect. In most pooled AVD deployment scenarios, session host VMs are clones of a desktop image and do not contain any unique user data.

Session host VMs running in the datacenter where an outage occurs will go offline. It is recommended to distribute these host VMs across multiple Azure availability zones and across two Azure regions to minimize disruption.

5) FSLogix Profiles

When a user needs to connect to a desktop or remote application, FSLogix profiles provide the user’s Windows profile data. They are vital to supporting remote workflows and should be replicated and available in multiple locations for best resiliency.

To guard against outages, use ZRS storage with Azure Files Premium. Files stored in this manner are not impacted by availability zone failure. However, for an Azure region outage you will need user profile replication.

Also see: Top Digital Transformation Companies

Actions Following an Azure Outage

Should an Azure outage occur, the first item to assess is Microsoft’s organization of AVD delivery via Azure regions and availability zones. Regions are a set of datacenters within a defined perimeter while zones are unique physical locations within a region. A zone protects your applications and data from datacenter failures. However, if a zone fails, it is imperative your initial AVD architecture and design has redundancy built in to provide recovery.

If, worst case scenario, an entire region fails, the best disaster recovery strategy is to automatically distribute AVD session hosts across two Azure regions and replicate FSLogix profile data, thereby creating an Active/Active DR configuration. If one of the regions becomes unavailable, VMs in the second region can continue servicing users.

Data Issues without any Outage

Corruption of data, metadata, or resources can also occur without any underlying data center or region outage. Changes are often made to desktop images during the normal course of AVD environment maintenance. It is important to have backups of desktop images to be able to quickly recover from any corruption. Image versioning and use of Azure Compute Gallery or library of images will help manage backup to the right version as needed.

Session host VMs can become unavailable or corrupted in the normal course of operation. It is recommended to leverage self-healing automation that automatically repairs broken session hosts without requiring IT admin action. Corruption of profile containers can also occur. Depending on your FSLogix storage technology choice – configure Azure Backup for Azure Files shares, Azure NetApp Files snapshots, or use any backup method for file server VMs (e.g. Volume Shadow Copies). Restore corrupted profile containers, as needed.

More Remote Work, More AVD

Fortunately, it isn’t too difficult to make AVD a secure and resilient compute environment for your remote workforce. First, be extremely diligent in evaluating your Azure region and availability zone coverage and employing the multiple region and redundancy tools available. Second, if you’re using Active Directory, be sure to have a system backup and restore program in place and replication as well for FSLogix profiles – all of this is aimed at avoiding access lockdown and workflows coming to a halt.

Lastly, think of making AVD security a standard part of your security planning going forward. It will pay off in worker satisfaction, revenue growth and better prepare you to scale AVD in the future.

Also see: Tech Predictions for 2022: Cloud, Data, Cybersecurity, AI and More

About the Author:

Vadim Vladimirskiy is the CEO and co-founder of Nerdio.

The post 5 Backup Practices to Protect Your Azure-Hosted Desktop appeared first on eWEEK.

Categories: Cloud Computing News

Assessing Behavioral Risk on the Network: 5 Key Techniques

eWeek Cloud Computing News - Tue, 03/22/2022 - 13:16

Security leaders are facing the perpetual challenge of keeping their threat detection capabilities on par with increasingly sophisticated malware. Unfortunately, traditional threat detection technology that uses malware signatures and rules no longer offers the most effective approach for protecting enterprises against modern malware.

While signature-based detection – which scans traffic for unique patterns of code that indicate malware, or the hash of a known bad file – is useful for catching unsophisticated malware, it doesn’t catch new or unknown threats for which no signature exists. Furthermore, attackers can also easily repackage malware so it won’t match known signatures.

A good example of this is the Cryptolocker ransomware, which was first discovered in 2013. Variants like CryptoWall and TorrentLocker use the same basic Cryptolocker code and are still common today. Signature-based threat detection platforms have other limits as well – they are notorious for false positives and for flooding security teams with more alerts than they can investigate.

Traditional threat detection is also unable to identify insider attacks carried out by employees or by an attacker who has obtained legitimate credentials through a phishing attack or data breach.

In response, many organizations are making the shift to behavioral risk analysis, which uses a completely different process, one that requires a great deal of input data to be effective. In this article, I’d like to dive deeper into how behavioral risk analysis helps overcome the challenges associated with traditional threat detection.

Also see: The Successful CISO: How to Build Stakeholder Trust

Shifting to Behavioral Risk Analysis

Behavioral risk analysis examines network activity for behavior that is both unusual and high-risk. This requires machine learning models that baseline normal network behavior and look for anomalies.

But not all unusual activities are risky. For example, consider a marketing employee accessing marketing materials from a SharePoint drive for the first time in several months. This is unusual compared to that person’s normal behavior, but likely relatively low risk. But that same employee accessing code repositories from an unfamiliar location in the middle of the night when most employees are offline is much riskier and should be flagged.

Conducting risk analysis involves determining the risk level of behaviors, which requires gathering a large amount of contextual data (usually into a data lake), calculating a risk score based on that data, looking at the anomaly in light of that risk score, and prioritizing it accordingly.

This helps to reduce false positives (behavior that is unusual, but low risk often triggers a false positive alert in less sophisticated solutions) and brings the security teams workload down to a more manageable level by helping them to prioritize. This contextual information is the key to identifying what behaviors are risky or not.

5 Techniques for Behavioral Risk Analysis

Behavioral risk analysis has several techniques. These include the following (please note that the details might vary based on the specific solution in question):

  1. Outlier modeling: Uses machine learning baselines and anomaly detection to identify unusual behavior, such as users accessing the network from unrecognized IP addresses, users downloading copious amounts of IP from sensitive document repositories not associated with their role, or server traffic from countries that the organization does not do business with.
  2. Threat modeling: Uses data from threat intelligence feeds and rule/policy violations to look for known malicious behavior. This can screen out unsophisticated malware quickly and easily.
  3. Access outlier modeling: Determines if a user is accessing something unusual or something they shouldn’t be. This requires pulling in data on user roles, access entitlements, and/or badging.
  4. Identity risk profile: Determines how risky the users involved in an incident are, based on HR data, watchlists or external risk indicators. For example, employees who were recently passed over for a promotion may be more likely to have a grudge against the company and want to retaliate.
  5. Data classification: Tags all the relevant data associated with an incident, like the events, network segments, assets or accounts involved, to give context to the security team investigating the alerts.

Also see: Secure Access Service Edge: Big Benefits, Big Challenges

Complex and Multi-Factored 

As you can see from these steps, estimating risk is complex and requires looking at many different factors. Behavioral risk analysis requires input data from a wide range of sources.

These sources include HR and identity data from Microsoft Active Directory or an IAM solution, logs from security solutions like firewalls, IDS/IPS, SIEM, DLP and endpoint management solutions, and data from the cloud, applications and databases.

Outside data sources such as public employee social media posts (to determine which employees are at a higher risk of being malicious) or threat feeds like VirusTotal are also useful. Due to the sheer amount of contextual data required, successful behavior analytics solutions need many third-party integrations and the ability to accept a wide range of data feeds into a database or data lake. The more data, the better.

When done successfully, behavioral risk analysis can improve efficiency, reduce false positives, and detect insider threats and zero-day attacks that other threat detection methods cannot. As a side benefit, the ML analysis involved can also produce valuable data on how systems and devices are used (for example, looking at the normal usage patterns for a system or a set of devices could let the IT team know the best time to shut it down for updates).

Behavioral risk analysis can also enable automated responses to threats. Modern malware can shut down dozens of systems in seconds. It’s not possible for human operators to respond fast enough to stop this.

Behavioral analytics, if done correctly, can produce alerts that are accurate enough for responses to be automated. The amount of context that this approach provides means that automated remediation actions can be extremely targeted, such as removing access to one system for one user. This means there’s a lower chance of accidentally interfering in legitimate business processes. In turn, this may help convince risk-adverse CIOs or CISOs that automated responses are feasible.

Behavioral risk analytics has great potential to make threat detection more efficient and keep organizations safer. Building robust ML analytics drawn from adequate input data will be key to the success of this approach over the next several years as this technology becomes more standard in security platforms (such as next-generation SIEM).

Also see: Tech Predictions for 2022: Cloud, Data, Cybersecurity, AI and More

About the Author:

Saryu Nayyar, CEO at Gurucul

The post Assessing Behavioral Risk on the Network: 5 Key Techniques appeared first on eWEEK.

Categories: Cloud Computing News

Data Security: 3 Things Most Organizations Overlook

eWeek Cloud Computing News - Tue, 03/22/2022 - 11:58

If you’re reading this, no doubt you take data security seriously. Your company might even have an industrial-strength firewall, rock-solid data governance rules, a professional security team, and a roster of data protections like encryption. You feel good about it. You sleep well at night.

But should you? Sorry to ruin your sleep here, but the truth is that most companies overlook three major data protection risks that can be the difference between kinda-sorta secure (maybe!) and virtually airtight.

Those three security challenges are untrusted computation programs, unvalidated input, and unauthorized data movement. Let’s break them down.

Also see: The Successful CISO: How to Build Stakeholder Trust

1) Untrusted Computation Programs

So, you’ve given people, teams, and companies access to your first-party data. Can somebody just come in and start processing it?

How do you know, whether they’re internal or external, that they’re using the program and algorithm that they said they were going to, and not something more risky? If you don’t have it registered, if you don’t have some proof that it’s the same one, you have no idea what’s really happening. It’s purely trust — and we live in a zero-trust world when it comes to data.

Every network, every device, every person and every service needs to be untrusted until it proves itself. What you need are zero trust technologies that are right for a zero-trust world.

What are these?  How do you know that somebody’s computer program, algorithm or analytic routine is safe? Zero trust technologies can validate with perfect confidence, such as with a “fingerprint,” that the agreed-upon code can be compared against code that is executing, in real time. (Failure to do this compromised the computers in the recent Ukraine cyberattack, by the way.) Otherwise, you can’t look your compliance team or your legal team in the eye and say, “Yes, I know — authoritatively! — that our data is always being used the right way.”

Also see: Secure Access Service Edge: Big Benefits, Big Challenges

 2) Unvalidated Input

When you’re dealing with first-party data (or any sensitive data) you need absolute certainty that only the data that you permit to be accessed is accessed.

There are some tools for that out there. For example, access control-based tools, whether on-premises or in Cloud-based warehouses like Snowflake, can help. But in many cases, even with the best legacy tools, you’re providing access to an entire dataset, not necessarily to just the data that you need. And the innovation that’s really required for safety in a big data world is to be able to constrain access to just certain data in a data set.

You need a validation technique that is absolutely reliable, not just initially, but all the way through the processing and use of the data — so you can understand not just how someone got it, but also what happened to it.

For example, what if one of your data scientists wants to try cross-indexing or sorting on another column? That might seem okay in a world where everyone has good intentions, but what if the data science guy or gal isn’t quite so benign? What if suddenly super sensitive data on social security numbers, credit cards numbers, race, gender, household income and sexual orientation are used deliberately (or inadvertently) for more nefarious purposes?

These are real things that happen and it’s critical that in a protection-first world you’re able to not just reduce the likelihood but eliminate the possibility of that ever happening.

Also see: Best Website Scanners 

3) Unauthorized Data Movement or Mining

Data scientists get creative with data sets all the time; it is part of the job description. But without the right controls in place, things get messy.

It’s like someone in financial services saying, “I’m just going to move this money to Dave’s account for a few days because I did something wrong and need to cover it. I promise I’ll move it back to Diana’s account later. She’ll never know.” That never works, and in today’s regulatory environment it creates opportunities for people to go to jail and for companies to get in hot water on CNN. And that fast and loose behavior happens all the time in data science when there are no controls in place.

What you need is an ability to control access for even informal calls and queries of data. It’s an extra step for the data analysts, but it’s also the protection that you need. It brings more discipline and arguably a better process and more accountability. If you are running a company, whether it’s in ad tech or another sector, you need to be able to address this issue definitively, consistently, and forever.

Also see: Top Data Mining Tools 

A Virtual Magic Bullet

The good news is that technology can solve all three of these problems. There are now ways to defuse these three security risks without disrupting your business — and still have your data uses grow. New technologies like machine learning can fingerprint computation programs.  Trust-enabling secure enclaves — also called “confidential compute” — can keep data processing safe.

And new controlling and processing surveillance technologies like digital contracts can extract the best of legal contracts and technical parameters, including the “fingerprint” of an algorithm, and make input validation and data movement extra secure by surveilling processing 24×7 and reporting anomalies — and stopping data use in real time.

Add the capability to provide audit quality data, and you are finally able to close the data risks and prove it to your lawyers and compliance overseers. Better yet, all of these eliminate the risks that come with putting your highly curated and highly secure data to work.

And then you can really sleep well at night.

Also see: Tech Predictions for 2022: Cloud, Data, Cybersecurity, AI and More

About the Author:

David Blaszkowsky is Head of Strategy and Development of Helios Data, and a former senior U.S. financial regulatory official and bank data executive. 

The post Data Security: 3 Things Most Organizations Overlook appeared first on eWEEK.

Categories: Cloud Computing News

Mitel Focuses on Cloud Partnership and Innovating at the Edge

eWeek Cloud Computing News - Mon, 03/21/2022 - 12:15

Communications and the cloud have seemingly become synonymous. The pandemic-induced trend toward working from home prompted companies to adopt “as a service,” or UCaaS, solutions for collaboration.

This created a massive wave of deployments, and some industry observers began to believe that the on-premises opportunity, which includes private cloud, will no longer be viable.

Also see: NTT Addresses the Why and When of Private 5G  Mitel Partners with RingCentral for UCaaS

While most vendors have put all their eggs in the UCaaS basket, one vendor that is innovating in both cloud and on-prem in UC is Mitel.

The company had been trying to dance on both sides of the line, but given the number of 800-pound gorillas in UCaaS, the company choose to partner with Gartner MQ leader RingCentral for those capabilities. Its goal is to drive more innovation into its on-prem products. Given that most of the “traditional” vendors have de-emphasized this part of the business, Mitel is unique in accelerating the pace of innovation here.

Most industry watchers, myself included, had been curious as to how the company will execute on this plan. Mitel recently held an industry analyst event to outline its go forward strategy.

During his opening keynote, CEO Tarun Loomba, explained this pivot in strategy: “With the market getting more competitive, focus is so important. It’s a big part of why we did the partnership with Ring – so we could focus on our core strengths while still making sure all customers are well cared for.” That’s certainly the right approach as, in business, it’s better to excel in one area than be mediocre in a few.

Mitel’s History of Innovation

Loomba continued, “The reality of the market is that millions of customers will have, want or need a modernized UC solution – and that will be the case for many years to come. We have the expertise and portfolio to serve those customers.”

An interesting fact about Mitel is that the company has been one of, if not the most, innovative vendors of the past few decades. It was the first to introduce a remote worker VPN phone, was the first “traditional” vendor to embrace the shift to IP, and was the first to partner with Microsoft in UC.

One of the more interesting innovations was when it introduced its solution for virtual machines. While most of the industry scoffed at this (in fact one vendor once told me that they would never run on a VM), Mitel pushed forward and embraced this concept. I recall seeing them appear at VMworld, long before the rest of the industry made the pivot. There were obviously bumps along the way, but now that capability is standard.

As part of his presentation, Loomba provided a look ahead as to where Mitel will be driving innovation. Much of the focus will be delivering hybrid and edge solutions. The definition of “cloud” is changing and moving away from centrally managed clouds to a more distributed model that encompasses private clouds and edge locations.

It’s a well-known fact that companies compete based on providing better customer and user experience, and edge computing moves the data closer to the user. Mitel was late to the cloud, but edge is an area in which they have an early mover advantage. Much of the general application and cloud computing industry has already embraced edge, but communications tend to adopt these types of shifts late, primarily due to the importance of technology.

Also see: Top Edge Companies 

On-Premises Communications: Still Alive and Kicking

Clearly, the on-premise world is still very important to businesses. The trends toward all communications moving to the cloud is nowhere near being a fait accompli.

The capital markets are echoing this as the valuation of the UCaaS and CCaaS (contact center as a service) vendors have been cut in half or more. The reality is that businesses are in the process of bringing people back to the office, at least on a part time basis. And this keeps the market for more of a traditional solution alive and kicking.

This is no different than other industries that were supposed to go “all cloud.” Sure, AWS and its peers sell a massive amount of cloud computing and storage. But Dell, HPE and others continue to sell huge volumes of systems that go into company-owned data centers. The key for the “on-prem” companies is to continue to drive innovation – and change pricing models to accommodate.

Similarly, in the communications space, not everything is moving to a SaaS delivered model. In fact, my estimate is that the total UC/UCaaS industry is still about two-thirds / one-third on-prem/private cloud, and the other third is SaaS delivered.

While the growth is in public cloud, the combined industry is massive, and these transitions take a long time. VoIP systems have been available for the better part of 30 years and there is still an TDM installed base.

Some people have asked me if there’s a day when all communications are delivered from a public cloud service. My answer is: perhaps, but that’s so far in the future that I’ll long be retired.

Also see: Tech Predictions for 2022: Cloud, Data, Cybersecurity, AI and More

Distributed Cloud Creates New Use Cases 

The distributed cloud model will have a profound impact on communications, particularly in voice and video as it moves those workloads much closer to the user, enabling several new capabilities. Video analytics, real time translation, facial recognition and artificial intelligence capabilities are just a few use cases. Communications data can also be combined with other information to enhance things like in-store analytics, sports and entertainment, and other use cases where speed matters.

This is a good move for Mitel as, in the words of the esteemed Wayne Gretzky, it’s important to skate to where the puck is going to be rather than where it is now. The UCaaS landscape is set and the partnership with RingCentral accomplishes two things. It gives Mitel a strong, viable options for its customers and it lets Mitel invest in edge and hybrid cloud, which is a market that is still in the making. This should help Mitel address its customers’ needs now and also position it for the future of cloud communications.

The post Mitel Focuses on Cloud Partnership and Innovating at the Edge appeared first on eWEEK.

Categories: Cloud Computing News

HPE’s Dan Griffith on Cloud Native Trends and Technologies

eWeek Cloud Computing News - Thu, 03/17/2022 - 15:36

I spoke with Dan Griffith, Director, Cloud Native Advisory & Solutions, HPE, about the nuts and bolts of cloud native technology. He also explained his views about the future of this emerging technology.

Among the topics we covered:

  • You’ve been a cloud professional about as long as cloud has been a serious concern in the enterprise – since about 2013, correct me if I’m wrong. What have you seen about cloud’s evolution that has surprised you?
  • Currently you’re focused on cloud native. It seems that even though it’s viewed as offering major advantages, companies are moving to it slowly. What’s your sense of companies’ attitudes toward cloud native?
  • What advice would you give to clients to optimize their cloud native deployment?
  • The future of cloud native? What should companies know? And how should they prepare?

Listen to the podcast:

Also available on Apple Podcasts

Watch the video:

The post HPE’s Dan Griffith on Cloud Native Trends and Technologies appeared first on eWEEK.

Categories: Cloud Computing News

Top 20 Kubernetes Best Practices

eWeek Cloud Computing News - Thu, 03/17/2022 - 15:15

Containers have emerged as the standard for cloud-native application development, and Kubernetes, also known as K8s, is arguably the most popular container orchestration tool. A survey from the Cloud Native Computing Foundation (CNCF) revealed that 91% of respondents use Kubernetes, 83% of them in production. That’s up from 78% the previous year.

However, popular isn’t the same as easy to use. Kubernetes is a complex system. Getting started with it entails a significant learning curve. While the following Kubernetes best practices and recommendations may not be applicable to your situation, those that are can help you get more out of Kubernetes – easier and faster.

Also see: Top Cloud Companies 20 Kubernetes Best Practices

1) Go with Vendor Hosting

Use external hosting to kickstart your Kubernetes deployment. Depending on the type of hosted service you choose, your team won’t have to deal with manually provisioning the control plane components, adding nodes to expand your cluster, or configuring the pods that support your containers. They also won’t have to implement role-based access control (RBAC) to secure your separate environments or instrument monitoring and logging for your cluster.

2) Use the Latest Version

Use the newest version of Kubernetes. In addition to updates and additional features, the latest release will have patches to previous version security issues. This is critical for mitigating many of the vulnerabilities that could affect your cluster. Older versions also don’t get as much support from the Kubernetes community.

3) Use a Version Control System

You should store configuration files related to your deployment, ingress, services, and other files in a version control system before pushing to a cluster. This helps you keep track of who made changes and implement a change approval process to improve your cluster’s stability and security.

4) Use Labels and Annotations

As the number of objects in your cluster grows, it gets more difficult to find and organize them. Labels ─ key/value structures assigned to objects ─ let you attach meaningful and relevant metadata to cluster objects so they can be categorized, found, and operated on in bulk.

You can use labels to determine whether a pod is part of a production or a canary deployment and whether it’s front-end or back-end. They can also specify which layer an object belongs to and its release version, as well as differentiate between stable and alpha releases.

5) Use Readiness and Liveness Probes

Readiness and liveness probes are essentially health checks. A readiness probe ensures a given pod is up and running before allowing the load to get directed to that pod. If the pod isn’t ready, requests are taken away from your service until the probe verifies the pod is up. A liveness probe verifies if the application is still running. It tries to ping the pod for a response and then check its health. If there’s no response, then the application isn’t running on the pod. The liveness probe launches a new pod and starts the application on it if the check fails.

6) Set Resource Requests and Limits

Resource requests specify the minimum resources a container can use, while resource limits specify the maximum resources.

Without resource requests and limits, pods in a cluster can use more resources than required. If the pod starts consuming more CPU or memory on the node, then the scheduler may not be able to place new pods. Even the node itself may crash.

For both requests and limits, it’s typical to define CPU in millicores. Memory is defined in megabytes or mebibytes.

7) Use Smaller Container Images

Base images can consist of up to 80% of packages and libraries that won’t be needed. Instead, use smaller container images such as alpine images which are 10 times smaller than base images. They require less storage space and will help you pull and build the image faster. Also, the smaller the container image, the less chance of security issues. You can then add any packages and libraries required to run your application.

8) Monitor Control Plane Components

Monitor workload and resource consumption and the performance of control plane components, including Kubernetes API, kubelet, etcd, controller-manager, kube-proxy, and kube-dns. This will identify issues/threats within the cluster and increase its latency.

You should also use automated monitoring tools rather than manually managing the alerts.

9) Use Autoscaling

Leverage autoscaling mechanisms in Kubernetes to automatically scale cluster services when there’s a surge in resource consumption.

Horizontal pod autoscaler automatically scales the number of pods in deployment, a replication controller, replica set, or stateful set based on perceived CPU utilization.

Vertical pod autoscaler recommends suitable values to be set for CPU and memory requests and limits. And it can automatically update the values.

Cluster autoscaler expands and shrinks the size of the pool of worker nodes. It adjusts the size of a Kubernetes cluster depending on the current utilization.

10) Adopt GitOps

Use GitOps, a Git-based workflow, as the preferred model for using Git as the single source of truth for all automation, including CI/CD pipelines. Using a GitOps framework can help improve productivity by speeding up application development and lowering deployment times. It can also enhance error traceability and automate CI/CD workflows.

11) Monitor Disk Usage

Because high-disk usage can affect cluster performance, you should regularly monitor all disk volumes associated with your cluster, as well as the root file system. With alert monitoring, you’ll be able to take corrective actions either by scaling or freeing disk space when needed.

12) Start with Stateless Applications

With a stateless backend, development teams can make sure there aren’t long-running connections that make scaling more challenging. Using stateless also enables developers to deploy applications more efficiently with zero downtime.

Stateless applications make it easier to migrate and scale as and when required according to business needs.

Also see: Top Edge Companies  Kubernetes Best Practices: Authorization and Authentication

13) Employ Role-based Access Control

To help enhance the security of your Kubernetes workloads, enable Kubernetes Role-Based Access Control (RBAC). RBAC is usually enabled by default on Kubernetes 1.6 and higher. Because Kubernetes combines authorization controllers, when you enable RBAC, you must also disable the legacy Attribute Based Access Control (ABAC).

Assign roles to each user in your cluster and each service account running in your cluster. Roles in RBAC contain several permissions that a user or service account can perform. You can assign the same role to multiple people and each role can have multiple permissions. RBAC settings can also be applied on namespaces. If you assign roles to a user allowed in one namespace, they will not have access to other namespaces in the cluster. Kubernetes provides RBAC properties such as role and cluster role to define security policies.

14) Use Third-Party Authentication for API Server

Integrate Kubernetes with a third-party authentication provider to take advantage of additional security features such as multi-factor authentication. Doing so also helps ensure that kube-apiserver doesn’t change when you add or remove users. Make sure users aren’t managed at the API server level if possible.

Also see: DevOps, Low-Code and RPA:  Pros and Cons 

Kubernetes Best Practices: Security Issues

15) Use Network Policies

Use network policies to restrict access to services within a Kubernetes cluster. They can also restrict access to your cloud’s metadata API from pods in the cluster, and control traffic flow at the IP address or port level.

You’ll find information on setting up a network policy in the Kubernetes documentation.

16) Don’t Run as Root

The UID (the Kubernetes systems-generated string that uniquely identifies objects) of the user running a container maps directly to the host. If the container runs as UID 0 (root), it will also appear as root on the node it’s running on.

Kubernetes has built-in protections to prevent escalation of privileges with this mechanism, However, there’s always a chance that security issues could allow for escalating privileges. Avoid the situation by not running run your containers as root. Instead, modify the Dockerfile for your built containers to create and use a user with a known UID.

17) Create a Firewall

Create a firewall for your API server to prevent attackers from sending connection requests to your API server from the internet. You can use regular firewalling rules or port firewalling rules. If you are using something like GKE, you can use a master authorized network feature to limit the IP addresses that can access the API server.

18) Restrict API Access

Most cloud implementations for Kubernetes already restrict access to the Kubernetes API for your cluster by using RBAC, Identity & Access Management (IAM), or Active Directory (AD). If your cluster doesn’t use these methods, set them up using open source projects for interacting with various authentication methods.

19) Restrict SSH Access

Another important security measure is to restrict SSH access to your Kubernetes nodes. You typically wouldn’t have port 22 open on any node but may need it to debug issues at some point. Configure your nodes via your cloud provider to block access to port 22 except via your organization’s VPN or a bastion host. You’ll be able to quickly get SSH access but outside attackers won’t.

20) Audit Policy Logs

Regularly audit all logs stored at /var/log/audit.log to identify threats, monitor resource consumption, and capture key event heartbeats of the Kubernetes cluster. The Kubernetes cluster default policies are defined in the /etc/kubernetes/audit-policy.yaml file. You can customize them for specific requirements. You can also use Fluentd, an open-source tool, to maintain a centralized logging layer for your containers.

Also see: How Database Virtualization Helps Migrate a Data Warehouse to the Cloud

Kubernetes Best Practices: Constant Learning Required

These Kubernetes best practices are just some of the many that are available to help make Kubernetes an easier and more valuable system to use in application development. Nonetheless, there’s still a lot to learn to use Kubernetes effectively.

That can be overwhelming for development teams already bogged down with the many tasks required in modern application development ─ even with the ever-growing number of tools and services to accelerate the processes entailed. But by starting with these tips, you’ll be well on the way toward advancing your complex application development projects using Kubernetes.

Also see: Tech Predictions for 2022: Cloud, Data, Cybersecurity, AI and More

About the author:

Alexander Ivenin is a System Technical Lead at ClearScale.

The post Top 20 Kubernetes Best Practices appeared first on eWEEK.

Categories: Cloud Computing News

Lenovo Introduces Infrastructure Solutions for Midsize Businesses

eWeek Cloud Computing News - Thu, 03/17/2022 - 15:08

Business computing hardware launches are usually pretty straightforward. After considering markets, talking with customers and partners, and analyzing component characteristics, vendors develop and launch new products with features they believe will address specific business opportunities.

However, you can observe this process from another viewpoint: where new solutions reflect how a vendor perceives or understands its commercial customers.

That is an issue worth considering in terms of the new ThinkSystem V2 solutions Lenovo recently announced for midsize companies.

Opportunities and Challenges for Midsize Businesses

Like most system vendors, Lenovo has a strong interest in and focus on enterprise computing. After all, large organizations’ sizable and complex IT requirements typically translate into significant orders and long-term sales and service relationships. But as a group, midsize companies represent a substantial opportunity in nearly every global market.

As Lenovo noted in its announcement, midsize businesses make up the majority of the world economy and workforce. Plus, those companies tend to grow more quickly and dynamically than large enterprises, often with the assistance of robust compute solutions and services. As a result, IDC’s prediction that 70 percent of midsize businesses will increase their IT spend by 2026 should come as no surprise.

Why so? Because technology-led transformation can help companies enhance or accelerate key business tasks and processes, adapt to market shifts and meet vital challenges, like the continuing growth in cybercrime, security breaches and ransomware attacks. However, midsize organizations also face significant barriers in achieving those benefits, particularly in terms of finding, hiring and retaining IT staff and managers with the skills needed for technology-led business transformation.

Also see: What is Edge Computing

Lenovo’s New ThinkSystem and TruScale solutions

What is Lenovo doing to help midsize customers address these issues? The company is rolling out a trio of new single-socket ThinkSystem V2 servers, along with storage and service offerings. The new solutions include:

  • ThinkSystem ST50 V2: A compact, performance-optimized tower solution designed for growing businesses, remote/branch offices, and small/home offices. The ST50 V2 includes Intel Xeon E-2300 processor with up to 8 cores at 95W, up to 64GB TruDDR4 memory at 3200MHz (planned support for up to 128GB), 2x 3.5-inch SSD/HDD bays, 1x 2.5” SDD bay, 1x NVMe M.2 SSD Module, 1x optical drive bay. Support for the NVIDIA Quadro RTX T1000 GPU is also available.
  • ThinkSystem SR250 V2: A single-socket 1U rack server for growing businesses that require power, reliability and flexibility for space constrained installations. The SR250 V2 includes Intel Xeon E-2300 processor up to 8 cores at 95W and up to 128GB TruDDR4 memory at 3200MHz. Flexible storage options include either 10x 2.5-inch hot-swap drive bays, or 4x 3.5-inch hot-swap or simple-swap drive bays, and simple-swap drive configuration supports an NVMe drive for tiered storage. Data protection provided by hardware RAID adapters. Support for the NVIDIA Quadro RTX T1000 GPU is also available.
  • ThinkSystem ST250 V2: Designed for growing businesses looking for enterprise-level power in an easily-managed tower form factor. The ST250 V2 includes Intel Xeon E-2300 processor, up to 8 cores at 95W and up to 128GB TruDDR4 memory at 3200MHz. Enterprise storage options support up to 16x 2.5-inch hot-swap or 8x 3.5-inch hot-swap and simple-swap drive bays. Simple-swap drive configuration includes support for an NVMe drive for tiered storage, and support is available for an optical drive and an RDX backup unit in media bays. Data center data protection provided by hardware RAID adapters. Support for the NVIDIA A2000 or Quadro RTX T1000 GPUs is also available.

Both the SR250 V2 and ST250 V2 include integrated systems management with Lenovo XClarity while the ST50 V2 offers optional Lenovo XClarity Provisioning Manager Lite (USB version). Lenovo noted that the ThinkSystem DM5100F storage system, an all-flash SAN solution, can help companies start small and grow, adapting to new workloads over time and allowing them to manage data from the network edge to the cloud. The company also offers DM storage systems with built-in ransomware protection, as well as ThinkShield Security solutions for the new ThinkSystem V2 servers.

The new solutions are available as Lenovo’s TruScale Infrastructure Services offerings. Plus, the company hopes that midsize companies facing the challenges of enabling and supporting remote workers, including those at remote and branch offices (ROBOs), will consider the Lenovo TruScale for Hosted Desktops solution. Finally, Lenovo noted that midsize companies could benefit from its Professional Services Tokens, which can be purchased in hourly increments and used for IT services consulting and support.

Also see: How Database Virtualization Helps Migrate a Data Warehouse to the Cloud

Final Analysis

Returning to my first point, what do the new ThinkSystem V2 servers and associated solutions say about how Lenovo perceives or understands midsize customers and prospects? First and foremost, the company understands the remarkable size, scope and variety of midsize businesses. There are nothing like “one size fits all” IT solutions for these organizations.

Instead, their computing requirements vary wildly according to the industries, markets and regions where they do business. So, while the new ThinkSystem V2 servers single socket design may seem modest, their highly scalable features make Lenovo’s solutions both appropriate for a wide range of commercial applications and industry use cases.

Just as important are Lenovo’s included and optional services and functions, including its XClarity systems management offerings and ThinkShield security features. While cyberthreats may be top of mind in the daily news, actual dangers vary widely for individual businesses, including midsize companies.

Flexibility is also apparent in Lenovo’s TruScale Services, which can be implemented according to customers’ needs and designed to address existing or potential IT staffing issues.

Overall, the adaptability and scalability of the new ThinkSystem V2 servers and associated solutions reflects Lenovo’s clear understanding of and appreciation for the midsize companies that will employ them.

Also see: Tech Predictions for 2022: Cloud, Data, Cybersecurity, AI and More

The post Lenovo Introduces Infrastructure Solutions for Midsize Businesses appeared first on eWEEK.

Categories: Cloud Computing News

What is Data Mesh

eWeek Cloud Computing News - Tue, 03/15/2022 - 15:50

A data mesh is a decentralized approach to data management, in which the data itself remains within the business domain that has collected it. Yet data mesh technology enables this data to be available to qualified users in disparate locations, without needing to move or otherwise download the data from its current location.

Data mesh is clearly not a silo. Indeed, it is central to digital transformation’s effort to distribute data widely. The SQL clients from the entire organization can query it, with a distributed query engine. And on top of this privately-owned coherent business data sits the distributed query engine, which can access and unify it for interoperability, rather than storing it centrally.

In other words, a data mesh democratizes the data. It creates “datasets as a product,” a standardized offering, available for anyone with permission. It’s secure, in compliance with local regulations, and suddenly considerably more scalable.

In short, with data mesh architecture, the business domain user rises to the top of the priority list. This empowers them to own the decisions about what data can and cannot be, freeing them from the costly infrastructure constraints that blocks the organization from accessing the accumulated wisdom of all its data.

Also see: Digital Transformation Guide: Definition, Types & Strategy

The Potential and Challenges of Data Mesh 

Here’s a prediction: by 2025, those of us who live in the ever-churning world of data aggregation, transportation, ETL, storage, business intelligence, and accessibility will look at data mesh much as we look at cloud computing today. It’s a strategy that simultaneously shrunk overhead (time and money), reduced grunt work (maintenance, upgrades, backups), and provided end-user abilities that didn’t exist before.

In short, data mesh is a tech evolution whose technical and business advantages make it both obvious and inevitable. What challenges does this evolving paradigm aim to solve?

Also see: Data Mining Techniques 

Too Much Data from Too Many Sources

The tsunami of data pouring in as businesses embrace full digital transformation is staggering. Data points flow in dynamically, on a global level, at a level of granularity never before contemplated.

And while historical financial/operational data has always been used as an analytical tool to drive business decisions by management, we’re now seeing BI providing game-changing insights driven by always-on transactional data for the marketing, sales, and product development teams as well. These customer-facing teams can finally instantly know what’s working and what’s not, based on every single action taken by customers.

It’s an extraordinary power to have, but the amount of data they have to work with is hard to collect, store, query, and manage.

Also see: Data Analytics Trends 

Data Lakes

Nobody will argue that siloed data is a good thing; hundreds of startup companies have emerged, offering solutions to break open those silos. But while the goal over the past decade has been the unification of data sources into a single repository to yield a “single source of truth,” that repository suddenly – amazingly – feels like yesterday’s strategy. Why? Because it introduces several limitations while that immense single source swells day by day.

A data mesh helps address this by lessening the closed off quality of a silo. A data mesh helps data become available to experts throughout the organization.

Large-Scale Enterprise Data Management 

Clearly, large-scale enterprise data management is messy. In particular, it’s a challenge to integrate live, flowing data into static or historical data.

Data transitioning in and out of the data lake from edge sources – and managing its storage once it arrives – is time and resource consuming and very expensive. The bottlenecks get more frequent, and business agility declines.

A single, aggregated collection of data cannot easily comply with data residency and privacy regulation compliance that varies from country to country; data governance is geographically diverse, whereas the hardware is not.

Finally – and often the most painful feature of a bloated data lake – is the reality that query overhead doesn’t scale. As more and more users need to query the same database, add sources, or manipulate what’s there, response times slow. This assumes, of course, that the data lake incorporates true data virtualization to seamlessly allow anyone with permission to connect to any data source or platform, an important concern according to our recent survey.

In short, putting all your eggs in one basket has some appeal, but that’s going to be one heavy basket that’s hard to carry … or to locate the right egg. Enter the data mesh. It maintain the benefits of a centralized, standardized data lake while introducing scalability and access that currently. You can think of it as a “distributed data lake.”

Also see: Best Data Analytics Tools 

Data Mesh and Empowering People

A data mesh offers automated, comprehensive, instant analytics at scale. Data scientists – and data consumers with less expertise and training – will now be able to access business data, to conduct their own analysis focused on their own business needs.

This self-service strategy, with its single point of access control, represents for the first time a people-centric plan for data management; a faster and more effective way to get answers without taxing the DevOps team, hoping for their availability.

Zhamak Dehghani, Director of Emerging Technologies at Thoughtworks, who is credited with creating this paradigm in 2019 at an O’Reilly conference (she named it later, when she literally wrote the book on the subject), refers to it as a hybrid: “a decentralized sociotechnical approach — concerned with organizational design and technical architecture.”

Access Drives Insights

The data mesh is also, in a sense, the next phase in the “anyone/anywhere” model that we’ve come to expect from cloud computing and data virtualization.

A business domain’s own applications and access tools are usually designed for its own users and their specific needs. And in an ideal situation, its data is local, so latency is minimal.

But if members of one business unit seek data from another, they are limited by their own frameworks. If they do gain access to that centralized data lake, its remote location (and size, most of which isn’t the business unit’s own data) increases latency.

With a data mesh, it is easier than ever to have systems interact, share their on-site data, and make the results available to a diverse group of business users. These may be completely independent teams (say, HR and R&D) or cross-functional teams with the same goals and often the same data (QA working with Product Management, or Sales working with Marketing). This new effortless transparency promises new levels of productivity.

Also see: Top Business Intelligence Software  The Three ‘Flavors’ of Data Mesh

As this approach takes hold, keep an eye out for three “flavors” of data mesh. Most companies will use a combination of these:

  • File-based: The data is compiled, packaged, and simply provided as a static file. This is the closest to today’s simple cloud-storage approach, but will exist under the new universal peer-to-peer sharing model.
  • Event-driven: No matter what business unit or department, consumers can “sign up” for alerts when data changes in a way that may be meaningful to them. Again, this isn’t rocket science, but it’s only available once this previously siloed data is exposed and accessible across the organization.
  • Query-enabled: Clearly the most powerful flavor, any user can submit federated queries spanning multiple databases, creating insights only possible when combining results. This is the Holy Grail that gives end-users new capabilities, and data scientists some stored up vacation time.

Be aware that the data mesh isn’t entirely about the corporate business employee. The end user is going to feel the speed of a response when the data is coming from an optimized, dedicated, distributed source, rather than a massive, multi-purpose one. In return, the clickstream and web data these users provide along the way can be instantly absorbed and processed as a pure feedback loop to improve performance, product features, and ultimately, profits.

Also see: Top Digital Transformation Companies

Empowering Data Democratization

While widespread implementation and adoption aren’t going to happen overnight, many organizations are embracing data mesh architecture to democratize and scale their data.

This move puts responsibility on data teams to become truly autonomous: they will need to ingest and clean data themselves, create ETL pipelines (and maintain them), and manage access control. At the same time, the more they invest in these fully-owned steps, the better results they can expect. And yes, that means a new “warm and fuzzy” era of mutually beneficial sharing as each domain helps the others by simply transforming and offering their data to their community.

I’ll close with a parting thought from Dehghani, as she describes the overarching value of distributed data mesh architecture, with domain-owned data under a centralized access system: “Over the last decades, the technologies that have exceeded in their operational scale have one thing in common: they have minimized the need for coordination and synchronization.”

About the Author:

Ori Reshef is the VP of Products at Varada.

The post What is Data Mesh appeared first on eWEEK.

Categories: Cloud Computing News

Juniper Brings Intent-Based Networking to the Edge

eWeek Cloud Computing News - Tue, 03/15/2022 - 09:53

Many predicted that the cloud would be the death knell for data centers. The use of public cloud services would make data centers obsolete – but that never came true.

In fact, the data center has never been more important. The enterprise is going through a data center Renaissance, where everything is moving to some kind of data center – whether it’s in a centralized public cloud, private cloud or edge location.

Also see: Top Edge Companies 

Data Center Demand is Growing

As people continue to work from home and consume more applications/services in a distributed way, there will be even greater demand for data centers. To help explain why that’s the case, I recently spoke with Michael Bushong, Vice President of Cloud-Ready Data Center at Juniper Networks. Highlights of my ZKast interview, done in conjunction with eWEEK eSPEAKS, are below.

Also see: Top Cloud Companies

  • A divergence is taking place. Organizations are moving to hybrid environments that combine on-prem, software as a service (SaaS) workloads, and the cloud. According to ZK Research data, 95 percent of enterprises plan to adopt hybrid cloud. Specifically, larger enterprises prefer this model since they have complex workflows, data sovereignty issues, and regulatory requirements that prevent them from moving everything to the public cloud.
  • As a result, the data center has evolved beyond the four walls of the enterprise. It has become more about operations, extending to different areas in the network. Many organizations hadn’t really moved to true cloud operations. There is now a shift toward true multicloud—meaning one operational construct across all the clouds, not just multiple centralized clouds.
  • Another major disruptor in data centers is the edge, which gave rise to the distributed cloud. This model spans public clouds, private clouds, and edge locations in distributed environments, changing the role of the network and data centers. Distributed edge offers cloud-like operations, so organizations can preserve a consistent user experience when deploying apps across different locations and connectivity modes.
  • Historically, the cloud served as a central location for hosting users, data, and apps. The distributed edge is changing that by taking apps/data and bringing it closer to the users. It’s no longer sufficient to just route everything through data centers. Instead, data centers must be pushed closer to the users.
  • In 2020, Juniper acquired intent-based networking (IBN) software provider Apstra, in an effort to help enterprises automate data center operations. Through the acquisition, Juniper gained the IBN software, intent-based analytics (IBA), and the Apstra Operating System (AOS). Apstra is the only IBN provider with multi-vendor solutions. It helps organizations avoid vendor lock-in by deploying services, apps, and devices in existing data centers regardless of the providers.
  • Juniper recently made several announcements, extending Apstra’s intent-based networking to new deployments at the edge. Juniper is exploring use cases like Internet of Things (IoT), smaller data centers, and telco cloud—where carriers are distributing their data centers out in support of 5G services.
  • Enterprises often have many apps all running in different data centers, supported by various vendors. The latest Apstra software release features group based policy (GBP), which enables micro and macro segmentation of data. GBP allows organization to fix problems quickly, rather than finding out that their policies are not working as intended in the middle of a serious security incident like a ransomware attack.
  • Having a network that’s up and running is not a sufficient measure of success. User experience is the new uptime, especially with hybrid work putting additional strain on the network. That’s why Juniper introduced experience-first networking across wired, wireless, and software-defined wide area (SD-WAN) networks. Juniper is leveraging Apstra to provide organizations with visibility of every user, every device, and every app.

Also see: Tech Predictions for 2022: Cloud, Data, Cybersecurity, AI and More

The post Juniper Brings Intent-Based Networking to the Edge appeared first on eWEEK.

Categories: Cloud Computing News

Red Hat CEO Paul Cormier: Open Source Drives the Cloud and Edge

eWeek Cloud Computing News - Mon, 03/14/2022 - 17:20

I spoke with Paul Cormier, CEO of Red Hat, about how open source’s innovation enables edge computing, and why hybrid cloud is now the operative model going forward.

Among the topics we discussed:

  • Linux has had a remarkable growth curve. Red Hat went public in 1999, and certainly there was enterprise resistance in those early years. Yet I just read an analyst forecast of $60 billion in open source revenue in the years ahead. Why has open source seen such a rapid growth curve?
  • Clearly Edge computing is also on a rapid growth pace in 2022. You’ve mentioned that Edge computing won’t happen without hybrid cloud and open source. Why is this?
  • Given how close you are to the cloud market, what do you see as a key challenge facing today’s cloud customers? Any advice you’d give to companies?
  • If you look to the future of the enterprise IT market – which is so full of competing market forces – are there a couple of trends that you think will shape tech? How can companies prepare now?

Listen to the podcast:

Also available on Apple Podcasts

Watch the video:

The post Red Hat CEO Paul Cormier: Open Source Drives the Cloud and Edge appeared first on eWEEK.

Categories: Cloud Computing News
Syndicate content