Schreiben von Software

Hi, This can be delivered as maven project is ready, only customization is needed according to your need.

This is my understanding of requirement : A REST-ful webservice should be developed as a independent, loose coupled and reusable utility service. The primary goal of this REST API is to provide the metadata of a particular database (I assume MySQL is used in assignment) i.e. data base name, version, operating system on which DB is hosted, table information (table name, coulmns, contstrains, names etc), indexes, sequences etc. A service can offer multiple operations like getDataBaseInformation, getDataBaseTables, getDataBaseTableInformation etc. to fetch different metadata about DB OR one globale method which returns the whole DB metadata. A use case I can think of this service is to enable DB clients to discover and fetch the information about the database dynamically and query tables. This decouples DB clients from the physical details of database and lets to evolve independently. As a general standard practice, the source should be able to compile, build and package with maven tool.

I've developed a proof of concept of your requirements as follows: 1. Set up a mvn spring boot project 2. Set up a sample in memory database with two simple tables and some sample data. 3. Exposed the database entities as a restful web service using spring jpa (for verification of data). 4. Written a web controller that exposes the database meta data required as json My remaining task is to add the constraint information, but currently most of the database, table and table column data is being served to spec. I estimate a first cut can be delivered in 1 day. I have a couple of questions also; 1. You say you need a Restful API - I have assumed you only need READ access to the DB meta data for this job. It is not required to implement Create, Update or Delete operations - is this correct? 2. Regarding the password field: I have assumed a single admin username and password is stored on the server which can be returned. However, I assume I'm not required to to show a user and password determined by user making the Web request - this would require addition time and more detailed requirements on your part to define the user auth design. In a production system this might not be a good idea anyway (showing a password in plain text). If you would like some verification of the current state of my proof of concept, I can send you screen shots of the current json output. Look forward your response, Cheers, Cam ps. this is my first bid on Freelancer :)