Knowledge Enhancement - RushKar

The certified services and prompt customer support has made Rushkar a top custom software development company in Ahmedabad at GoodFirms.

Rushkar is a private organization situated in Ahmedabad, India that deals in Microsoft technologies like ASP.Net. MVC, Dot Net Core, BizTalk, MS Dynamics CRM, Python, JAVA, and Mobile Applications (Hybrid & Native). The team of Rushkar selects the technologies or platforms that suit their clients’ requirements and assures robust software development with timely deliveries of various MVPs. Rushkar comprises of experts with 15+ years of experience in custom software and web application development along with hardware integration. 

Rushkar has been able to establish a strong presence of its impressive software development services globally including countries like the USA, UK, Canada, Australia, and the Middle East. Furthermore, the wizards of Rushkar have successfully accelerated the business output of their clients belonging to versatile industrial sectors like Health Care, Transportation, Logistics, Media, Oil & Gas, Education and so on.

GoodFirms’ Research Process

The companies that register with GoodFirms get researched and accredited on regular intervals. The scoring and ranking process is based on primary and secondary research from data available from various sources.

The research process heavily relies on three principal evaluations – Quality, Reliability, and Ability. The quality of the company is evaluated based on client ratings and project portfolios. Market penetration and experience is considered for assessing the reliability of the agency. While the ability of the company is judged based on the resources held by the company.

GoodFirms recently assessed Rushkar for their service-offering in three techno-commerce niches. Find the detailed findings below:

Rushkar’s Assessment and Rankings on GoodFirms:

Software Development Company

Rushkar builds business-driven applications that help their clients acquire exponential development in business with engaging applications. The team of Rushkar excels at every significant aspect of customized software development including designing, testing, programming, planning, bug fixing & more, which allow effective development & maintenance of an application or software. The full range of software services provided by Rushkar has earned the company an impressive position on the list of top software companies in Ahmedabad at GoodFirms.  

Have a look at one of the many reviews received by Rushkar at GoodFirms for its software development services:

Here is the scorecard evaluated by GoodFirms’ research team for Rushkar’s software development services:

Mobile App Development Company

Rushkar caters to its global clients with end-to-end app development services over all the significant versatile platforms including iOS, Android, and Windows Mobile. The crew of Rushkar holds expertise in mobile application advancement by building cross-stage portable applications that work consistently.

The exceptionally talented group of iOS and Android application engineers at Rushkar inspire innovative solutions in native iOS, Android, cross-platform, a hybrid app, and custom mobile app development services for B2B, B2C, C2B, and so on. Needless to say, Rushkar Technology will soon have its name embarked on the global list of top mobile app development services at GoodFirms.  

GoodFirms has also got a scorecard for Rushkar’s progressive mobile app development services:

Web Development Company

Ruskar focuses on front end development of highly functional interactive websites with user-friendly interface & smooth navigation. The tech wizards of Pushkar assure mobile optimized responsive web development along with custom interactivity. The members of the web development team at Rushkar produce feature-rich client applications with cross-browser, cross-platform, cross-device functionality. These simple facts have assured the company’s arrival on the list of top web development companies in India at GoodFirms.

About GoodFirms

Washington, D.C. based GoodFirms is stellar research and reviews platform for top software development companies, mobile app development companies, among many others in the B2B IT sphere. GoodFirms’ extensive research process ranks the companies, boosts their online reputation and helps service seekers pick the right technology partner that meets their business needs.

About the Author:

Anna Stark

Anna Stark is presently working as a Content Writer with GoodFirms – Washington D.C. based B2B Research Company, which bridges the gap between service seekers and service providers. Anna’s current role lingers her to shape every company’s performance and key attributes into words. She firmly believes in the magic of words and equips new strategies that work, always in with ideas, something new to carve, and something original to decorate the firm’s identity.

ASP.NET Web API is a framework to build HTTP services for multiple clients, including browsers and mobile devices. ASP.NET Web API is platform to build RESTful applications on top of .NET Framework. If creating ASP.NET Web API for multiple clients then it could be required to have versioning in API which allows you to alter behavior between different clients.

Why need versioning?

• API versioning should be required if any change in data contract such as renaming or deleting parameter or change in format of the response is required.
• Change in URL can also be considered for versioning. E.g. when it changes from api\user?id=123 to api\user\123 can be considered change in version.
• API versioning will introduce complexity for both service implementation and client using API.

REST does not provide any versioning but it can be achieved with help of one of the following more commonly used approaches,

URI Path

1. 1. Add API version in URI. e.g. api/v1/user/123 and api/v2/user/123
   2. It is very common and most straightforward approach though it violets REST API design who insist a URI should refer to unique resource.
2. Custom Request Header
   1. In this approach, customer header allows you to use URIs with versions which will be duplicate of content negotiation behavior implemented by existing Accept header. e.g. api-version: 2
3. Content Negotiation
   1. It most recommended approach nowadays, it allows clean set of URIs with help of accept header with some complexity to server different version of content/resource. e.g. Accept: application/vnd.domain.v2+json

