Wednesday, July 29, 2015

005 Secure your devices - Here is how I do it

Secure your devices
Here is how I do it.
All Clouds Considered is brought to you by Cloud Genius®
Cloud Genius is a top 10 rated institution built by industry experts focused on helping businesses succeed with the cloud and helping you transform your professional career.

Take a test drive at https://be.a.cloudgeni.us

Podcast transcript coming soon.


Join our discussion in the Cloud Genius community and chat with us on our chat channel where we hangout and learn from each other.

 


 

Want us to create an episode on a topic of your interest? Let us know and we gladly develop one. I am your host Nilesh. Look forward to seeing you online.




005 Secure your devices - Here is how I do it

Tuesday, July 21, 2015

004 The power of open source

Your cloud services provider shuts down the service...
 

but there is no real reason to worry if your business is build on open source foundations.
All Clouds Considered is brought to you by Cloud Genius®
Cloud Genius is a top 10 rated institution built by industry experts focused on helping businesses succeed with the cloud and helping you transform your professional career.

Take a test drive at https://be.a.cloudgeni.us

Since the last episode, when I mentioned we use Mitro as a service, the creators of mitro have decided to shut that service down. What does that mean, is that Mitro as a service is not going to be available.


But you know what that does not really matter. Here is why. Mitro is available as an open source product, which means the source code is available in a git repository.


So you can just go there and build your own back end solution using a cloud machine somewhere and deploy the source code available here. So you can basically go to Mitro’s source code, grab that source code here and run this mitro core application on a back end solution somewhere in the cloud, where you would deploy Java JDK and then build it up.


After doing that, the next step would be grab the browser extensions from this location and then install the dependencies needed such as node js and node package manager and then build out your extensions for browsers. and then your are done.


So the beauty here is, of using open source products even if the creators decide to shutdown the service, is that open source liberates you. Even if the creators decide to shut down the service, you can still run your own service based on your own cloud infrastructure based and the source code they have offered to the community.


That is the power of open source.


Join our discussion in the Cloud Genius community and chat with us on our chat channel where we hangout and learn from each other.

 


 

Want us to create an episode on a topic of your interest? Let us know and we gladly develop one. I am your host Nilesh. Look forward to seeing you online.




004 The power of open source

004 The power of open source

Your cloud services provider shuts down the service...
 

but there is no real reason to worry if your business is build on open source foundations.
All Clouds Considered is brought to you by Cloud Genius®
Cloud Genius is a top 10 rated institution built by industry experts focused on helping businesses succeed with the cloud and helping you transform your professional career.

Take a test drive at https://be.a.cloudgeni.us

Since the last episode, when I mentioned we use Mitro as a service, the creators of mitro have decided to shut that service down. What does that mean, is that Mitro as a service is not going to be available.


But you know what that does not really matter. Here is why. Mitro is available as an open source product, which means the source code is available in a git repository.


So you can just go there and build your own back end solution using a cloud machine somewhere and deploy the source code available here. So you can basically go to Mitro’s source code, grab that source code here and run this mitro core application on a back end solution somewhere in the cloud, where you would deploy Java JDK and then build it up.


After doing that, the next step would be grab the browser extensions from this location and then install the dependencies needed such as node js and node package manager and then build out your extensions for browsers. and then your are done.


So the beauty here is, of using open source products even if the creators decide to shutdown the service, is that open source liberates you. Even if the creators decide to shut down the service, you can still run your own service based on your own cloud infrastructure based and the source code they have offered to the community.


That is the power of open source.


Join our discussion in the Cloud Genius community and chat with us on our chat channel where we hangout and learn from each other.

 


 

Want us to create an episode on a topic of your interest? Let us know and we gladly develop one. I am your host Nilesh. Look forward to seeing you online.




004 The power of open source

Monday, July 20, 2015

003 Do you remember passwords?

Securing access to online banking, email and other cloud services is critical but do you remember your passwords?
 

I think you should not. Why do I say that? Take a listen…
All Clouds Considered is brought to you by Cloud Genius®
Cloud Genius is a top 10 rated institution built by industry experts focused on helping businesses succeed with the cloud and helping you transform your professional career.

Take a test drive at https://be.a.cloudgeni.us

If you can remember most of your passwords, you are either a superhuman or you are doing this password thing wrong. A password that someone can typically remember is not secure enough.


Automatic password management


You have probably heard of security breaches at Snapchat, Target, Adobe, Drupal, Last.fm, Samsung, Apple, Lastpass, in the last few months. With cloud security being an issue of prime importance, how do you choose a password that you can make sure won’t cause you too much damage if it gets compromised? Many people use the same password (or its derivative) for every website or service they use. However, you can probably see a problem with that. If one account were to be compromised, all of the other accounts are in danger as well. One technique to solve this issue is to create a unique password for every service you use. But now, this leads to a bigger problem. How would you remember so many different passwords or how would you save them somewhere in a secure manner?


