@thisisagile/easy
Advanced tools
Comparing version 1.12.2 to 1.12.3
export * from "./Api"; | ||
export * from "./AxiosProvider"; | ||
export * from "./ContentType"; | ||
export * from "./EasyRequest"; | ||
export * from "./EasyResponse"; | ||
export * from "./HttpStatus"; | ||
export * from "./HttpVerb"; | ||
export * from "./Req"; | ||
export * from "./RequestOptions"; | ||
@@ -9,0 +9,0 @@ export * from "./RequestProvider"; |
@@ -16,6 +16,6 @@ "use strict"; | ||
__exportStar(require("./ContentType"), exports); | ||
__exportStar(require("./EasyRequest"), exports); | ||
__exportStar(require("./EasyResponse"), exports); | ||
__exportStar(require("./HttpStatus"), exports); | ||
__exportStar(require("./HttpVerb"), exports); | ||
__exportStar(require("./Req"), exports); | ||
__exportStar(require("./RequestOptions"), exports); | ||
@@ -22,0 +22,0 @@ __exportStar(require("./RequestProvider"), exports); |
{ | ||
"name": "@thisisagile/easy", | ||
"version": "1.12.2", | ||
"version": "1.12.3", | ||
"description": "Straightforward library for building domain-driven microservice architectures", | ||
@@ -5,0 +5,0 @@ "author": "Sander Hoogendoorn", |
@@ -9,14 +9,25 @@ # easy | ||
This library will include best practices to support building services, such as: | ||
This library will include best and foremost simple practices to support building microservices, based on the following software architecture and patterns: | ||
* Nicely separated into four single-purpose layers, services, process, domain, data. | ||
* Each layer contains single-purpose layer supertype classes. | ||
* In the data layer we use gateways - either to a database, or to other services. | ||
* In the domain layer there are supertypes to model the domain, such as entities, records, value objects and enumerations. | ||
* The domain layer also knows the repository layer supertype, for handling instances of entities and structs. | ||
* The process layer contains use cases, that model your process. | ||
* The services layer has resource as the layer supertype, to model the API exposed. | ||
* Additionally, this library contains utility classes for standardizing e.g. uri's, and ids, constructors, lists, queries, and errors. | ||
* This library will contain a simple validation mechanism, using decorators. | ||
### Architecture | ||
Microservices built with easy have a four layered architecture: services, process, domain, data. Each of the layers serves a single purpose and follows clear patterns and communications. | ||
### Data | ||
It is the responsibility of the classes in the data layer to fetch and deliver data from outside the microservices. This data can come from e.g. a file system, relational and other types of databases (we prefer document databases), or from other services on your domain, or from services outside your domain. Classes performing this function are called gateways. | ||
### Domain | ||
In the domain layer there are supertypes to model the domain, such as entities, records, value objects and enumerations. | ||
The domain layer also knows the repository layer supertype, for handling instances of entities and structs. | ||
### Process | ||
The process layer contains use cases, that model your process. | ||
### Services | ||
The services layer has resource as the layer supertype, to model the API exposed. | ||
### Utilities | ||
Additionally, this library contains utility classes for standardizing e.g. uri's, and ids, constructors, lists, queries, and errors. | ||
This library will contain a simple validation mechanism, using decorators. | ||
We keep this library simple on purpose, extending it using additional libraries and frameworks should be possible simply by embedding their API's. | ||
@@ -26,2 +37,2 @@ | ||
### Please note: we are slowly adding more value to the library, step by step. Most of our additions are useful as such, both it will take some effort for the full architecture to be in place to implement fully working microservices. Please bare with us. | ||
Please note: we are slowly adding more value to the library, step by step. Most of our additions are useful as such, both it will take some effort for the full architecture to be in place to implement fully working microservices. Please bare with us. |
export * from "./Api"; | ||
export * from "./AxiosProvider"; | ||
export * from "./ContentType"; | ||
export * from "./EasyRequest"; | ||
export * from "./EasyResponse"; | ||
export * from "./HttpStatus"; | ||
export * from "./HttpVerb"; | ||
export * from "./Req"; | ||
export * from "./RequestOptions"; | ||
@@ -9,0 +9,0 @@ export * from "./RequestProvider"; |
Sorry, the diff of this file is not supported yet
136423
37
2018