TU Tran

In part 1 and part 2,We know how the order will be created using CQRS pattern.
In real ERP system, there are many other modules need to be updated when new order was created.
For example:
- Inventory module needs to be updated.
- Accounting module also needs to be updated.
- Customer management module needs to be notified in this case.
Let see, How can we implement this in TinyERP [More]

In previous part, we learn how to scale the architecture/ pattern for simple operation (basically CRUD operation). In this article, we will learn how to scale architecture/ pattern for more complex operation. [More]

In this article, we will learn how to switch between the architecture/ pattern when the complexity of the application increased. [More]

In previous post (Basic authentication with OWIN), we know how the authentication can be integrated into TinyERP.

In basic authentication, it was not secure as we need to send username/ password along in header of each request sent to server. Someone can catch and get this credential information.


In this article, we will discuss about another more security authorization. it was called "Token Based Authentication". [More]

In this article, we will discuss briefly on how to perform the basic authentication(username/password) in TinyERP using Owin.

For now, We will not talk about how security was provided by user/password authentication, it was not the purpose of this article.

With basic authentication, client will send user-name/password in each request to server. This is a good point that can let you understand how to integrate authentication into TinyERP as many questions from readers.
[More]

In this article, we will discuss about the number of patterns which can be used for your application.

There are many types of pattern for the simple to complex application as below:

   - Multiple-Tiers

   - Reporting database

   - CQRS

   - CQRS-DDD-ES

   - Microservice

   - Microservice-CQRS-DDD-ES

We will go through one by one briefly [More]

Overview about architecture for enterprise application at basic level [More]

For enterprise system, we may have a huge data, storing this in single database server may lead to some performance problems related to IO. Storing a single big database file was not recommended. [More]

In context of enterprise application, we may need to store data into various type of repositories due to different purpose:

    - Using relational database (such as: MSSQL, ...) for validation data, frequently modified data, ....

    - Using multiple small databases instead of 1 big database in enterprise system. Such as: database for order module, database for product management module, database for customer management module, ....

    - Using NoSQL (such as: MongoDB, RavenDb, ...) for fast reading.

    - Using Elastic for searching data.

We will go through these as below. [More]

This article will help us avoiding performance issues in enterprise application.
CQRS stands for Command Query Responsibility Segregation that was described by Grey Young.
For more information about this, You can search from the internet easily, So in this article, we will not spend time for reinventing the wheel. [More]