Paulovich.Caju 0.4.0

$ dotnet new -i Paulovich.Caju::0.4.0
$ dotnet new clean

It generates a .NET Solution with a layered backend (Domain - Application - Infrastructure - UI) based on the Clean Architecture Style.

There is a newer version of this package available.
See the version list below for details.
dotnet new --install Paulovich.Caju::0.4.0
This package contains a .NET Core Template Package you can call from the shell/command line.

Caju: .NET apps with awesome architectures! Gitter

Service Template to help you build evolvable and maintainable applications. It follows the principles from the Clean Architecture book and built on Domain-Driven Design. This tool increases productivity on developing your next microservices.

Generate your own awesome Back-end!

To generate your own awesome .NET Back-end simple run:

dotnet new -i Paulovich.Caju::0.4.0
dotnet new clean

The Architecture Styles

We prevent our software to be coupled from technology details like User Interface, Data Access frameworks, Service Bus or Web Servers. And there are some concepts that guided us:

  • Allow an application to equally be driven by users, programs, automated test or batch scripts, and to be developed and tested in isolation from its eventual run-time devices and databases.
  • The SOLID principles are all over the the solution.
  • The software implementation is agnostic from technology, framework, or database. The result is focus on the use cases with input/output ports.
  • Designed around the Business Domain, having Continous Delivery and Independent Deployment.

Sample applications

Run dotnet new -i Paulovich.Caju then try the following commands.

Clean Architecture Solution with basic use cases:

dotnet new clean --use-cases basic

Hexagonal Architecture Solution with all use cases:

dotnet new hexagonal --use-cases full

Empty Event-Sourcing Solution:

dotnet new eventsourcing` --use-cases empty

For olher solution types check out the Caju Samples folder.

Switches

There are switches to generate your awesome application with your needs. Try after dotnet new clean or dotnet new hexagonal or dotnet new eventsourcing:

  • --use-cases full basic readonly none
  • --user-interface webapi none
  • --data-access mongo entityframework dapper none
  • --service-bus kafka none
  • --tips true false
  • --skip-restore true false

Use the switch --help for the complete list of options.

Roadmap

  • Allow to choose the architecture style
  • Allow to choose the built-in
    • Full set of use cases
    • Basic set of use cases
    • Read Only
    • None
  • Allow to choose the data access frameworks
    • MongoDB
    • Dapper
    • Entity Framework Core
    • Azure Cosmos DB
    • NHibernate Core
    • None
  • Allow to choose the UI frameworks
    • Both
    • WebAPI
    • Console
    • None
  • Allow to choose the Service Bus frameworks
    • Kafka
    • Azure Event Bus
    • None
  • Allow to skip the dotnet restore after code generation
  • Allow to include or to remove the architecture tips

Common Issues

Check your .NET Core SDK. Our features are only supported in 2.1.4 SDK or plus.

$ dotnet --version
2.1.4

Caju: .NET apps with awesome architectures! Gitter

Service Template to help you build evolvable and maintainable applications. It follows the principles from the Clean Architecture book and built on Domain-Driven Design. This tool increases productivity on developing your next microservices.

Generate your own awesome Back-end!

To generate your own awesome .NET Back-end simple run:

dotnet new -i Paulovich.Caju::0.4.0
dotnet new clean

The Architecture Styles

We prevent our software to be coupled from technology details like User Interface, Data Access frameworks, Service Bus or Web Servers. And there are some concepts that guided us:

  • Allow an application to equally be driven by users, programs, automated test or batch scripts, and to be developed and tested in isolation from its eventual run-time devices and databases.
  • The SOLID principles are all over the the solution.
  • The software implementation is agnostic from technology, framework, or database. The result is focus on the use cases with input/output ports.
  • Designed around the Business Domain, having Continous Delivery and Independent Deployment.

Sample applications

Run dotnet new -i Paulovich.Caju then try the following commands.

Clean Architecture Solution with basic use cases:

dotnet new clean --use-cases basic

Hexagonal Architecture Solution with all use cases:

dotnet new hexagonal --use-cases full

Empty Event-Sourcing Solution:

dotnet new eventsourcing` --use-cases empty

For olher solution types check out the Caju Samples folder.

Switches

There are switches to generate your awesome application with your needs. Try after dotnet new clean or dotnet new hexagonal or dotnet new eventsourcing:

  • --use-cases full basic readonly none
  • --user-interface webapi none
  • --data-access mongo entityframework dapper none
  • --service-bus kafka none
  • --tips true false
  • --skip-restore true false

Use the switch --help for the complete list of options.

Roadmap

  • Allow to choose the architecture style
  • Allow to choose the built-in
    • Full set of use cases
    • Basic set of use cases
    • Read Only
    • None
  • Allow to choose the data access frameworks
    • MongoDB
    • Dapper
    • Entity Framework Core
    • Azure Cosmos DB
    • NHibernate Core
    • None
  • Allow to choose the UI frameworks
    • Both
    • WebAPI
    • Console
    • None
  • Allow to choose the Service Bus frameworks
    • Kafka
    • Azure Event Bus
    • None
  • Allow to skip the dotnet restore after code generation
  • Allow to include or to remove the architecture tips

Common Issues

Check your .NET Core SDK. Our features are only supported in 2.1.4 SDK or plus.

$ dotnet --version
2.1.4

Release Notes

- Clean, Hexagonal or Event-Sourcing architecture styles
- Entity Framework Core; Dapper; MongoDB Data Access frameworks
- Different sets of use-cases.
- Kafka as service-bus for Event-Sourcing
- WebAPI templates
- Docker images optimized for startup
- Layerd application with Domain, Application, Infrastructure and UI
- Domain-Driven Design (Aggregates, Entities, Value Objects, Commands, Domain Events)
- Serilog Logging

Dependencies

This package has no dependencies.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version History

Version Downloads Last updated
0.7.3 608 9/22/2019
0.7.2 123 9/22/2019
0.7.1 123 9/22/2019
0.7.0 124 9/22/2019
0.6.0 1,741 7/11/2018
0.5.0 532 5/13/2018
0.4.4 379 5/13/2018
0.4.2 499 4/26/2018
0.4.1 325 4/25/2018
0.4.0 479 4/19/2018
0.3.3 369 4/18/2018
0.3.2 364 4/18/2018
0.3.1 403 4/10/2018
0.3.0 398 4/10/2018
0.2.98 373 4/9/2018
0.2.97 368 4/8/2018
0.2.96 374 4/8/2018
0.2.94 525 4/8/2018
0.2.93 512 4/8/2018
0.2.91 495 4/8/2018
0.2.90 509 4/7/2018
0.2.86 488 4/7/2018
0.2.85 383 4/5/2018
0.2.84 397 4/2/2018
Show less