One solution to this problem that I like and use is Mitro. I use Mitro because it is an open source product. There are several other solutions available: 1Password, CommonKey, Dashlane, KeePass, Keeper Password Manager, LastPass, Meldium, Password Genie, Password Safe, RoboForm, Team Password Manager are just some examples.


Mitro will generate a random password for each cloud service that you use and will encrypt and save these all locally. All you have to do is remember just one password for Mitro and Mitro will log you in to any account that you have used Mitro with. Mitro has browser plugins for most browsers and is a simple and efficient solution to the problem of creating secure passwords.


I recommend that you try Mitro. For our corporate clients, I recommended SAML based Single Sign-on onto some centralized directory service and then login to other cloud services from there.


Password alone is not enough – You need additional layer of protection


A common technique most modern services provide is to use 2 step verification (also known as 2 factor authentication or 2FA). Think of it as a pin code (aka a token or a one time password) that you would provide on top of your password. 2FA is a bit more secure because the only way to log into an account is through providing a one time password that changes when you need to log in next.


There are several tools available that can generate this one time password for you:


  • Google Authenticator app on your phone generates one-time password which you must provide after you use your password when logging onto cloud services that are google authenticator enabled.

  • Yubi Key is another interesting technology which is available a small USB device that you plug into your computer. Every time you need to log into an account, you simple touch the USB device and it acts as a token for you to log in.

  • Don’t like to use these? Some services may allow you to opt-in to receive a one time passcode in your TXT/SMS or delivered to via a phone call.

You can secure Mitro as well with 2FA. Mitro can also help you securely share passwords among your team members as needed.


Push yourself towards using 2 factor authentication. Push your business to adopt single sign-on technologies. These techniques will make the cloud a better place for you.


What techniques do you currently use to secure access to critical services?


Join our discussion in the Cloud Genius community and chat with us on our chat channel where we hangout and learn from each other.

 


 

Want us to create an episode on a topic of your interest? Let us know and we gladly develop one. I am your host Nilesh. Look forward to seeing you online.




003 Do you remember passwords?

Thursday, July 16, 2015

003 Do you remember passwords?

Securing access to online banking, email and other cloud services is critical but do you remember your passwords?
 

I think you should not. Why do I say that? Take a listen…
All Clouds Considered is brought to you by Cloud Genius®
Cloud Genius is a top 10 rated institution built by industry experts focused on helping businesses succeed with the cloud and helping you transform your professional career.

Take a test drive at https://be.a.cloudgeni.us

If you can remember most of your passwords, you are either a superhuman or you are doing this password thing wrong. A password that someone can typically remember is not secure enough.


Automatic password management


You have probably heard of security breaches at Snapchat, Target, Adobe, Drupal, Last.fm, Samsung, Apple, Lastpass, in the last few months. With cloud security being an issue of prime importance, how do you choose a password that you can make sure won’t cause you too much damage if it gets compromised? Many people use the same password (or its derivative) for every website or service they use. However, you can probably see a problem with that. If one account were to be compromised, all of the other accounts are in danger as well. One technique to solve this issue is to create a unique password for every service you use. But now, this leads to a bigger problem. How would you remember so many different passwords or how would you save them somewhere in a secure manner?


One solution to this problem that I like and use is Mitro. I use Mitro because it is an open source product. There are several other solutions available: 1Password, CommonKey, Dashlane, KeePass, Keeper Password Manager, LastPass, Meldium, Password Genie, Password Safe, RoboForm, Team Password Manager are just some examples.


Mitro will generate a random password for each cloud service that you use and will encrypt and save these all locally. All you have to do is remember just one password for Mitro and Mitro will log you in to any account that you have used Mitro with. Mitro has browser plugins for most browsers and is a simple and efficient solution to the problem of creating secure passwords.


I recommend that you try Mitro. For our corporate clients, I recommended SAML based Single Sign-on onto some centralized directory service and then login to other cloud services from there.


Password alone is not enough – You need additional layer of protection


A common technique most modern services provide is to use 2 step verification (also known as 2 factor authentication or 2FA). Think of it as a pin code (aka a token or a one time password) that you would provide on top of your password. 2FA is a bit more secure because the only way to log into an account is through providing a one time password that changes when you need to log in next.


There are several tools available that can generate this one time password for you:


  • Google Authenticator app on your phone generates one-time password which you must provide after you use your password when logging onto cloud services that are google authenticator enabled.

  • Yubi Key is another interesting technology which is available a small USB device that you plug into your computer. Every time you need to log into an account, you simple touch the USB device and it acts as a token for you to log in.

  • Don’t like to use these? Some services may allow you to opt-in to receive a one time passcode in your TXT/SMS or delivered to via a phone call.

You can secure Mitro as well with 2FA. Mitro can also help you securely share passwords among your team members as needed.


