Use of Open Source components in Abeo. Who we are?. Abeo is the result of the merger between ConsultIT and eScienza Consulting company for systems development and advisory at several levels in the IT-industry Ca 50 employees Ca 55 mill. NOK turnover
PowerPoint Slideshow about 'Use of Open Source components in Abeo' - majed
An Image/Link below is provided (as is) to download presentation
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
As we do not have our own products, Open Source products can function as our toolbox, which we can bring into projects to deliver faster and at a lower cost.
For the customer, we can assume the responsibility for delivering a problem free solution ourselves, rather than blaming problems on a third party – since we have full access to the source code and can correct problems ourselves.
Open Source-products are usually driven by technical needs, and therefore have a tendency to suit us well as technicians.
Our competence in Open Source products can also be of interest for those of our customers wishing to start using Open Source-products internally.
Easy to integrate with other components (for example JBoss)
The Open Source-products we have used function very well as a development platform, we save licensing costs, and we are sure to avoid being tied to a particular commercial platform by using non-standard features.
Our experiences with using Open Source products in production have also been very good.
Newer technologies, such as webservices, are not that well supported.
Good tools for development, maintenance and debugging.
Our experiences with using Open Source components in solutions have been good.
It is usually easy to integrate the components with the rest of the solution.
Many of the components provide more functionality than what is needed, and planned for. However, this extra functionality often proves useful and is used later in the project. If we had made the components ourselves, we would end up using extra time to develop our own mechanisms to provide the similar functionality.
Many of the components require a bit more effort to understand.
Easy to extend with our own functionality – access to the source code has been key here!
Some problems can be difficult to solve, access to the source code to see what is really happening has been very useful.