In this blog series, the UD 5 Performance Part 1 article focused on benchmarks between the UD 4.7 and UD 5.0 using a simple read / modify / write loop running directly on the server. This article continues the same series of testing by including record locking in the test loop to compare the impact of locking between both Universal Drivers. Details about the test setup and testing environment are included in part 1, and since this is a continuation we will not review the details in this part.
Since writing part 1, Revelation Software also released an article on UD 5 and UD 4.7 Benchmarks. Their benchmarks compared the overall test time where as our series is more focused on throughput (records read/written per second). Two key differences between the Revelation tests and the testing methodology in our series is the Revelation Software benchmarks include locking and wrote new records into a new table. This series does not write any new records but instead modifies only existing records.
There is a lot of excitement around the release of the Universal Driver 5.0 and it’s new features. This article will be the first of several that analyzes the performance and operation of the new product against the current Universal Driver 4.7.
Manufacturer benchmarks are a black art with comparisons done to test the product under the best possible circumstances to highlight product superiority. The benchmark test in this article is independent of the manufacturer and designed not to introduce un-needed complexity or variables. Default options are selected whenever possible during setup and the test is run directly on the server.
There is no end in sight to the growth of online content and web services. Sooner or later your application will need to communicate with an online service for new functionality. You may need to interface your OpenInsight based application with a web API or simply need to download a file. This blog article walks through extending the built-in functionality to provide a more feature rich user experience.
With the rising demand for proper and established standards with web-based applications SRP has been rather busy implementing Representational State Transfer (REST) APIs. We will be sharing our experiences and best practice approaches to this in upcoming articles. Since Semantic URLs are often considered an important element of implementing RESTful APIs we wanted to lead off with an article that explains how all versions of the OECGI can be hidden from the URL.