In our last blog, we looked at ensuring our code was streamlined and efficient, but we also need to look at the technology that we use to develop and deploy the product. Many solutions can be developed to solve the same issue and although each often has pros and cons, often there are obvious technologies to discount.

It can be surprisingly difficult to select the correct technology to use for the requirement, for example, do you use a trigger, process builder, visual flow or workflow when a record becomes updated. And there are many other questions you can ask such as;

• Do you use a custom setting or custom metadata to hold product configuration settings?
• Do you store large data sets in a custom object, an external object or a Big Object?
• Do you use SOAP or REST for integration.

These are all questions that a good PDO will ask in the development process and whilst it may seem harder than you first think, it will be normal for the PDO.

The effects of using the wrong technology when building an internal application is not as great; doing so for your customer using your app can be profound.

To find out more about the challenges and the potential Pot Holes have a read of this article or contact us to find out how we would approach different challenges. Or if you want to find out how we can help email Steven.Fouracre@metacube.com