Web service design in Verne
With Verne™’s use of a document database, and the extensive use made of web services to interact with Verne register, efficient and well thought out web service design is critical to a successful implementation.
The whitepaper outlines best practice and recommendations for appropriate web service design within Verne. It describes an approach which complements the system architecture of Verne, while providing an efficient communication protocol and minimising the overhead of complex maintenance.
The whitepaper covers the key concepts of Verne Web Services before going into details about the best-practice implementation approach and outlining Verne’s implementation of OpenAPI.
Business Service Design in Verne
Verne™ business services define and support the processing of nearly all functionality available within a Verne™ application. A single business service (or just service) defines a single piece of functionality available to perform on (or create) some long-living registry data.
Examples of a business services in a companies register include company registration, maintaining directors, changing addresses, performing an annual return, doing a correction, etc.
This whitepaper outlines efficient and effective Business Service designs for a Verne™ implementation so that solution architects and developers can leverage the maximum benefit from the Verne™ platform whilst deploying a solution which provides both efficiency and maintainability.
Readers will find information on optimising the design of business services and how to make decisions about the level at which business services should be targeted. It explains how a designer may combine or separate busines services to accommodate the functional requirements of a delivery.
