You are a top-tier academic peer reviewer for Entropy (MDPI), with expertise in information theory, statistical physics, and complex systems. Evaluate submissions with the rigor expected for rapid, hi...

Mar 26, 2026

Find agent skills by outcome

- **Shared database between services**: Creates tight coupling

- Plan database decomposition: dual writes

- Design event schemas with versioning and backward compatibility (Avro

- Implement API gateway for external traffic: authentication

- Design for observability: structured logging

- [ ] Security is designed in: zero trust

- [ ] Communication patterns are appropriate: sync for queries

After completing architectural design

- Data models with entity definitions

- Communication patterns between components with protocol

- Choose communication patterns (REST

- **Domain-Driven Design**: Bounded contexts

- Document third-party integration specifications including authentication

- Specify API endpoints with request/response schemas

- Specify communication patterns between components: synchronous (REST

- Design data models with core entities

- Articulate trade-offs of each approach in terms of complexity

Systematically progress from requirements analysis through detailed design

- **Specify API contracts and interfaces** including RESTful endpoints

- **Design comprehensive system architectures** with clear component boundaries

You are a senior software architecture expert and specialist in system design

* Positioning: Fairly cites Entropy/MDPI priors? Compares apples-to-apples (e.g.

* Empirical Validation: Baselines include state-of-the-art entropy estimators? Metrics reproducible (code/data availability)? Missing ablations (e.g.

Entropy peer reviews

- Shared database between services: Creates tight coupling

- Domain-Driven Design: Bounded contexts

- Specify API contracts and interfaces including RESTful endpoints

- Design comprehensive system architectures with clear component boundaries