Allowing:
text search
tag filter
author id filter

Create endpoint for exposing user profile informationn

Create endpoint for fetching a full reader chapter

Some buisness considerations that applies for chapter price:

• It could be free (i.e. an introduction chapter)

Create endpoint for exposing reader books

Replicate book published and book updated domain events into reader library context

Create reader library context and database boilerplate

Create an endpoint for completing a pending payment

Both, JpaUserRepository and JpaUserCredentialsRepository, are lacking of integration tests.

Only a book in a In progress but no visible status could be deleted, since in other statutes a book could be already bought by readers

Create an endpoint for exposing complete payments of a reader

Create an endpoint (using spring security) for logging in users. Furthermore I need to add all the boilerplate code for springboot to create and configure spring security

A book could be in some of following statuses:

• Finished: author finished this book and it is ready for a whole reading
• Visible in progress: author is currently writing the book and set a percentage of completion
• In progress but not visible: same as visible in progress but author does not want to users see this book yet. So its chapters are not buyable.

When a book is completed or finished? When author has no draft chapters and sets the percentage of completion to 100%

When a book is created always begin with a 0% of completion percentage and has no chapters and the status is In progress but not visible

In order to be able of identifying authenticated users we need to decode and validate JWT on every request that enter in application with the token.

Jest client only support up to 6.x. Change in total count of ES7.X breaks the latests jest client

The response should include information about the book and the chapters (excluding chapter content).

A book should only be returned if it is visible, otherwise requester must be the book author in order to see the book.

Furthermore, only chapters published will be visible unless requester is the book author

Make async domain bus event

Add an endpoint for updating completion percentage of a book:

• the completion percentage can increase or decrease but never be greater than 100 or smaller than 0.
• if completion percentage is updated to 100, then the book is finished

Furthermore, we need to split concept of status into status and visibility. A book could be finished but in a restricted (or even null) visibility.

Book statuses: IN PROGRESS - FINISHED
Visibility: NULL - RESTRICTED - VISIBLE

Finally, this new endpoint should follow REST standard with a PATCH request for partially update the book resource

As a user
I want to be able of logging in application
So a new "authentication" context should be created and credentials (from domain event) should be stored in database (probably in a new schema for this new context.

As an author
I want to create an empty book with some basic information (title, excerpt, and tags)
in order to be able of add some chapters later

Create a new endpoint for exposing the author books

Currently an user just could update the completion percentage, but may need to update other things like title, summary, cover, or even visibility

Persist book tags in database using vladmihalcea's hibernate extensions

MUST include chapter content

By the moment only for book author. Later chapter buyers (when buy process is complete)

Prefix all endpoints with the context which they belong in order to avoid endpoints collisions

Create endpoint for fetching books info in bulk

This endpoint should be something like:

POST /readers/{readerId}/payments
{
"book": "id",
"chapter": "id",
}

and should return a payment id (which internally should be the stripe checkout session

Replicate chapter published and chapter updated domain events into reader library context

Add order and excerpt concepts to chapter

Same as it happens with the book, a chapter could only be deleted if its status is draft. Otherwise the chapter could be already bought by users.

Full Name
Photo
Website

A chapter can be updated regardless its status (draft or published). But all readers that have bought this chapter (or the whole book) will access always to the latest version of the chapter.

A writer only will be able of updating title and content of the chapter.

Replicate basic user info in search context

Incorporate following concepts to chapter:

Title
Content: with no more than 10000 words
Num of words
Last modification

Furthermore, a chapter could be in a draft status, which would mean that is not buyable in other context, maybe neither it should appear in an index, etc..

A chapter is always created in a draft status at beginning, only when author mark it as ready is "published".

Some business considerations that applies for book price:

• Could be free

Create endpoint for exposing reader book by id

A chapter will never change its status from published to draft, but it should change from draft to published in order to be reachable from readers.

This endpoint should be, as all of the application, idempotent, so whenever a chapter is already marked as published, it should return OK.

Replicate in search context book info (aggregating with author info) and index to elasticsearch

Add swagger for documenting API

Returns a HTTP 409 status code for duplicated username/email error instead a HTTP 500

Subscribe to PaymentCompleted domain event

If a chapter of this book has been previously acquired, the book will replace previously buy

PUT readers/{readerId}/books/{bookId}/chapters/{chapterId}

It should save this new chapter as a partially book acquisition with simply the given chapter

Probably modeled as a ReaderBook sealed class: ReaderWholeBook ReaderPartialBook

Create endpoint in reader library for fetching information about a book