Define a user story in the business transaction DSL
The business transaction DSL.
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.
- 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
- 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.
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)
This code style allow you clearly separate actual business scenario from implementation details.
If you have an issue with any version of the library, you can apply for a paid enterprise support contract. This will guarantee you that no breaking changes will happen to you. No matter how old version you're using at the moment. All necessary features and bug fixes will be backported in a way that serves your needs.
Please contact email@example.com if you're interested in it.
Stories library is offered under the two clause BSD license.
— ⭐️ —
The stories library is part of the SOLID python family.
Release history Release notifications | RSS feed
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size stories-4.0.0-py3-none-any.whl (28.1 kB)||File type Wheel||Python version py3||Upload date||Hashes View|
|Filename, size stories-4.0.0.tar.gz (19.9 kB)||File type Source||Python version None||Upload date||Hashes View|