Push yourself towards using 2 factor authentication. Push your business to adopt single sign-on technologies. These techniques will make the cloud a better place for you.


What techniques do you currently use to secure access to critical services?


Join our discussion in the Cloud Genius community and chat with us on our chat channel where we hangout and learn from each other.

 


 

Want us to create an episode on a topic of your interest? Let us know and we gladly develop one. I am your host Nilesh. Look forward to seeing you online.




003 Do you remember passwords?

Thursday, July 9, 2015

000 Introducing All Clouds Considered

All Clouds Considered is brought to you by Cloud Genius®
Cloud Genius is an institution built by industry experts focused on helping businesses succeed with the cloud and helping you transform your professional career.

Take a test drive at https://be.a.cloudgeni.us

Introducing All Clouds Considered.
A podcast for those who want to use the cloud for business & enhance their career.

Welcome to Episode Zero of All Clouds Considered. This one is all about what we will be talking about, who this show is for, and what you can expect.


I have been in the technology trenches since 1983. Over the years, I have invented, patented, and made software that has changed how billions of people do business worldwide.


After acquiring lawful permanent residence status through Microsoft Corporation, I decided it was time to live my dream, so I left Microsoft and started on my own, now with a small team, that focuses on helping businesses benefit from the cloud and helping people use the cloud to advance their career.


My guiding mantra:


Always be learning. And be generous with my knowledge.


In this episode, I will discuss:


  • What is All Clouds Considered?

  • Who this podcast is for?

  • The show format.

  • How to get your technology and business questions answered?

What is All Clouds Considered?


All Clouds Considered is an audio and video podcast where I will share my learnings. Occasionally, I will invite other industry experts to join in and share their perspectives through this podcast.


Who this podcast is for?

This podcast is meant for people who want to use the cloud for business and for people who want to advance their professional career.


The show format


The format of this show is a mix of audio, video, and screen sharing podcasts. Occasionally, I will have remote guest experts join in via Internet video conference and webinars.


How to get your technology and business questions answered?


I invite you to join the Cloud Genius community. You can join us via our chat channel where we hangout and learn from each other.

 


 

Through All Clouds Considered, I look forward to you and I continuing our journey together.


I am your host Nilesh. Look forward to seeing you online.



The Show Notes

Nilesh on LinkedIn, TwitterGoogle+Facebook

Cloud Genius on LinkedIn, Twitter, Google+, Facebook



000 Introducing All Clouds Considered

Tuesday, July 7, 2015

002 Reduce cloud vendor lock-in

Have you taken steps to reduce vendor lock-in?
Here is what we suggest you do.
All Clouds Considered is brought to you by Cloud Genius®
Cloud Genius is an institution built by industry experts focused on helping businesses succeed with the cloud and helping you transform your professional career.

Take a test drive at https://be.a.cloudgeni.us

Vendor lock-in is the situation in which you are dependent on a single vendor for a product (i.e., a good or a service) and cannot move to another vendor without substantial costs and/or inconvenience. Lock-in is typically a result of standards controlled by the vendor, thereby granting the vendor some degree of monopoly power that usually leads to better profits for such vendor… and trouble for you :)


Cloud solutions may sound a really good deal however it is important to remember that you might lock your business up with that cloud vendor.

So what exactly lock-in means in the context of cloud computing. For this we look at the various types of lock-in:


  • Horizontal lock-in limits the ability to replace a product with a comparable competing product. If you chose CRM solution from Oracle earlier, then you will need to migrate your data and code, retrain your users and rebuild the integrations to your other solutions if you want to move to Microsoft Dynamics CRM. Wouldn’t it be nice it you could reuse your garage, cabling, etc., when you switch from Toyota Prius to a Nissa Leaf? The higher you go up the levels of the cloud computing stack the stronger is the horizontal lock-in. Moving from one SaaS solution to another in the cloud is no different from moving from one software to another provided there is a clear migration path. But PaaS can be a very deep lock-in especially if code needs to written to comply with PaaS requirement. IaaS lock-in is much less severe however the underlying hypervisors differ and can lead to some complexity during migration from one IaaS vendor to another.

  • Vertical lock-in limits choice in other levels of the cloud services stack. For example, selecting solution A mandates the use of database B, operating system C, hardware vendor D and/or implementation partner E. Open standards help prevent vertical lock-in by ensuring that hardware, middleware, and operating systems could be chosen independently. Vertical lock-in built-into SaaS and PaaS offerings as the underlying infrastructure comes with the service. However, you won’t need to worry about managing the underlying layers of the cloud stack. IaaS offers comparatively less vertical lock-in. You know that application logic and data need proximity to gain decent performance so you should almost always procure storage services from the same IaaS provider as used for application logic processing.

  • Inclined lock-in is a tendency to buy as many solutions as possible from one provider, even if such solutions in some of these areas are less desirable. You tend to sometimes select a single vendor not only to make management, training and integration easier with a single throat to choke but also to be able to demand higher discounts. This leads to large and powerful vendors causing a high degree of inclined lock-in.

  • Generational lock-in becomes an issue when an entirely new generation of technology reaches the market. No technology generation and no platform lives forever. The first three types of lock-in are not too bad if you picked the right solution vendors (generally the ones that turn out to become the market leaders). But even such market leaders at some point reach end of life. You want to be able to replace them with the new generation of technology without it being prohibitively expensive or even impossible.

