Skip to main content

Deployment Strategies (Greenfield, Brownfield, Bluefield, Greyfield)

It is crucial to understand the project deployment and the landscape of any technical project. This will help to assess the complexity and dependencies to plan across. Information Technology terminology landscape refers to related infrastructure and application components/systems around. Knowing your field helps you to plan for execution and deployment strategies effectively.

No alt text provided for this image





Greenfield Deployment

Greenfield is an empty landscape where nothing is decided or confirmed. The technical team can decide on the technology and how it can be utilized. There are no dependencies on existing applications and thus can be easily rolled out.

No alt text provided for this image

  • A fresh start and nothing exist at the moment
  • Can introduce best practices, new flows
  • Moderate risk presents as there is no proof of a working landscape
  • Adding a new landscape to existing

Brownfield Deployment

Brownfield can be considered as extending the landscape base on existing technology. this can be thought as upgrading or adding new components based on the existing landscape.

No alt text provided for this image

  • Proper understanding of the existing technology
  • low-risk tolerance as technology is already in use and exist
  • Build on existing technology
  • Less dependency management as it is expanding the same landscape.

Bluefield Deployment

Contains the properties of both greenfield and brownfield. This introduces a new landscape that coexists with the existing landscape. Dependencies should be managed to accommodate the existing landscape. This can be thought of as adding new technology to an existing application (Ex:- adding a cloud base AI component to an existing on-premises application)

No alt text provided for this image

  • Combination of Green and Brown deployment
  • Present moderate risk tolerance as new technology will be introduced.
  • New best practices and ideas can be accommodated into the new component
  • Dependencies should be managed and identify for successful deployment

Greyfield Deployment

This is not a famous strategy we encounter usually. Greyfield is an application landscape which has been used before but kind of isolated and mostly unused for the moment. This involves the redevelopment of the existing landscape and making use of it. The key point is to utilize most of the existing landscape and extend and add new capabilities on top of this to use.

No alt text provided for this image

  • This includes converting obsolete landscape to usable components
  • Proper assessment required (decommissioning and greenfield may be viable sometimes rather than doing Grayfeild)
  • Dependencies should be assessed along with the feasibility
Labels:

Comments

Post a Comment

Popular posts from this blog

How to Link Two List and Create a combine view in the SharePoint 2010

In this way you can join multiple list together and can create a combine view. for an example assume that you are managing a list for some events. And also you are having a participants in separate list. Thus you want to join the two list and create a composite view. SharePoint 2010 allows you to create this kind of view using  Linked Data Source. in this approach you can create your own custom list in the SharePoint. How to Create a Linked Data source Go to SharePoint designer and  go to the link called data sources. And Click the Linked Data Source button in the ribbon. Then SharePoint designer will prompt following kind of a dialog. In there add two list, that you wan to linked together. I'm adding airline schedule and booking list. those are the two list that i wan to merge. then click next. And it will guide you another screen. it will ask you to select either Merge Merge use to combine list which are having same columns definition. for and example we can s...
32 comments
Read more

How to set Current User Name to InfoPath Person/Group Picker

This method also use for get User Profile Information such as First Name , Last Name , Office and etc. In generally we can not set a default value to InfoPath Person/Group Picker. On the other hand we can not get Current Username in the InfoPath. (Yeh it is true that we can use userName() function. But this will return the Current User Account ID not the name). So we want to use SharePoint user profile services to do this. First we need to  create a user profile connection. Thus First go to Manage connection and click add connection. Then go to receive data option and SOAP Web service and specify the User Profile Service URL . The URL will be something like ( http://sever/sites/site/_vti_bin/UserProfileService.asmx ). This is depends on your site or site collection. if it is a site collection you can omit /sites/site/ part from your URL. then proceed to next , select UserProfileByName and un select the Automatically load. Now you have created the connection....
8 comments
Read more

The content database has a schema version which is not supported this version

How to copy you production SharePoint  database to development environment. I had my production environment as SharePoint 2013 SQL Server 2012 and I want to move the instance to another environment , which is freshly installed and different environment and different KBs Share Point 2013 SQL Server 2016 How to migrate SharePoint 2013 , SQL Server 2012 Content Database to SharePoint 2013 SQL Server 2016. Method 1. This is a general method, which is used for upgrading your content database. 1 . Get the back up of the current Content Database 2. Copy SQL backup to new environment 3. Restore the SQL Back Up in to the new environment 4. Go to the Security Login section and grant permission to content database for existing SharePoint Users.   5. You need to select the User mapping and DBO for the content database. 6 Then, execute below PS in SharePoint PowerShell. Make sure you executed as Run as Administrator 7 Firstly, You need to Update the content database. 8. then, mount the usi...
Post a Comment
Read more