Define a user story in the business transaction DSL
Project description
Stories
The business transaction DSL.
Documentation | Source Code | Task Tracker
stories
is a business transaction DSL. It provides a simple way to define a
complex business transaction that includes processing over many steps and by
many different objects. It makes error handling a primary concern by taking a
“Railway Oriented Programming” approach
to capturing and returning errors from any step in the transaction.
Pros
- Define a user story in the business transaction DSL.
- Separate state, implementation and specification.
- Clean flow in the source code.
- Separate step implementation.
- Each step knows nothing about a neighbor.
- Easy reuse of code.
- Allows to instrument code easily.
- Explicit data contracts and relations in code.
- Data store independent.
- Catch errors when they occur.
- Not when they propagate to exception.
stories
is based on the following ideas:
- A business transaction is a series of operations where any can fail and stop the processing.
- A business transaction can describe its steps on an abstract level without being coupled to any details about how individual operations work.
- A business transaction doesn’t have any state.
- Each operation shouldn’t accumulate state, instead it should receive an input and return an output without causing any side-effects.
- The only interface of an operation is
ctx
. - Each operation provides a meaningful piece of functionality and can be reused.
- Errors in any operation should be easily caught and handled as part of the normal application flow.
Example
stories
provide a simple way to define a complex business scenario that
include many processing steps.
>>> from stories import story, arguments, Success, Failure, Result
>>> from app.repositories import load_category, load_profile, create_subscription
>>> class Subscribe:
...
... @story
... @arguments('category_id', 'profile_id')
... def buy(I):
...
... I.find_category
... I.find_profile
... I.check_balance
... I.persist_subscription
... I.show_subscription
...
... def find_category(self, ctx):
...
... ctx.category = load_category(ctx.category_id)
... return Success()
...
... def find_profile(self, ctx):
...
... ctx.profile = load_profile(ctx.profile_id)
... return Success()
...
... def check_balance(self, ctx):
...
... if ctx.category.cost < ctx.profile.balance:
... return Success()
... else:
... return Failure()
...
... def persist_subscription(self, ctx):
...
... ctx.subscription = create_subscription(category=ctx.category, profile=ctx.profile)
... return Success()
...
... def show_subscription(self, ctx):
...
... return Result(ctx.subscription)
>>> Subscribe().buy(category_id=1, profile_id=1)
Subscription(primary_key=8)
>>> import asyncio
>>> from stories import story, arguments, Success, Failure, Result
>>> from aioapp.repositories import load_category, load_profile, create_subscription
>>> class Subscribe:
...
... @story
... @arguments('category_id', 'profile_id')
... def buy(I):
...
... I.find_category
... I.find_profile
... I.check_balance
... I.persist_subscription
... I.show_subscription
...
... async def find_category(self, ctx):
...
... ctx.category = await load_category(ctx.category_id)
... return Success()
...
... async def find_profile(self, ctx):
...
... ctx.profile = await load_profile(ctx.profile_id)
... return Success()
...
... async def check_balance(self, ctx):
...
... if ctx.category.cost < ctx.profile.balance:
... return Success()
... else:
... return Failure()
...
... async def persist_subscription(self, ctx):
...
... ctx.subscription = await create_subscription(category=ctx.category, profile=ctx.profile)
... return Success()
...
... async def show_subscription(self, ctx):
...
... return Result(ctx.subscription)
>>> asyncio.run(Subscribe().buy(category_id=1, profile_id=1))
Subscription(primary_key=9)
This code style allow you clearly separate actual business scenario from implementation details.
Questions
If you have any questions, feel free to create an issue in our Task Tracker. We have the question label exactly for this purpose.
License
Stories library is offered under the two clause BSD license.
— ⭐️ —
The stories library is part of the SOLID python family.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Hashes for stories-1.0.2-py2.py3-none-any.whl
Algorithm | Hash digest | |
---|---|---|
SHA256 | ed3baff24bb65033873862d33f7b8ba316fd2c4a7f5838bb7dc7fff39aa57ab6 |
|
MD5 | 0ed15ed1d62ccf39324094e19b8bd27f |
|
BLAKE2b-256 | 95993dd3306a753b48a2f6990229b9b0c3e7942adec727f761a016be0897bda8 |