Private Software Development Cloud
Due to the recent announcement of the acquisition of GitHub by Microsoft and the (sometimes very emotional) discussions about possible ramifications, it becomes obvious that people, teams or companies use services like GitHub for many different reasons. That is because they all have different prerequisites and requirements; GitHub hosts code for 100% Open Source developers as well as for companies with private repositories only and everything in between.
Risk of vendor lock-in
These days, there always is the “risk” that one of the big players acquires a small company. In situations like that you never know the intentions of the acquireing company. Of course they always say that nothing will change, but history has shown that that is not always the truth. That’s why it is so important to be prepared; that means: stay flexible, independent from a single vendor and in charge of your code; especially when your code is not Open Source.
One way to achieve this is by using Open Source components, because with them you can always be sure that you will at least be able to operate systems yourself; even if a service provider shuts down or changes its conditions.
GitHub compared to Cloudogu EcoSystem
When we get back to the source of the discussion, the acquisition of GitHub, there are many people out there that decided that they want to leave GitHub, because they don’t trust the new owner. The reasons for these decisions are as diverse as the reasons for using GitHub in the first place.
If someone is looking for an alternative, our EcoSystem could be the solution of choice. Of course, the CES is not and will never be, an Open Source community platform like GitHub, but it could be an alternative for teams that want to host their repositories themselves and that need additional functionality, e.g. issue tracker, wiki or static code analysis as well as user and permission management.
Cloudogu EcoSystem already utilizes a large number of best-of-breed Open Source applications that cover the whole software development lifecycle and embeds them in an environment that enriches them with aspects like a SingleSign-on service and simplified navigation. This way it enables teams to easily set up and operate a software development infrastructure that meets the basic needs of modern software development.
The following image shows the software development lifecycle that is supported by the Cloudogu EcoSystem.
Of course, this lifecycle doesn’t mean that the CES is limited to these applications; thanks to the container-based architecture, new applications can be integrated into the CES. Therefore, it is not necessary to change your toolchain, the CES toolchain can be adapted to your needs.
Try the demo
First of all, you could take a quick look at Cloudogu EcoSystem and convince yourself of the functionalities.