There are situations in which the use of products such as a CMS or e-commerce system does not make sense.
This is usually the case with special USP development. While it’s true that products we use can be successfully customised, this is not economical in specific cases. The decision for or against individual development essentially depends on the number and depth of the necessary adjustments.
Individual solutions have gained a reputation for being expensive and time-consuming; in addition to developing features from the ground up, which are often already available in commercially available products, additional maintenance and support has to be considered.
When done correctly, however, costs and effort can result in a high ROI. Our customers are thus able to develop their existing strengths and competitive advantages even more effectively and sustainably by way of a perfect image in the digital world. We always check the cost-effectiveness of a product adaptation as part of our consultation.
Essential success factors include choosing the correct procedure and previous experience with this type of project. Agile software development and our extensive experience with up-to-date frameworks and technologies ensure a successful project for our customers.
Combining several systems (best of breed) is an increasingly common example of individualised development. Our partners’ products usually cover many of our customers’ needs. However, competitive pressure and the need to differentiate from the competition are so great that a single product doesn’t suffice. The example of content-driven e-commerce (content commerce) makes that very clear. There are products well-suited for both disciplines—CMS for content on the one hand, and shops for commerce on the other hand. We have specialised in merging these products in order to capitalise on strengths such as efficiency and speed. We have been developing components and modules for years, in close cooperation with manufacturers, in order to link these systems and combine the strengths of each. One striking example along these lines would be an e-commerce search engine that uses content from multiple systems. This is how we guarantee the best possible user experience for our customers’ customers.
We are constantly combining systems and frameworks with modern software architectures. Data is decoupled via an enterprise service bus (e.g. though Mule or Camel in combination with Active MQ), data is provided via the RESTful web service for the front-end and a full-text search with all the advantages of ElasticSearch is guaranteed.
Thanks to our many years of experience with modular software, modern approaches to microservices creation have become old habit. In order for these services to go live quickly, a high degree of automation is required. We use container technologies like Docker in conjunction with Jenkins. When setting up the development environment, our developers keep in mind tools for provisioning servers such as Ansible, and these are put to use in a great many places.
Bringing artefacts automatically into production requires high software quality. We guarantee this by way of a very high test threshold. In addition to unit tests and integration tests, we also carry out performance tests (jMeter or Gatling) at an early stage, in order to test the system early with respect to non-functional specifications. We begin regressions with meaningful web tests. Automated deployment becomes expedient and professionally possible only by means of this multi-layered safety net.
Microservice systems also have to be monitored and resiliently implemented. That means that if one of the services fails, the system must remain functional with respect to the customer until the failed service has been restored, usually via automation. diva-e uses frameworks such as Netflix Stack in projects.
Many of our projects are also operated directly in the cloud. Depending on the project, proprietary services such as Amazon Web Services or Microsoft Azure Cloud Services are used.
To meet these demands, we often use the very flexible and widely used Spring Framework. Our developers are also proficient in dealing with Java Enterprise environments, but we encounter these technologies less and less and they are increasingly being replaced by lightweight microservices.
News, references and more
Gutes Doppel: UX Design und Scrum
Fachbericht über die Integration von User Experience in den Scrum-Prozess