eventcloud | Sample SaaS Event Management Application | Microservice library

Firstly, what's the difference between MultiTenancySides.Host and MultitenancySides.Tenant?

MultiTenancySides.Host → can only be assigned to Host users (user.TenantId == null).

MultiTenancySides.Tenant → can only be assigned to Tenant users (user.TenantId != null).

Secondly, how [AbpAuthorize] differs from [AbpAuthorize(PermissionNames.Pages_Tenants)]?

[AbpAuthorize] → user is logged in.

[AbpAuthorize(PermissionNames.Pages_Tenants)] → user is logged in and has that permission.

Here are my answers:

1-) Event is being created with a static factory method. There are 2 ways to create an entity in Domain Driven Design.

1. Creating with static factory methods: It's a convenient way of creating business entities. And this method is being used in EventCloud. The only downside of this method is it's static! If your entity is holding state it's not good for testability. But there are 3 advantages of this approach;
   1. They have names: for example Event.CreatePublicEvent(), Create.PrivateEvent()
   2. They can cache: You can cache them in a private static HashSet or Dictionary.
   3. They can subtype.

2. Creating with a constructor: If you have only one constructor then creating an object through its public constructor is the most convenient approach in Domain Driven Design. As long as you make parameterless constructor protected or private. Besides, an entity should be responsible for its own data integrity and validity so you have to set all business related public properties as private setter and you should allow them to change through public methods.

   Further information, see https://www.yegor256.com/2017/11/14/static-factory-methods.html

2-) EventManager is a domain service that is used for business logic. And Event.Create() is being used in the EventAppService class. Click here to see where exactly is being executed. Even Event.Create() method consists of a single line of code but it's open for extension.

I hope that will be useful ;)

Happy coding...

The issue has been solved.

The reason of this issue happened is because I use a framework that cause this situation happened. The framework is included a transaction at starting, so what I need to do is disable the transaction of the framework then the issue is solved.

The framework that I'm using is ASP.NET Zero