Difference between revisions of "Contensive 5.0 vs 4.1"
From Contensive Wiki
(→Physical Components=) |
|||
| Line 1: | Line 1: | ||
| − | == | + | The move to Version 5.0 was to |
| + | # Remove all proprietary third party dependencies (paid licenses) | ||
| + | # All code to be open source | ||
| + | # Support an architecture that easily scales out. | ||
| + | |||
| + | ==Structural Components== | ||
| + | |||
| + | The differences are very small. Both are based on the windows... | ||
| + | |||
| + | ==Physical Component Differences== | ||
Contensive Library version 5 has several functional components that make up an application | Contensive Library version 5 has several functional components that make up an application | ||
Revision as of 14:44, 10 November 2016
The move to Version 5.0 was to
- Remove all proprietary third party dependencies (paid licenses)
- All code to be open source
- Support an architecture that easily scales out.
Structural Components
The differences are very small. Both are based on the windows...
Physical Component Differences
Contensive Library version 5 has several functional components that make up an application
- The Client Processor (cp)
- This component (clibCore.dll) is the primary executable on the server. A reference to the assembly in your dotnet project gives you access to the full cp namespace for running addons and routes. It is installed with the setup.
- The client Base Classes (cpBase)
- installed with the setup and is available through NuGet (Contensive.clib). A reference to this assembly is needed to write Contensive Addons.
- The command line utility (clib.exe)
- Used to facilitate installation, setup and maintenance. for example, "clib -n" initializes a new server instance and creates new applications on the instance.
- The windows service (clibService.exe)
- (Optional) The service performs two optional functions. First, it schedules the execution of code (addons) in the background, adding them to an execution queue as needed. Second it kicks off command processes from the front of the queue. This way, on a single server the service can perform all duties and on a multiple server installation, you can have as many background worker processes (workerRoles) as you need and still only need a single task scheduler.
- Sql Server
- Either a local or remote instance of Sql Server. The local instance can be any edition (including the free Sql Express). A remote instance can be an instance of Sql Server, or the AWS RS service (supporting Multi Availability Zones, etc)
- MemCacheD cache cluster
- (Optional) Currently only AWS Elasticache is supported.
- Application Filesystem
- (Optional) A persistent (non ephemeral) file store used to synchronize