Vendor lock-in makes you vulnerable. Think defensively before committingNilesh
Here is what we tell our clients.

 
  1. Avoid vendor lock-in Ensure your app is able to move easily to another cloud provider as and when needed. In essence, keep your plan B in implementable shape and prepare plan B before making serious customizations for a specific cloud platform.

  2. Analyze the TCO for language and tools selection When building your cloud app, think hard about the code selection before you start filling up your git repository. Popular coding languages may not be the most economical for your specific situation. Think of availability of professionals skilled in the coding language of your choice both within and outside your organization.

  3. Carefully select your code base Runtime, scripting environments and code frameworks are not all similar. Discuss with your dev team members on the choice that would be most optimal for you.

  4. Understand redundancy and cloud architecture Identify single points of failure (SPOF) in the architecture. Judge the redundancy elements for yourself and consult with the experts.

  5. Tread PaaS land carefully Explore installable PaaS that you can run yourself if need be. Spread the risk among several different PaaS providers that do not depend on a common IaaS provider.

These tactics are the ones we find most used by our cloud clients in attempting to reduce the impact of vendor lock-in to a good degree.



Got even better ideas on reducing vendor lock-in?

Share below via comments and join our discussion in the Cloud Genius community and chat with us on our chat channel where we hangout and learn from each other.

 


 


Want us to create an episode on a topic of your interest? Let us know and we gladly develop one. I am your host Nilesh. Look forward to seeing you online.



002 Reduce cloud vendor lock-in

003 Do you remember passwords?

Securing access to online banking, email and other cloud services is critical but do you remember your passwords?
 

I think you should not. Why do I say that? Take a listen…
All Clouds Considered is brought to you by Cloud Genius®
Cloud Genius is a top 10 rated institution built by industry experts focused on helping businesses succeed with the cloud and helping you transform your professional career.

Take a test drive at https://be.a.cloudgeni.us

If you can remember most of your passwords, you are either a superhuman or you are doing this password thing wrong. A password that someone can typically remember is not secure enough.


Automatic password management


You have probably heard of security breaches at Snapchat, Target, Adobe, Drupal, Last.fm, Samsung, Apple, Lastpass, in the last few months. With cloud security being an issue of prime importance, how do you choose a password that you can make sure won’t cause you too much damage if it gets compromised? Many people use the same password (or its derivative) for every website or service they use. However, you can probably see a problem with that. If one account were to be compromised, all of the other accounts are in danger as well. One technique to solve this issue is to create a unique password for every service you use. But now, this leads to a bigger problem. How would you remember so many different passwords or how would you save them somewhere in a secure manner?


One solution to this problem that I like and use is Mitro. I use Mitro because it is an open source product. There are several other solutions available: 1Password, CommonKey, Dashlane, KeePass, Keeper Password Manager, LastPass, Meldium, Password Genie, Password Safe, RoboForm, Team Password Manager are just some examples.


Mitro will generate a random password for each cloud service that you use and will encrypt and save these all locally. All you have to do is remember just one password for Mitro and Mitro will log you in to any account that you have used Mitro with. Mitro has browser plugins for most browsers and is a simple and efficient solution to the problem of creating secure passwords.


I recommend that you try Mitro. For our corporate clients, I recommended SAML based Single Sign-on onto some centralized directory service and then login to other cloud services from there.


Password alone is not enough – You need additional layer of protection


A common technique most modern services provide is to use 2 step verification (also known as 2 factor authentication or 2FA). Think of it as a pin code (aka a token or a one time password) that you would provide on top of your password. 2FA is a bit more secure because the only way to log into an account is through providing a one time password that changes when you need to log in next.


There are several tools available that can generate this one time password for you:


  • Google Authenticator app on your phone generates one-time password which you must provide after you use your password when logging onto cloud services that are google authenticator enabled.

  • Yubi Key is another interesting technology which is available a small USB device that you plug into your computer. Every time you need to log into an account, you simple touch the USB device and it acts as a token for you to log in.

  • Don’t like to use these? Some services may allow you to opt-in to receive a one time passcode in your TXT/SMS or delivered to via a phone call.

You can secure Mitro as well with 2FA. Mitro can also help you securely share passwords among your team members as needed.


Push yourself towards using 2 factor authentication. Push your business to adopt single sign-on technologies. These techniques will make the cloud a better place for you.


What techniques do you currently use to secure access to critical services?


Join our discussion in the Cloud Genius community and chat with us on our chat channel where we hangout and learn from each other.

 


 

