🚀 fastship-py
uv add fastship-py
uv add "fastship-py[sqlalchemy]" # SQLAlchemy アダプタも使う場合
📚 How To
💾 Persistence
💾 テーブルクラス ( SQLAlchemy ) の実装
〇〇.port.adapter.persistence.repository.sqlalchemy.user.driver.users_table_row.py
from sqlalchemy import String
from sqlalchemy.orm import Mapped, mapped_column
# NOTE: テーブルクラスは `DataBase` を継承して作ること
from fastship.common.port.adapter.persistence.sqlalchemy import DataBase
class UsersTableRow(DataBase):
__tablename__ = "users"
id: Mapped[str] = mapped_column(String(36), primary_key=True)
name: Mapped[str] = mapped_column(String(50), index=True) # index 名は ix_users_name
〇〇.port.adapter.persistence.repository.sqlalchemy.user.driver.__init__.py
from .users_table_row import UsersTableRow
# 他のテーブルクラス
テーブルクラスを足したら、そのモジュールの tables にドライバーモジュールのパスを足す
class 〇〇(AppModule):
@property
@override
def tables(self) -> list[str]:
return ["〇〇.port.adapter.persistence.repository.sqlalchemy.user.driver"]
🚚 マイグレーション (Alembic)
事前にマイグレーション用のパッケージを生成
uv add alembic
uv run alembic init migration
migration/env.py:
# alembic init の生成物から、target_metadata = None をこの 3 行に差し替える
from fastship.migration import load_metadata
from core import Backend # 全モジュールを束ねた CompositeModule
target_metadata = load_metadata(Backend())
🔀 リードレプリカへの読み書き振り分け (SQLAlchemy)
接続先はインフラが環境変数で注入する (Secret Manager の値は実行基盤で環境変数として公開する)。アプリ側では設定しない。
| 環境変数 | 内容 |
|---|---|
DATABASE_WRITER_URL |
プライマリ。必須 |
DATABASE_READER_URL |
リードレプリカ (Read Pool のエンドポイント)。未設定ならすべてプライマリへ送る |
from fastship.common.port.adapter.persistence.sqlalchemy import SQLAlchemyUnitOfWork
unit_of_work = SQLAlchemyUnitOfWork.from_settings(pool_pre_ping=True)
トランザクション (unit_of_work.session()) は、読み取りも含めてすべてプライマリで実行する。
レプリカの遅延した値を元に更新すると、プライマリの新しい値を上書きしてしまう (lost update) ため。
更新系の生 SQL (text()) もここで実行する。
トランザクション外の読み取り (unit_of_work.query()) は、以下の規則でリーダーとライターに振り分ける。
| クエリ | 送り先 |
|---|---|
読み取り (select() / session.get() / text()) |
リーダー |
書き込み (flush / insert() / update() / delete()) |
ライター |
SELECT ... FOR UPDATE (with_for_update()) |
ライター |
| 一度でもライターへ送ったセッションの以降のクエリ | ライター (書き込み直後に古いデータを読まない) |
session.use_writer() を呼んだ後のクエリ |
ライター (レプリカ遅延を許容できない読み取り) |
with unit_of_work.query() as session:
session.use_writer()
session.get(...)
認可の判定 (無効化された API キー、停止されたユーザー、取り消された権限など) は、レプリカ遅延の間に
古い状態で許可しないよう、session.use_writer() を呼んでプライマリから読むこと。
Read Pool のノード数を増減しても、エンドポイントは変わらないためアプリ側の変更は要らない。
SessionPreparer (RLS の SET LOCAL など) は、振り分け先のコネクションそれぞれに適用される。
🛠️ Other
📦 DI コンテナ
登録方法:
from sqlalchemy import create_engine
from fastship.common.application import UnitOfWork
from fastship.common.port.adapter.persistence.inmem import InMemUnitOfWork
from fastship.common.port.adapter.persistence.sqlalchemy import SQLAlchemyUnitOfWork
from fastship.di import DI, DIContainer
engine = create_engine("postgresql+psycopg://...")
DIContainer.instance().register(
DI.of(UnitOfWork, {"InMem": InMemUnitOfWork()}, SQLAlchemyUnitOfWork(engine)),
)
利用方法:
from fastship.di import DI, DIContainer
# `DI_FOR_PY=InMem` なら InMemUnitOfWork のインタンスを取得
# `DI_FOR_PY=` なら SQLAlchemyUnitOfWork のインタンスを取得
unit_of_work = DIContainer.instance().resolve(UnitOfWork)
from injector import inject
class 〇〇ApplicationService:
@inject
def __init__(self, 〇〇_repository: 〇〇Repository) -> None: ...
from fastship.common.domain.model import DomainRegistry
〇〇_repository = DomainRegistry.resolve(〇〇Repository)
Metadata
Release files for fastship-py 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| fastship_py-0.4.0.tar.gz | 90.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fastship_py-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 146.0 kB
Release files / fastship_py-0.4.0.tar.gz
| Download URL | fastship_py-0.4.0.tar.gz |
|---|---|
| Size | 90.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4f9515be4313ce1e0927b944fa83f86c3a97acead3e96cd65321bcae3aa64b27
|
|
BLAKE2b-256 checksum How to use checksums |
ebb19abe8517a3744001f2656d1b0a02176026881317a323f8500aea5b65ee4b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.
Transparency logRelease files / fastship_py-0.4.0-py3-none-any.whl
| Download URL | fastship_py-0.4.0-py3-none-any.whl |
|---|---|
| Size | 55.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a16b67c8d3267741febc85e4b23766f3030dbb5da2cd078052c66e3ff53e53f2
|
|
BLAKE2b-256 checksum How to use checksums |
ba8d6ac36989c4c5e92552002132232f45d0f2c9b35187ebd24f52c1103f31b9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.
Transparency logSecurity for fastship-py 0.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for fastship_py-0.4.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.