The Good lawsuit

 

Image

 

Sometimes I rant about how much I hate Airwatch, they hire kids that are 21 or 22 years old, they under pay their employees, they put features in the product just to check something off for the Gartner report. ( I still feel that way sometimes)  However, this is a really weak lawsuit.  I dislike when technology companies attempt to patten an idea.  That is basically what Good is trying to do here. 

Nowhere in any of Airwatche’s code will you find anything, that even remotely resembles Good code.  Good is suing over the belief that Airwatch (and Mobile Iron for that matter) stole the idea from them (and did it better then they did).  This is such a ridiculous concept in technology and all it does is hurt innovation.  I don’t care if Good thought up this MDM game 10 years ago, Androids and iPhones didn’t even exist back then. There is no argument for attempting to say that your patten, that applied to some old WinMO devices and Symbian devices, is valid today in the technology diverse systems that we are working in.  Just think about this for a second, if this nonsensical patten crap existed 100 years ago, people would of been afraid to invent anything.

SaaS versus On-Premise solutions

Image

So recently I had my galbladder out, so I didn’t have as much time to write, or work for that matter.  I came back to my job to see that I had close to 4000 emails.  Err…  I can assure you that this is a very fun process of going through e-mails…or not.  What I wanted to talk about today is  what most people in the MDM space have seen happening over the past few years.  When setting up MDM/ or any application or service that can go in the cloud, you are going to have to deal with a decision.  Do we want it behind our firewall, or do you want it out in the cloud.  Do we want it here, or do we want to use a SaaS (Software as a service) or a  connector to get to that machine.  I am going to attempt to explain the differences here.  Now Obviously I assume you are going to have a whole team of network engineers, software engineers and really smart people who have put much more thought into this then you, this is just some basics.

 

On-Premise

The general concept behind on-premise is that you want to have control of the system.  You want to be able to patch it, you want to have it on your hardware, you do not want someone to have control over its SLA’s (service delivery times) In other words You want to control the success of it.

 

Hosted/SaaS/Cloud

In this situation, you use some sort of VPN or connector to connect your corporate environment out to a cloud solution.  In this case, you are saying that you do not want to have to deal with patching this, dealing with its up time, the only part of the equation that you are responsible for is the connection via the VPN or SaaS.