Want us to create an episode on a topic of your interest? Let us know and we gladly develop one. I am your host Nilesh. Look forward to seeing you online.




003 Do you remember passwords?

Monday, July 6, 2015

002 Reduce cloud vendor lock-in

Have you taken steps to reduce vendor lock-in?
Here is what we suggest you do.
All Clouds Considered is brought to you by Cloud Genius®
Cloud Genius is an institution built by industry experts focused on helping businesses succeed with the cloud and helping you transform your professional career.

Take a test drive at https://be.a.cloudgeni.us

Vendor lock-in is the situation in which you are dependent on a single vendor for a product (i.e., a good or a service) and cannot move to another vendor without substantial costs and/or inconvenience. Lock-in is typically a result of standards controlled by the vendor, thereby granting the vendor some degree of monopoly power that usually leads to better profits for such vendor… and trouble for you :)


Cloud solutions may sound a really good deal however it is important to remember that you might lock your business up with that cloud vendor.

So what exactly lock-in means in the context of cloud computing. For this we look at the various types of lock-in:


  • Horizontal lock-in limits the ability to replace a product with a comparable competing product. If you chose CRM solution from Oracle earlier, then you will need to migrate your data and code, retrain your users and rebuild the integrations to your other solutions if you want to move to Microsoft Dynamics CRM. Wouldn’t it be nice it you could reuse your garage, cabling, etc., when you switch from Toyota Prius to a Nissa Leaf? The higher you go up the levels of the cloud computing stack the stronger is the horizontal lock-in. Moving from one SaaS solution to another in the cloud is no different from moving from one software to another provided there is a clear migration path. But PaaS can be a very deep lock-in especially if code needs to written to comply with PaaS requirement. IaaS lock-in is much less severe however the underlying hypervisors differ and can lead to some complexity during migration from one IaaS vendor to another.

  • Vertical lock-in limits choice in other levels of the cloud services stack. For example, selecting solution A mandates the use of database B, operating system C, hardware vendor D and/or implementation partner E. Open standards help prevent vertical lock-in by ensuring that hardware, middleware, and operating systems could be chosen independently. Vertical lock-in built-into SaaS and PaaS offerings as the underlying infrastructure comes with the service. However, you won’t need to worry about managing the underlying layers of the cloud stack. IaaS offers comparatively less vertical lock-in. You know that application logic and data need proximity to gain decent performance so you should almost always procure storage services from the same IaaS provider as used for application logic processing.

  • Inclined lock-in is a tendency to buy as many solutions as possible from one provider, even if such solutions in some of these areas are less desirable. You tend to sometimes select a single vendor not only to make management, training and integration easier with a single throat to choke but also to be able to demand higher discounts. This leads to large and powerful vendors causing a high degree of inclined lock-in.

  • Generational lock-in becomes an issue when an entirely new generation of technology reaches the market. No technology generation and no platform lives forever. The first three types of lock-in are not too bad if you picked the right solution vendors (generally the ones that turn out to become the market leaders). But even such market leaders at some point reach end of life. You want to be able to replace them with the new generation of technology without it being prohibitively expensive or even impossible.

Vendor lock-in makes you vulnerable. Think defensively before committingNilesh
Here is what we tell our clients.

 
  1. Avoid vendor lock-in Ensure your app is able to move easily to another cloud provider as and when needed. In essence, keep your plan B in implementable shape and prepare plan B before making serious customizations for a specific cloud platform.

  2. Analyze the TCO for language and tools selection When building your cloud app, think hard about the code selection before you start filling up your git repository. Popular coding languages may not be the most economical for your specific situation. Think of availability of professionals skilled in the coding language of your choice both within and outside your organization.

  3. Carefully select your code base Runtime, scripting environments and code frameworks are not all similar. Discuss with your dev team members on the choice that would be most optimal for you.

  4. Understand redundancy and cloud architecture Identify single points of failure (SPOF) in the architecture. Judge the redundancy elements for yourself and consult with the experts.

  5. Tread PaaS land carefully Explore installable PaaS that you can run yourself if need be. Spread the risk among several different PaaS providers that do not depend on a common IaaS provider.

These tactics are the ones we find most used by our cloud clients in attempting to reduce the impact of vendor lock-in to a good degree.



Got even better ideas on reducing vendor lock-in?

Share below via comments and join our discussion in the Cloud Genius community and chat with us on our chat channel where we hangout and learn from each other.

 


 


Want us to create an episode on a topic of your interest? Let us know and we gladly develop one. I am your host Nilesh. Look forward to seeing you online.



002 Reduce cloud vendor lock-in

Sunday, July 5, 2015

Reduce cloud vendor lock-in this Independence day

Have you taken steps to reduce vendor lock-in?
Here is what we suggest you do.
All Clouds Considered is brought to you by Cloud Genius®
Cloud Genius is an institution built by industry experts focused on helping businesses succeed with the cloud and helping you transform your professional career.

