|
1 | 1 | --- |
2 | | -layout: default |
| 2 | +layout: home |
3 | 3 | currentMenu: home |
4 | 4 | --- |
5 | 5 |
|
6 | | -# Welcome |
| 6 | +## Why should you care? |
| 7 | +__InEngine.NET__ is a set of .NET packages that allows for the creation of a code-centric data integration and asynchronous job scheduling server. |
| 8 | +Integration jobs are created in code, making them flexible and testable. |
7 | 9 |
|
8 | | -__InEngine.NET__ is a set of .NET packages, created by [Ethan Hann](http://ethanhann.com), that allows for the |
9 | | -creation of a code-centric data integration and asynchronous job scheduling server. |
10 | | - |
11 | | -- [NuGet Package](https://www.nuget.org/packages/IntegrationEngine) |
12 | | -- [GitHub Project](https://github.com/ethanhann/InEngine.NET) |
13 | | - |
14 | | -### Why should you care? |
15 | | - |
16 | | -Data integration is a common task when working in a large or medium enterprise environment. |
17 | | -Data integration servers take data from a data source, transform it (or not), and put it somewhere. |
18 | | -__InEngine.NET__ can allow you to do that and more in a programmatic manner. |
19 | | - |
20 | | -There are several existing full-featured data integration server products on the market. |
21 | | -These products do not work in a way software developers are comfortable with. |
| 10 | +Existing commercial data integration server products do not work in a way software developers are comfortable with. |
22 | 11 | They provide a drag-and-drop GUI application for implementing a data integration. |
23 | | -This sounds appealing on the surface, but such GUIs are often clunky and slow. |
24 | | -Additionally, existing products do not provide a testable way to build integrations and detect when they stop functioning. |
| 12 | +This sounds appealing, but such GUIs are often clunky and slow. |
| 13 | +Additionally, such products do not provide a testable way to build integrations and detect when they stop functioning. |
25 | 14 | This is a major issue as data integrations are fragile by nature. |
26 | 15 |
|
27 | 16 | In contrast, a developer would prefer fine-grained, programmatic access to the data they are querying, transforming, and persisting. |
28 | 17 | A developer would also like to be able to test their integrations to ensure their continued operation. |
29 | | -__InEngine.NET__ provides this. |
| 18 | +__InEngine.NET__ allows this. |
30 | 19 |
|
31 | | -### How does it work? |
32 | | - |
33 | | -1. __InEngine.NET__ is a library. In order to use the library a developer must create a .NET console or service |
34 | | -project that instantiates and initializes an instance of _IntegrationEngine.EngineHost_. |
35 | | -1. Integration jobs that implement _IntegrationEngine.Model.IIntegrationJob_ (located in an assembly passed to _EngineHost_) are loaded. |
36 | | -1. Integration jobs are scheduled by posting a request to the [InEngine.NET Web API](web-api.html). |
37 | | -1. When a job is triggered a message is added to the message queue, defined in [IntegrationEngine.json](configuration.html), that indicates which job to run. |
38 | | -1. When a message is detected, the __InEngine.NET__ job runner plucks the message from the queue and runs the job encoded within it. |
| 20 | +## What is the license? |
| 21 | +[MIT](https://github.com/ethanhann/InEngine.NET/blob/master/LICENSE) |
39 | 22 |
|
40 | | -<img src="https://docs.google.com/drawings/d/1dEmGlhfDWhljOjWIn7ttuNQxfY1N_dXOaHxNOLpgV9U/pub?w=960&h=720" alt="IntegrationEngine Job Processing Diagram" /> |
| 23 | +## How much does it cost? |
| 24 | +It's free! |
41 | 25 |
|
42 | | -### How is this software licensed? |
43 | | -[MIT](https://github.com/ethanhann/InEngine.NET/blob/master/LICENSE) |
| 26 | +## Where can I get this fantastic software? |
| 27 | +The software is released as a set of [NuGet Packages](https://www.nuget.org/packages/IntegrationEngine). |
| 28 | + |
| 29 | +The source code is hosted on [GitHub](https://github.com/ethanhann/InEngine.NET). |
0 commit comments