Building Sustainable Microservices with bisslog python
The Problem: When Microservices Become a Mess Building a modern microservice in Python seems easy — until it isn’t. As the service grows, you start noticing problems: 🧱 Business logic tightly...
Bisslog
A disciplined architecture for building sustainable microservices.
Why Bisslog?
Frameworks promise simplicity — until they start dictating how your domain logic should behave.
Bisslog is not a framework. It’s a lightweight, dependency-free core library that helps you organize your backend code around business rules, not around frameworks, plugins, or adapters.
It brings architectural clarity to Python microservices by:
- Enforcing separation of concerns through well-defined ports.
- Making your use cases framework-agnostic.
- Encouraging metadata-driven definitions.
- Keeping the domain code pure, testable, and portable.
If you’ve ever asked “Where should this logic go?” — Bisslog gives you the answer.
What does it look like?
Each Bisslog-based application is organized around core use cases that define what the system does, completely separated from how it’s triggered (e.g., HTTP, EventBridge, Lambda, CLI) or where data is stored (MongoDB, PostgreSQL, S3, etc).
No decorators leaking HTTP context into your domain. No global objects. No magic.
Read more
📖 The Myth of Lightweight Frameworks – Why convenience becomes coupling.
📘 Towards Sustainable Microservice Architecture – The theory behind Bisslog’s design.
Bisslog Adapter Catalog: Organized by Purpose
The bisslog ecosystem supports clean, sustainable service architecture through the use of adapters that encapsulate infrastructure concerns. These adapters enable integration with external systems ...
🧩 Guide to Creating Database Adapters in bisslog
This guide shows how to implement database adapters in bisslog-based projects using the Ports and Adapters approach to build sustainable and decoupled architectures. 📁 Project Structure src/ ├─...
Bisslog isn't a dependency — it's a mindset
What if your architecture didn’t depend on a library — but simply followed a consistent way of thinking? That’s the philosophy behind bisslog. At its core, bisslog is not a framework, not a runti...