Method Routing

At the heart of this design is the simplification of the layering between data and request <-> display. Much of modern system design is abstraction and services: event driven, distributed.  However this has constricted the velocity of feature development by requiring the mapping of data created from external sources. 

Accessibility does not mean assessible. On a project that I work on, there was a requirement to create JSON objects for submission to Salesforce. The data sources were a number of 'micro-services' that produced generic data models. This placed the burden on me to not only request the data from each of the seperate data sources and then retrieve the applicable data fields required for populating the Salesforce JSON schema object.

• In cloud development the primary design pattern is 'microservices'. 
• Microservices are a powerful approach to 'services' architecture. 
• Services are based on domains of functionality and processing.  

BUT, web applications are not extensions of microservices they are Client/Server applications that provide user interfaces to interact with data and system processing.

As a Client<->Server Application, the front-end needs to access data stored for consumption. A mistake that many make in  modern development is to carry forward the process of manufacturing data 'On-Demand'.  Much time and coordination was mandated, within the monolith structure, for the optimization of data extraction and transformation, while the user waits. 

I am reminded of advancements within the 'Fast Food' industry, in the 50's and 60's. Although, not perfect, the solutions for providing good food, fast, was to do one of the following:

1. Prepare a wide menu of items staged under the heat lamps for immediate consumption.
2. Reduce the menu to very few items and be in a constant state of preparing the primary ingredients for assemble upon ordering. 

In keeping with this analogy, data can be manufactured 

EXAMPLE:

Web Controller:

Single Controller Providing ReSTful Methods 

1. Post
2. Put
3. Get
4. Delete

Each Method will accept a JSON Object based on a JSON Schema Interface

1. Action → equivalent method calling the business coding. Using System. Reflection- Invoke Method
2. Parameters → array of variable names and data values

    public class MethodRouting

    {

        public dynamic ProcessRequest(string JsonPayload)

        {

            JObject jObject = JObject.Parse(JsonPayload);

            string methodName = jObject["methodName"].ToString();

            DataProcessing dataProcessing = new DataProcessing();

            MethodInfo methodInfo = dataProcessing.GetType().GetMethod(methodName);

            var parameterLength = methodInfo.GetParameters().Count();

            var methodParameters = new object[parameterLength];

            var parametersRequest = jObject["parameters"];

            for (int i = 0; i < parameterLength; i++)

            {

                methodParameters.SetValue(parametersRequest[i], i);

            }

            methodInfo.Invoke(dataProcessing, (parameterLength == 0) ? null : methodParameters);

        }

    }