Skip to main content

Posts

Showing posts from 2020

The Pandemic and the Security Paradox

  Ten years ago, I wrote a post titled: Cloud Computing and the Security Paradox . In this ancient post I argued that the claim of insufficient Security of the Public Clouds systems is based on a perception that what is not controlled by the Enterprise within its Data Center is less secured. However, Public Clouds Security was better than assumed  based on our perception.  Sometimes it was better than the Security of Data and Systems located within the Enterprise's Data center.  The COVID-10 magnified the Security Risks and the Public Clouds are more Secured than many Private systems. The enhanced Threats landscape   The COVID-19 Pandemic restrictions changed dramatically the way people collaborate and interact. The Security measures, Procedures, Policies and tools should be adapted to the new  interaction  style. Adaptation is a continuos Process therefore the vulnerability is higher than before COVID-19.  Main reasons for the higher vulnerabilit...

IBM Mainframe in splitted IBM at 2022

The topic of the post Vendors Survival: Will IBM Survive until 2030? is no longer a question to be asked , is  IBM's plans to split into two companies.   The new IBM will focus on Hybrid Clouds and one of its goals is rapid growth. The smaller "new Co" will address Infrastructure and IT Services issues. Its goal will be efficiency. It will include other products and Business Lines. Some of the low margin products and Platforms will gradually disappear or will be sold to other companies. These products and platforms may be part of "New Co" at 2022. I promised to de dicate a post to the IBM Mainframe. This post is the promised post.  The Mainframe's Positioning It is likely that it will be part of the "New Co".  The term "Modernization" appears in s ome non-official descriptions describing " New Co".  Modernization refers frequently to  Silo   Legacy Mainframe systems. The idea is to build componentized integrated systems which a...

Vendors Survival: Will IBM Survive until 2030? is no longer a question to be asked

IBM's headquarter in Armonk, New York Source: Wikipedia I wrote   the first post on IBM's Survival on 2017. Issues appearing in the post were not resolved yet by IBM.  To quote my post " The problem is that IBM does not lead any significant new technologies market ." The market that IBM should be one of the Leaders is the Public Cloud market. Unfortunately for IBM, it failed to lead this market. On 2018 I wrote another post:  First Take: IBM's Red Hat Acquisition: Is it too late?   IBM's position was even worse than in 2017.  "Is it too late?" refers to the Cloud market. Like HP, few years ago , IBM plans to split its business into two companies at the end of 2021.  IBM (currently 59 billion revenues until June 30 2020) will focus on Hybrid Clouds.  "New CO" (currently 19 billion revenues) will focus on infrastructure services.  the new IBM The new IBM will focus on Public Hybrid Clouds. Mainly integrating clouds of Amazon's AWS and ...

Vendors Survival: Will Google Survive until 2030?

Sundar Pichai Picture Source: Wikipedia The previous post raised a technical issue reflecting a problem in Google's Blogspot.  After I fixed the problem, I still get the error message: Earnings at risk - You need to fix some ads.txt file issues to avoid severe impact to your revenue. FIX NOW LEARN MORE The other message  " It may take a few days for changes to update."    still appearing ten days after. "Few days" according to Google is at least ten days. The problem I depicted in the previous post is a minor problem in comparison to other problems Google should address.   That is why I am asking the question: Will Google Survive until 2030? I already asked few times the question: Will Google Survive for ten years? I askes it in 2008 , 2011 and 2011 - Revisited .  As far as Google's Survival is concerned, I am less optimistic than I was few years ago. Current Problems Employees' Dissatisfaction The indic...

Google in trouble: Root Level Domain or Root Cause Analysis?

    Google's headquarters, the  Googleplex   Picture Source: Wikipedia What is Root Level Domain and what is Root Cause Analysis? It is easy to define   Root Cause Analysis (RCA). For example, you can read an article on it in the English Wikipedia.  In the context of Risk Management, RCA is a Risk Identification and Risk Assessment technique. Root    Level Domain  is not well defined in the context of Google's Blog spot.  Therefore the answer to the question in this post's title is:  Root Cause Analysis. Google is in a risk. The next post in this blog will be titled: Vendors Survival: will Google Survive until 2030?   Google and The Devil  The proverb "the Devil is hidden in the details" is applicable to Google's advertisement in Blogger's blogs: A good  new   idea but poor design and very poor execution . This is a small indicator showing that Google is not the same Google of 10...