redroma/aroma-data-operations

Defines the Data Interfaces and Operations used by the various Aroma Services.

aroma-data-operations's Issues

Remove 'duration' field from 'save' method

Requirement

Remove the 'timeToLive' parameter from

Why

This was only really used for the 'Message' api, and is not used elsewhere.

Implement Memory-based EncryptedPasswordRepository

Rewrite using `NamedParametersJdbcTemplate`

Requirement

Swap out the simplistic JDBC Templates currently being used in exchange for the NamedParameter version.

Why

It makes the code more tolerant to failure and more flexible to use key-value based matching, instead of position-based matching. It also noticeably simplifies testing.

Remove `save` function from Serializer

Requirement

Simplify the DatabaseSerializer so that it is only responsible for deserializing an object from a Result Set.
This will make the DatabaseSerializer a simple extension of a JDBC RowMapper

Why

There have been at least 2 exceptionally cases where the save() function could not be used. That is because the save() function is currently designed to take in only one Thrift object at a time, whereas some operations may need a couplet of objects. It makes sense to move this logic back into the individual Repositories.

Extract Guice code to Alchemy-Kotlin

Requirements

Create an Alchemy-Kotlin Library and extract the guice code there.

Why

This is code that can be shared across multiple projects. It is also something that can be begin Alchemy's transition into Kotlin.

Rewrite `SQLMessageRepository` in Kotlin

Requirement

Rewrite the SQLMessageRepository class in Kotlin.

Why

Kotlin is the language of choice and the defacto language going forward.

Implement Cassandra-backed EncryptedPasswordRepository