Take a test drive at https://be.a.cloudgeni.us

Vendor lock-in is the situation in which you are dependent on a single vendor for a product (i.e., a good or a service) and cannot move to another vendor without substantial costs and/or inconvenience. Lock-in is typically a result of standards controlled by the vendor, thereby granting the vendor some degree of monopoly power that usually leads to better profits for such vendor… and trouble for you :)
cloud-lockin


Cloud solutions may sound a really good deal however it is important to remember that you might lock your business up with that cloud vendor.

So what exactly lock-in means in the context of cloud computing. For this we look at the various types of lock-in:


  • Horizontal lock-in limits the ability to replace a product with a comparable competing product. If you chose CRM solution from Oracle earlier, then you will need to migrate your data and code, retrain your users and rebuild the integrations to your other solutions if you want to move to Microsoft Dynamics CRM. Wouldn’t it be nice it you could reuse your garage, cabling, etc., when you switch from Toyota Prius to a Nissa Leaf? The higher you go up the levels of the cloud computing stack the stronger is the horizontal lock-in. Moving from one SaaS solution to another in the cloud is no different from moving from one software to another provided there is a clear migration path. But PaaS can be a very deep lock-in especially if code needs to written to comply with PaaS requirement. IaaS lock-in is much less severe however the underlying hypervisors differ and can lead to some complexity during migration from one IaaS vendor to another.

  • Vertical lock-in limits choice in other levels of the cloud services stack. For example, selecting solution A mandates the use of database B, operating system C, hardware vendor D and/or implementation partner E. Open standards help prevent vertical lock-in by ensuring that hardware, middleware, and operating systems could be chosen independently. Vertical lock-in built-into SaaS and PaaS offerings as the underlying infrastructure comes with the service. However, you won’t need to worry about managing the underlying layers of the cloud stack. IaaS offers comparatively less vertical lock-in. You know that application logic and data need proximity to gain decent performance so you should almost always procure storage services from the same IaaS provider as used for application logic processing.

  • Inclined lock-in is a tendency to buy as many solutions as possible from one provider, even if such solutions in some of these areas are less desirable. You tend to sometimes select a single vendor not only to make management, training and integration easier with a single throat to choke but also to be able to demand higher discounts. This leads to large and powerful vendors causing a high degree of inclined lock-in.

  • Generational lock-in becomes an issue when an entirely new generation of technology reaches the market. No technology generation and no platform lives forever. The first three types of lock-in are not too bad if you picked the right solution vendors (generally the ones that turn out to become the market leaders). But even such market leaders at some point reach end of life. You want to be able to replace them with the new generation of technology without it being prohibitively expensive or even impossible.

Vendor lock-in makes you vulnerable. Think defensively before committingNilesh
Here is what we tell our clients.

 
  1. Avoid vendor lock-in Ensure your app is able to move easily to another cloud provider as and when needed. In essence, keep your plan B in implementable shape and prepare plan B before making serious customizations for a specific cloud platform.

  2. Analyze the TCO for language and tools selection When building your cloud app, think hard about the code selection before you start filling up your git repository. Popular coding languages may not be the most economical for your specific situation. Think of availability of professionals skilled in the coding language of your choice both within and outside your organization.

  3. Carefully select your code base Runtime, scripting environments and code frameworks are not all similar. Discuss with your dev team members on the choice that would be most optimal for you.

  4. Understand redundancy and cloud architecture Identify single points of failure (SPOF) in the architecture. Judge the redundancy elements for yourself and consult with the experts.

  5. Tread PaaS land carefully Explore installable PaaS that you can run yourself if need be. Spread the risk among several different PaaS providers that do not depend on a common IaaS provider.

These tactics are the ones we find most used by our cloud clients in attempting to reduce the impact of vendor lock-in to a good degree.



Got even better ideas on reducing vendor lock-in?

Share below via comments and join our discussion in the Cloud Genius community and chat with us on our chat channel where we hangout and learn from each other.

 


 


Want us to create an episode on a topic of your interest? Let us know and we gladly develop one. I am your host Nilesh. Look forward to seeing you online.



Reduce cloud vendor lock-in this Independence day

Saturday, July 4, 2015

Reduce cloud vendor lock-in this Independence day

Vendor lock-in is the situation in which you are dependent on a single vendor for a product (i.e., a good or a service) and cannot move to another vendor without substantial costs and/or inconvenience. Lock-in is typically a result of standards controlled by the vendor, thereby granting the vendor some degree of monopoly power that usually leads to better profits for such vendor.
cloud-lockin


Cloud solutions may sound a really good deal however it is important to remember that you might lock your business up with that cloud vendor.

