TODO

[hanfak]

Now

• Turn params into a rquest object
• pass request to usecase
• respond with request been processed
• Access query parameters
• bash script to run sql file from bash
• Tests for -- settings -- property reader -- servlet -- webservice -- marshaller -- unmarshaller -- Clear database and reset with primings in @before
• Check dependency inversion is correct
• Check that db query returns an object which implements a domain interface
• check that request retrieved sends a request object with data, that implements a domain interface, to the usecase
• add product, to db and code
• add stock use case
• buy products use cases
• refund products use cases
• -Add status probe-
• Setup docker container -- Bash script to run sql via docker , using path where sql file is running on docker
• Events (immtubale records) -- Store events in db -- workflow validation
• Logging Http request and response via servlet filters ()

[hanfak]

Questions

• Passing a request object (from unmarshalling request from infrastructure) to the usecase as a parameter. Cannot do this as breaks layering rules (inner layers know nothing about out layers). I have used dependency inversion, created an interface Request which is implemented by the request being passed to the usecase. Yet setting the type of the parameter in the usecase method ie Request product instead of ProductAvailabilityRequest product, causes error.

Should I just pass the string (product name) rather than the ProductAvailabilityRequest? How can I get the above problem working? Does it matter that I just pass the object instead of the interface?

[hanfak]

Later stuff

• Setup yatspec Add dictionary Add interesting givens
• webserver builder
• Add Logger ** Create logger factory
• properties change path/host depending on computer or different environment
• Coverage tests (pit)
• setup error and code style tests (findbugs/pmd)
• Add Static anaylsis tests ** Comments must have a 'TODO'
• Use database pooling ie c3po, hiraki
• wiring of dependencies Add singletons (settings) Add different wirings for JDBC ** Third Party
• Extract Database for stock/products/customer to third party service ** Status probe and test for each
• JDBC writer and reader factories DBevents prevent sql secruity issues use a test database for acceptance test to access and to test database
• request object, use httpclient.request (build own req object)
• PACT tests (consumer tests)
• continuous integration with github (Travis) setup database with primiing, and access rights setup tests (esp for yatspec)
• Aggregates for storing events
• concurrency and multiple threads example
• CQRS (separate reader and writers for jdbc)
• Use of TraceyID or equivalent
• Quartz and cron jobs to automate calls to endpoints at specific regular times
• editioning and views using oracle db
• Kubernetes
• Extract business databases to separate services on different containers (ie stock/customer)
• GUI/front end on different container using ember and some hosted on node/sinatra where it consumes this app endpoints
• file stuff??
• set variables depending on environments rather than computer