API versioning, which to choose?

• Considering the continuous change in API, any versioning approach could be wrong at some point.
• A real challenge with versioning is managing the code base which serving multiple versions of resource. If all the versions are kept in same code base then older versions could be vulnerable at some point for unexpected changes. If code base are different then very high chances of escalation in maintenance.
• A versioning could be obstacle to improvements as version change are restricted.
• Versioning with content negotiation and custom headers are popular nowadays, but versioning with URL are more common now as it's easier to implement.
• It’s a pragmatic decision, but API should have version from the first release.

 Resource versioning?

• With versioning of API it should be required to version resources as different version may return resource with change. It can be easily achieved with help of inheritance.

ASP.NET Web API versioning can be achieved by extending DefaultHttpControllerSelector, following code illustrates versioning with content negotiation

public class ContentNegotiationVersioningSelector : DefaultHttpControllerSelector
    {
        private HttpConfiguration _HttpConfiguration;
 
        public ContentNegotiationVersioningSelector(HttpConfiguration httpConfiguration) : base(httpConfiguration)
        {
            _HttpConfiguration = httpConfiguration;
        }
 
        /// <summary>
        /// extesnsion to default controller selector
        /// </summary>
        public override HttpControllerDescriptor SelectController(HttpRequestMessage request)
        {
            HttpControllerDescriptor controllerDescriptor = null;
 
            // get list of controllers provided by the default selector
            IDictionary<string, HttpControllerDescriptor> controllers = GetControllerMapping();
            // get request route data
            IHttpRouteData routeData = request.GetRouteData();
 
            if (routeData == null)
            {
                throw new HttpResponseException(HttpStatusCode.NotFound);
            }
 
            // get api version from accept header
            var apiVersion = GetVersion(request);
 
            //check if this route is actually an attribute route
            IEnumerable<IHttpRouteData> attributeRoutes = routeData.GetSubRoutes();            
 
            if (attributeRoutes == null)
            {
                string controllerName = GetRouteVariable<string>(routeData, "controller");
                if (controllerName == null)
                {
                    throw new HttpResponseException(HttpStatusCode.NotFound);
                }
 
                string versionControllerName = String.Concat(controllerName, "V", apiVersion);
 
                if (controllers.TryGetValue(versionControllerName, out controllerDescriptor))
                {
                    return controllerDescriptor;
                }
                else
                {
                    throw new HttpResponseException(HttpStatusCode.NotFound);
                }
            }
            else
            {
                // find all controller descriptors whose controller type names end with
                // the following suffix (example: ControllerV1)
                string versionControllerName = String.Concat("V", apiVersion);
 
                IEnumerable<IHttpRouteData> filteredAttributeRoutes = attributeRoutes
                    .Where(attrRouteData =>
                    {
                        HttpControllerDescriptor currentDescriptor = GetControllerDescriptor(attrRouteData);
 
                        bool match = currentDescriptor.ControllerName.EndsWith(versionControllerName);
 
                        if (match && (controllerDescriptor == null))
                        {
                            controllerDescriptor = currentDescriptor;
                        }
 
                        return match;
                    });
 
                routeData.Values["MS_SubRoutes"] = filteredAttributeRoutes.ToArray();
            }
 
            return controllerDescriptor;
        }
 
        /// <summary>
        /// gets the controller descriptor for attribute routes.
        /// </summary>
        private HttpControllerDescriptor GetControllerDescriptor(IHttpRouteData routeData)
        {
            return ((HttpActionDescriptor[])routeData.Route.DataTokens["actions"]).First().ControllerDescriptor;
        }
 
        /// <summary>
        /// gets value from the route data, if present.
        /// </summary>
        private static T GetRouteVariable<T>(IHttpRouteData routeData, string name)
        {
            object result = null;
            if (routeData.Values.TryGetValue(name, out result))
            {
                return (T)result;
            }
            return default(T);
        }
 
        /// <summary>
        /// gets the type of the version
        /// Accept: application/vnd.domain.v{version}+json
        /// </summary>
        private string GetVersion(HttpRequestMessage request)
        {
            var acceptHeader = request.Headers.Accept;
 
            var regex = new Regex(@"application\/vnd\.domain\.v([\d]+)\+json", RegexOptions.IgnoreCase);
 
            foreach (var mime in acceptHeader)
            {
                Match match = regex.Match(mime.MediaType);
                if (match.Success == true)
                {
                    return match.Groups[1].Value; // change group selection based on regex if requried
                }
            }
 
            return "1"; // return latest version if not accept header provided (should be configured)
        }
    }

Add following line to replace default controller selector,

config.Services.Replace(typeof(IHttpControllerSelector), new ContentNegotiationVersioningSelector(config));

Controller hierarchy for versioning

Versioning resource or POCO classes

Similarly, URL and custom header based versioning can be implemented by extending DefaultHttpControllerSelector as above.