Infrastructure Program

networkinf-thumb

Maybe not as spectacular as the other projects, but not less important, is the Infrastructure Program. It is the oldest, and most stable of all projects, that influences all other. The major goals is the extension and adaption of the current infrastructure (e.g. servers, domains, developing environments, project dependent equipment, …). Under the domain of Networld this infrastructure is maintained and put at disposal for all sub-projects.

Why is this a separate project?

One reason that the Infrastructure Program is a separate project is that the other projects developed by Networld have changed frequently in the past, but the infrastructure stays always the same (at least the basic one, for example the servers). Another reason is that if there are a few small projects it makes from a business perspective sense to share an underlying infrastructure to save costs. Specially if the project leader is always the same person and the team overlaps.

How does the infrastructure look like?

For obvious reason you do not receive a full insight in our whole infrastructure, but the following picture should give you an example how Networld looks under the hood. It shows the server used by the Sigimera project. It consists of one physical server that are split into three virtual server that handle different steps of the business logic.

Could I use the Networld Infrastructure for my own projects?

Unfortunately Networld is a closed ecosystem that is only accessible for our team members. It is possible that this will be changed in the future.



Comments are closed.