Cloud-Neutral Development is the future of IT

Cloud becomes first choice for deployment of applications for most of the companies. Major benefits of cloud is cost, speed, scale & reliability. With the increase in the number of cloud providers, today companies have many choices to pick their deployment cloud provider.

Now major question for any organization is which cloud provider they should choose? Generally all cloud provider gives browser-based dashboard that makes it easier for IT professionals and developers to order resources and manage their accounts. Some cloud computing services are also designed to work with REST APIs and a command-line interface (CLI), giving developers multiple options.

If you have specific need in your application and some provider provides PaaS service which fulfill maximum of your requirement than you can go for cloud-native development model. In this model you will stick with particular cloud provider. You will not able to move to other cloud provider in future without any or major changes in your application.



Container based development makes you application platform independent. If you are using cloud provider for IaaS purpose than it is easy for you to change provider in future at any time. With the PaaS services you need to stick with particular provider. Many cloud provider are more focusing to sale PaaS services because that client will not able to leave easily.

By using PaaS we can save lot of cost in developing those solutions by our-self.

Following are the key reasons why your application or product should be cloud neutral-

  • To avoid vendor lock-in – you don’t want to get stuck with a particular vendor as you will need the flexibility to move to other cloud providers in future. Because of the competition market you might get same services with very low cost by other cloud provider, if your application is cloud neutral than you can easily move to other provider.
  • Geographic Support – in many of the countries there are restrictions that enforce the data to stay within the boundaries of the country. There is a possibility that the cloud vendor you have chosen may not have a data centre in that geography. In this scenario, you don’t have a choice other than to deploy with a different local cloud provider. Therefore, your application should be able to work in any cloud.
  • Reusability of components – It’s very common to re-use some part or component or service of one application in other application. If other application is hosted in on-premises or in other cloud than you will not able to use easily in case of cloud-native model. 


Comments

Post a Comment

Popular posts from this blog

Serverless Integration design pattern on Azure to handle millions of transactions per second

Image
Recently i was working on one of the integration project where client have following requirements- It should support millions of transactions per second Based on demand/number of requests it should auto-scale. Client don't want to procure huge hardware up-front. It should support multiple applications integration & open for future integrations without any or minimum changes. If any application is down for some time, framework should have in-build retry logic after some configured schedule. We have analyzed below options for this integration framework- 1. Biztalk Server 2. Azure Function, Logic App & Event Hub 3. Third party integration server Every option has its own pros & cons. Based on client requirement analysis with each option we found option 2, Azure Function and Event Hub approach most suitable for this type of integration. Below are the main features which played a key role to select this framework for integration- Azure Function- A...
Read more

Working with Stored Procedure in Azure DocumentDB (CosmosDB)

Image
In this blog post we will learn how to create & test Stored Procedure in Azure DocumentDB (CosmosDB). Login to Azure Portal & click on New. Search for cosmosDB- Click on "Azure Cosmos DB". Click on "Create". Fill up all details e.g.- CosmosDB ID, API (for this demonstration we will select DocumentDB), Subscription, Resource Group & Location. Click on "Create" button. After creating cosmos DB ID you can view as below screenshot- Below are the some important points which we should keep in mind- 1. We can create multiple Databases under one Cosmos DB.  2. One database can have multiple collections.  3. One collection can have multiple documents.  4. Each document have one field as "id" this is primary key for each document. This is also unique under one collection. We can't create multiple documents with same id under one collection. To create collection and database click ...
Read more