GitBook: [master] 2 pages modified

Author: Marleine van Kampen

2.2-setup/properties.md

@@ -6,17 +6,17 @@ The following table gives a complete list of all the configuration properties av
 
 | Name | Default value | Type | Description |
 | :--- | :--- | :--- | :--- |
-| server.port | 8024 | Integer | The Http Server port |
-| axoniq.axonserver.name |  | String | Node name of this Axon Server node, if not set defaults to the hostname. |
-| axoniq.axonserver.port | 8124 | Integer | gRPC port for Axon Server |
-| axoniq.axonserver.internal-port | 8224 | Integer | gRPC port for communication between Axon Server nodes |
-| axoniq.axonserver.hostname |  | String | Hostname of this node as communicated to clients, defaults to the result of hostname command |
-| axoniq.axonserver.internal-hostname |  | String | Hostname as communicated to other nodes of the cluster. Defaults to hostname. |
-| axoniq.axonserver.domain |  | String | Domain of this node as communicated to clients. Optional, if set will be appended to the hostname in communication with clients. |
-| axoniq.axonserver.internal-domain |  | String | Domain as communicated to other nodes of the cluster. Optional, if not set, it will use the domain value. |
-| axoniq.axonserver.accesscontrol.enabled | false | Boolean | Access control active |
-| axoniq.axonserver.accesscontrol.cache-ttl | 30000 | Long | Milliseconds that authenticated tokens will be cached |
-| axoniq.axonserver.accesscontrol.internal-token |  | String | Token to add to Axon Server internal cluster message |
+| `server.port` | 8024 | Integer | The Http Server port |
+| `axoniq.axonserver.name` |  | String | Node name of this Axon Server node, if not set defaults to the hostname. |
+| `axoniq.axonserver.port` | 8124 | Integer | gRPC port for Axon Server |
+| `axoniq.axonserver.internal-port` | 8224 | Integer | gRPC port for communication between Axon Server nodes |
+| `axoniq.axonserver.hostname` |  | String | Hostname of this node as communicated to clients, defaults to the result of hostname command |
+| `axoniq.axonserver.internal-hostname` |  | String | Hostname as communicated to other nodes of the cluster. Defaults to hostname. |
+| `axoniq.axonserver.domain` |  | String | Domain of this node as communicated to clients. Optional, if set will be appended to the hostname in communication with clients. |
+| `axoniq.axonserver.internal-domain` |  | String | Domain as communicated to other nodes of the cluster. Optional, if not set, it will use the domain value. |
+| `axoniq.axonserver.accesscontrol.enabled` | false | Boolean | Access control active |
+| `axoniq.axonserver.accesscontrol.cache-ttl` | 30000 | Long | Milliseconds that authenticated tokens will be cached |
+| `axoniq.axonserver.accesscontrol.internal-token` |  | String | Token to add to Axon Server internal cluster message |
 | axoniq.axonserver.accesscontrol.token |  | String | Token expected from client requests \[Developer edition only\] |
 | axoniq.axonserver.cluster.enabled | false | Boolean | Cluster enabled |
 | axoniq.axonserver.cluster.connection-check-delay | 1000 | Long | Delay before the first run of the connection checker \(in ms.\) |

architecture-overview.md

@@ -1,13 +1,14 @@
 # Architecture overview
 
-The Axon platform consists of two parts: Axon Framework and Axon Server. 
+The Axon platform consists of two parts: Axon Framework and Axon Server.
 
-Axon Framework is a Java library. It gets included in your custom Java (Kotlin, Scala) application as a dependency, typically through Maven. As a library, it helps you write applications using CQRS, DDD and event sourcing principles. Axon Framework has a concept of location transparency: couplings are realized by exchange of command, event and query messages over bus interfaces.
+Axon Framework is a Java library. It gets included in your custom Java \(Kotlin, Scala\) application as a dependency, typically through Maven. As a library, it helps you write applications using CQRS, DDD and event sourcing principles. Axon Framework has a concept of location transparency: couplings are realized by exchange of command, event and query messages over bus interfaces.
 
-Axon Server is a stand-alone server runtime that helps to run Axon applications at any scale. It can store many billions of events without running into the problems that relational databases have at that scale. And it will correctly route all types of messages between hundreds of application instances, without requiring any configuration: it will discover the correct routing automatically.   
+Axon Server is a stand-alone server runtime that helps to run Axon applications at any scale. It can store many billions of events without running into the problems that relational databases have at that scale. And it will correctly route all types of messages between hundreds of application instances, without requiring any configuration: it will discover the correct routing automatically.
 
 ![Architecture overview of the Axon platform](.gitbook/assets/axon4architecture.png)
 
 The complete Axon platform is the easiest way to build a microservices system in Java, allowing developers to focus on the business functionality and let Axon take care of the rest.
 
-Since Axon 4.0, Axon Framework by default assumes the presence of Axon Server. Nevertheless, it is still possible to run Axon Framework 4.0-based applications without Axon Server, just like it was the case in Axon Framework before 4.0. An RDBMS or Mongo can be used as an event store, and commands can be distributed using JGroups or Spring Cloud routing (or, you can build a traditional monolith and not use command and query distribution). In practice, these kinds of distributed configurations have shown to be difficult to set up correctly, which is why we created Axon Server and default to using it in Axon 4.0.
+Since Axon 4.0, Axon Framework by default assumes the presence of Axon Server. Nevertheless, it is still possible to run Axon Framework 4.0-based applications without Axon Server, just like it was the case in Axon Framework before 4.0. An RDBMS or Mongo can be used as an event store, and commands can be distributed using JGroups or Spring Cloud routing \(or, you can build a traditional monolith and not use command and query distribution\). In practice, these kinds of distributed configurations have shown to be difficult to set up correctly, which is why created Axon Server and default to using it in Axon 4.0.
+