So what exactly lock-in means in the context of cloud computing. For this we look at the various types of lock-in:


  • Horizontal lock-in limits the ability to replace a product with a comparable competing product. If you chose CRM solution from Oracle earlier, then you will need to migrate your data and code, retrain your users and rebuild the integrations to your other solutions if you want to move to Microsoft Dynamics CRM. Wouldn’t it be nice it you could reuse your garage, cabling, etc., when you switch from Toyota Prius to a Nissa Leaf? The higher you go up the levels of the cloud computing stack the stronger is the horizontal lock-in. Moving from one SaaS solution to another in the cloud is no different from moving from one software to another provided there is a clear migration path. But PaaS can be a very deep lock-in especially if code needs to written to comply with PaaS requirement. IaaS lock-in is much less severe however the underlying hypervisors differ and can lead to some complexity during migration from one IaaS vendor to another.

  • Vertical lock-in limits choice in other levels of the cloud services stack. For example, selecting solution A mandates the use of database B, operating system C, hardware vendor D and/or implementation partner E. Open standards help prevent vertical lock-in by ensuring that hardware, middleware, and operating systems could be chosen independently. Vertical lock-in built-into SaaS and PaaS offerings as the underlying infrastructure comes with the service. However, you won’t need to worry about managing the underlying layers of the cloud stack. IaaS offers comparatively less vertical lock-in. You know that application logic and data need proximity to gain decent performance so you should almost always procure storage services from the same IaaS provider as used for application logic processing.

  • Inclined lock-in is a tendency to buy as many solutions as possible from one provider, even if such solutions in some of these areas are less desirable. You tend to sometimes select a single vendor not only to make management, training and integration easier with a single throat to choke but also to be able to demand higher discounts. This leads to large and powerful vendors causing a high degree of inclined lock-in.

  • Generational lock-in becomes an issue when an entirely new generation of technology reaches the market. No technology generation and no platform lives forever. The first three types of lock-in are not too bad if you picked the right solution vendors (generally the ones that turn out to become the market leaders). But even such market leaders at some point reach end of life. You want to be able to replace them with the new generation of technology without it being prohibitively expensive or even impossible.

Vendor lock-in makes you vulnerable. Think defensively before committingNilesh
Here are our quick defense tactics against cloud vendor lock-in.

 
  1. Avoid vendor lock-in Ensure your app is able to move easily to another cloud provider as and when needed. In essence, keep your plan B in implementable shape and prepare plan B before making serious customizations for a specific cloud platform.

  2. Analyze the TCO for language and tools selection When building your cloud app, think hard about the code selection before you start filling up your git repository. Popular coding languages may not be the most economical for your specific situation. Think of availability of professionals skilled in the coding language of your choice both within and outside your organization.

  3. Carefully select your code base Runtime, scripting environments and code frameworks are not all similar. Discuss with your dev team members on the choice that would be most optimal for you.

  4. Understand redundancy and cloud architecture Identify single points of failure (SPOF) in the architecture. Judge the redundancy elements for yourself and consult with the experts.

  5. Tread PaaS land carefully Explore installable PaaS that you can run yourself if need be. Spread the risk among several different PaaS providers that do not depend on a common IaaS provider.

These tactics are the ones we find most used by our cloud clients in attempting to reduce the impact of vendor lock-in to a good degree.


Got other ideas on how you would avoid cloud vendor lock-in? Share via comments.




Reduce cloud vendor lock-in this Independence day

Reduce cloud vendor lock-in this Independence day

Vendor lock-in is the situation in which you are dependent on a single vendor for a product (i.e., a good or a service) and cannot move to another vendor without substantial costs and/or inconvenience. Lock-in is typically a result of standards controlled by the vendor, thereby granting the vendor some degree of monopoly power that usually leads to better profits for such vendor.
cloud-lockin


Cloud solutions may sound a really good deal however it is important to remember that you might lock your business up with that cloud vendor.

So what exactly lock-in means in the context of cloud computing. For this we look at the various types of lock-in:


  • Horizontal lock-in limits the ability to replace a product with a comparable competing product. If you chose CRM solution from Oracle earlier, then you will need to migrate your data and code, retrain your users and rebuild the integrations to your other solutions if you want to move to Microsoft Dynamics CRM. Wouldn’t it be nice it you could reuse your garage, cabling, etc., when you switch from Toyota Prius to a Nissa Leaf? The higher you go up the levels of the cloud computing stack the stronger is the horizontal lock-in. Moving from one SaaS solution to another in the cloud is no different from moving from one software to another provided there is a clear migration path. But PaaS can be a very deep lock-in especially if code needs to written to comply with PaaS requirement. IaaS lock-in is much less severe however the underlying hypervisors differ and can lead to some complexity during migration from one IaaS vendor to another.

  • Vertical lock-in limits choice in other levels of the cloud services stack. For example, selecting solution A mandates the use of database B, operating system C, hardware vendor D and/or implementation partner E. Open standards help prevent vertical lock-in by ensuring that hardware, middleware, and operating systems could be chosen independently. Vertical lock-in built-into SaaS and PaaS offerings as the underlying infrastructure comes with the service. However, you won’t need to worry about managing the underlying layers of the cloud stack. IaaS offers comparatively less vertical lock-in. You know that application logic and data need proximity to gain decent performance so you should almost always procure storage services from the same IaaS provider as used for application logic processing.

  • Inclined lock-in is a tendency to buy as many solutions as possible from one provider, even if such solutions in some of these areas are less desirable. You tend to sometimes select a single vendor not only to make management, training and integration easier with a single throat to choke but also to be able to demand higher discounts. This leads to large and powerful vendors causing a high degree of inclined lock-in.

  • Generational lock-in becomes an issue when an entirely new generation of technology reaches the market. No technology generation and no platform lives forever. The first three types of lock-in are not too bad if you picked the right solution vendors (generally the ones that turn out to become the market leaders). But even such market leaders at some point reach end of life. You want to be able to replace them with the new generation of technology without it being prohibitively expensive or even impossible.

