Skip to main content

software evaluation and storage

Cloud providers offer a certain combination of technology and storage solution which becomes their unique selling point. The focus for some providers is majorly based on the software stack they offer. Most providers move from offering plain infrastructure as a service to offering platform as a service.
The stack-specific clouds are known to align with the popular cloud solutions available. The application which is built using the software stack defined by the cloud will save a lot of time and cost. With this solution, enterprises need not use the lower-level infrastructure setup and configuration. This software stack that is provided requires the enterprises to follow certain best practices while designing and writing the apps, which in turn requires high levels of vendor lock- in.
Along with software stack, storage is an important consideration. How will the data be stored in the cloud and made accessible to the enterprises? Will the storage solution make way for remote access? Virtualization is another concern that should be addressed before hiring the cloud solution.
Vendor Lock-in and Legal Compliance
The application programming interface (API) offered by the cloud solution is an important criteria that one should evaluate. This helps one access the infrastructure and performs operations like provisioning and de-provisioning servers.
The API is supported by multiple providers, and vendors will reduce the lock-in and help towards migration whenever needed. Again, the application does not need to be changed majorly in this case. The developer-vendor ecosystem will help enhance the services and capabilities of the cloud solution provider.
Consider the cloud solution provider that offers a developer-vendor ecosystem and has taken into consideration all the legal compliances that will make migration easy and convenient. The API should be supported by majorly all vendors and should comply with all the legal and security requirements as defined by the enterprises. API monitoring and management should be easy with the tools offered by the cloud solution provider.

Comments

Popular posts from this blog

The Seven-Step Model of Migration

Irrespective of the migration approach adopted, the Seven-step Model of Cloud Migration creates a more rational point of view towards the migration process and offers the ability to imbibe several best practices throughout the journey Step 1: Assess Cloud migration assessments are conducted to understand the complexities in the migration process at the code, design and architectural levels. The investment and the recurring costs are also evaluated along with gauging the tools, test cases, functionalities and other features related to the configuration. Step 2: Isolate The applications to be migrated to the cloud from the internal data center are freed of dependencies pertaining to the environment and the existing system. This step cuts a clearer picture about the complexity of the migration process. Step 3: Map Most organisations hold a detailed mapping of their environment with all the systems and applications. This information can be used to distinguish between the

Special Permissions in linux

The setuid permission on an executable file means that the command will run as the user owning the file, not as the user that ran the command. One example is the passwd command: [student@desktopX ~]$ ls -l /usr/bin/passwd -rw s r-xr-x. 1 root root 35504 Jul 16 2010 /usr/bin/passwd In a long listing, you can spot the setuid permissions by a lowercase s where you would normally expect the x (owner execute permissions) to be. If the owner does not have execute permissions, this will be replaced by an uppercase S . The special permission setgid on a directory means that files created in the directory will inherit their group ownership from the directory, rather than inheriting it from the creating user. This is commonly used on group collaborative directories to automatically change a file from the default private group to the shared group, or if files in a directory should be

RequestsDependencyWarning: urllib3 (1.24.1) or chardet (3.0.4) doesn't match a supported version

import tweepy /usr/lib/python2.7/dist-packages/requests/__init__.py:80: RequestsDependencyWarning: urllib3 (1.24.1) or chardet (3.0.4) doesn't match a supported version!   RequestsDependencyWarning) Traceback (most recent call last):   File "<stdin>", line 1, in <module>   File "/usr/local/lib/python2.7/dist-packages/tweepy/__init__.py", line 14, in <module>     from tweepy.api import API   File "/usr/local/lib/python2.7/dist-packages/tweepy/api.py", line 12, in <module>     from tweepy.binder import bind_api   File "/usr/local/lib/python2.7/dist-packages/tweepy/binder.py", line 11, in <module>     import requests   File "/usr/lib/python2.7/dist-packages/requests/__init__.py", line 97, in <module>     from . import utils   File "/usr/lib/python2.7/dist-packages/requests/utils.py", line 26, in <module>     from ._internal_utils import to_native_string   File "/usr/lib/python2.

tag