2️⃣🔠 useful tips and tricks for implementing domain-driven design in Go

1. Define domain models based on business concepts rather than technical requirements. Focus on the core domain logic.

2. Use repositories and services to isolate domain logic from infrastructure concerns.

3. Leverage interfaces and dependency injection to achieve loose coupling between components.

4. Use custom types rather than primitives to model domain concepts. Add domain-specific behavior.

5. Encapsulate business rules inside domain entities and value objects.

6. Validate invariants and enforce business rules in entity methods.

7. Use the factory pattern to encapsulate complex entity creation logic.

8. Design aggregates to manage consistency boundaries. Reference other aggregates by ID.

9. Implement domain events to maintain state consistency and communicate events to other parts of the system.

10. Use CQRS and command/query separation to simplify queries and prevent side effects.

11. Define explicit domain service interfaces to encapsulate domain logic reuse.

12. Leverage Go's interfaces for ports and adapters to isolate external dependencies.

13. Write tests focused on domain logic. Mock out external dependencies.

14. Refactor towards deeper domain models by pushing more logic into entities.

15. Establish ubiquitous language within code, models, and team communication.

16. Iterate models with domain experts to refine core abstractions.

17. Distill core domains from subdomains. Bound contexts with interfaces.

18. Maintain domain code and models separate from infrastructure code.

19. Implement anti-corruption layers to isolate external models.

20. Document context mappings between bounded contexts and subdomains.

➖➖➖➖➖➖➖➖
🕊 @gopher_academy

🔥Go Style Best Practices

This file documents guidance about how to best apply the Go Style Guide. This guidance is intended for common situations that arise frequently, but may not apply in every circumstance. Where possible, multiple alternative approaches are discussed along with the considerations that go into the decision about when and when not to apply them.

https://google.github.io/styleguide/go/best-practices.html

➖➖➖➖➖➖➖➖
🕊 @gopher_academy

🔥 دورهمی Go 1.21 Overview

بیشتر تغییرات در پیاده‌سازی های Toolchain، runtime و کتابخونه‌های زبان بوده.
که به صورت مختصر موارد زیر هستند:

• Three new built-in functions: min, max, and clear.
• Improved type inference for generic functions.
• Profile Guided Optimization (PGO) feature for faster and more efficient builds.
• New packages for structured logging, slices, maps, and comparison utilities.
• A new port for WebAssembly System Interface (WASI).
• Backward and Forward Language Compatibility

- تاریخ: روز پنجشنبه ۳ شهریور ۱۴۰۲ ساعت ۱۱ تا ۱۲ یک جلسه‌ی آنلاین برگزار می شود.
- برگزار کننده: مهندس حسین زلفی
- محل برگزاری: پلت فرم zoom (اسپانسر GoBridge)


Add to Calendar
Add to Google Calendar
Add to Yahoo Calendar



لینک ورود به جلسه: https://us02web.zoom.us/s/86594571933

آیدی میتینگ:

865 9457 1933

پسورد:
214062

➖➖➖➖➖➖➖➖
🕊 @gopher_academy

⚠️ How to Gracefully Close Channels

Several days ago, I wrote an article which explains the channel rules in Go. That article got many votes on reddit and HN, but there are also some criticisms on Go channel design details.

https://go101.org/article/channel-closing.html

➖➖➖➖➖➖➖➖
🕊 @gopher_academy