Vendor lock-in makes you vulnerable. Think defensively before committingNilesh
Here are our quick defense tactics against cloud vendor lock-in.

 
  1. Avoid vendor lock-in Ensure your app is able to move easily to another cloud provider as and when needed. In essence, keep your plan B in implementable shape and prepare plan B before making serious customizations for a specific cloud platform.

  2. Analyze the TCO for language and tools selection When building your cloud app, think hard about the code selection before you start filling up your git repository. Popular coding languages may not be the most economical for your specific situation. Think of availability of professionals skilled in the coding language of your choice both within and outside your organization.

  3. Carefully select your code base Runtime, scripting environments and code frameworks are not all similar. Discuss with your dev team members on the choice that would be most optimal for you.

  4. Understand redundancy and cloud architecture Identify single points of failure (SPOF) in the architecture. Judge the redundancy elements for yourself and consult with the experts.

  5. Tread PaaS land carefully Explore installable PaaS that you can run yourself if need be. Spread the risk among several different PaaS providers that do not depend on a common IaaS provider.

These tactics are the ones we find most used by our cloud clients in attempting to reduce the impact of vendor lock-in to a good degree.


Got other ideas on how you would avoid cloud vendor lock-in? Share via comments.




Reduce cloud vendor lock-in this Independence day

Thursday, July 2, 2015

001 Do you remember to backup?

Backing up your data is critically important... but do you remember to backup? Always?
I think you should not.

Why do I say that? Take a listen…

All Clouds Considered is brought to you by Cloud Genius®
Cloud Genius is an institution built by industry experts focused on helping businesses succeed with the cloud and helping you transform your professional career.

Take a test drive at https://be.a.cloudgeni.us

Backups and restores are ideally done by robots…completely hands-free, fully automated, totally encrypted.


In this episode, I will not discuss the importance of backup because you probably know it already, instead, I will discuss


  • Why backups should not be on your to do list

  • The true test of a backup solution

  • Encrypting your backups

  • How do I currently backup?

Why backups should not be on your to do list


I believe you should have control over your digital lives, including your backups. I believe you can get the benefits of cloud computing without having to give up privacy or security.


Doing backups is a chore. A huge risk in backing up manually is that you might forget to backup. You are a human after all. So my solution to this problem is to not put backups on my todo list…instead I assign the task to a piece of software which runs in the background and backs up *all* things I need backed up.


The true test of a backup solution


Backing up alone is not a complete solution to the problem. The true test of a proper backup solution is a complete, successful restore that is free from encumbrance. I, therefore, strongly suggest that you test whether the backup you took is actually restorable exactly the way you like. There is no point in backing up if you can’t restore.


Encrypting your backups


Backing up to the cloud? What if someone gets hold of your backup? What if someone  violates your privacy in the cloud? How do you go about preventing that from happening to begin with? Do you recall that iCloud fiasco and those poor little celebrities?


How do I currently backup?


I use Arq backup with a hidden folder in my google drive as the backup target. It automatically and continuously backups all that I need. It de-duplicates to cut unnecessary redundancy. And, it allows me to select my encryption key while ensuring that that backups are encrypted with my encryption key before any packet leaves my firewall.


The most important reason I use this software is because the author provides arq_restore, an elegant, open-source command-line utility for restoring from backups that is free from encumbrance even though this software itself is not open source. This way, I can get my data back even in case if this company goes out of business.


How would you improve upon this method?


How do you automate your backups? How would you improve upon my current method of automating backups? Join our discussion in the Cloud Genius community and chat with us on our chat channel where we hangout and learn from each other.

 


 


Want us to create an episode on a topic of your interest? Let us know and we gladly develop one. I am your host Nilesh. Look forward to seeing you online.



The Show Notes


ARQ Backup
Google Drive

Nilesh on LinkedIn, TwitterGoogle+Facebook

Cloud Genius on LinkedIn, Twitter, Google+, Facebook




001 Do you remember to backup?