Single Sign-On for Spotler Group

Introduction

We have been working with the Spotler Group for over 3 years. After starting work on the Email Editor project, the client invited us to collaborate on the creation of the Single Sign-On system.

Focus

Objective

To create an SSO system that would unify various products of the Spotler Group under a single brand.

Needs

Approach

We started with discovery workshops, during which we received both technical information about the projects that the SSO would cover and a specification of business requirements.

The results of the workshop provided a basis for conducting an extensive review of commercially available SSO solutions. We presented the advantages and disadvantages of each solution to the client’s Steering Group. After selecting a core solution, a draft of the proposed architecture was prepared. Until that time, the process had been supported by our architect, who had already created similar solutions for other clients.

We used lessons learned from previous projects to avoid potential pitfalls. The next step consisted of the implementation, first of the MVP version and then of the testing phase. The verification of the MVP version was conducted simultaneously with the onboarding of the technical support staff, who provided additional feedback on the part of the application responsible for handling user requests.

The next stage involved deploying the solution to the production environment and beginning the onboarding of customers. Throughout the entire process, our team not only improved the solution but also provided assistance to the teams responsible for specific Spotler Group products in integrating with the SSO system.

In managing the work of the development team from ArdentCode, we used the Kanban method. The entire process was supervised by a manager from Spotler.

During the project, we delivered weekly progress reports. Initially, the reports were presented to the Steering Group, and later to the CTO and Head of Product Development at Spotler.

Key changes

Results

Conclusion

SSO enables improved security and therefore helps protect the privacy and safety of Spotler Group users. Ultimately, after the migration has been completed, the system will also enable a reduction in costs related to the maintenance of authentication systems.

Case study of Email Editor – great cooperation

Introduction

Spotler Group is a European provider of digital marketing and communication tools, which helps companies engage customers and enhance their brand experience. The Spotler Group has grown in part by acquiring companies that offer solutions in the MarTech space. As the group expanded, the need for a modern, scalable email editor that could be integrated with multiple products became apparent, and in 2022, the decision was made to begin work on such an editor. ArdentCode, with its experience in similar projects, was chosen to partner with Spotler to execute the task.

Product

The concept of the Email Editor had been analyzed and developed within the Spotler Group for some time. However, due to limited internal resources, it was necessary to open up to an external partner. ArdentCode, with its experience, was the natural choice for the project. As work progressed, the scope changed, and we expanded the team, adapting to the client’s evolving expectations.

Focus: 

Objective:  

Implement an application providing an email editor for non-technical users that can also be embedded in existing applications created in various technologies.

Needs: 

  1. Replace previous and costly-to-maintain editors
  2. Introduce a consistent design across products of one group, facilitating the use of the editor in different applications
  3. Eliminate the differences between them
  4. Use and develop Spotler Group’s Domain-specific language for email needs

Approach: 

  1. Take over the internally built PoC (Proof of Concept).

Starting work involved analyzing the implementation of the first version of the editor as a Proof of Concept. We verified the design from both the technical and functional points of view. Based on this evaluation, we provided guidance for the further direction of work.

2. Create the MVP (Minimal Valuable Project). 

After the analysis, we formed a project team that joined the existing team, and as a blended team, we completed the first version of the editor in accordance with the specification.

3. Deployment. 

After testing, we launched the editor’s production version. Proper implementation in one application was the key, to be followed by others. 

Results: 

  1. Reduced maintenance costs. By replacing multiple editors with one common solution, Spotler Group was able to significantly reduce future development costs and streamline the development of a single editor. 
  2. Introduction of a single email editing tool. This change contributed to delivering a vast amount of functionality to several products simultaneously, implementing AI assistants, creating a unified brand management system, and integrating with external service providers.
  3. Verification of the internal idea. The editor uses a descriptive markup language (SPML) created specifically for this project. The project’s success confirmed that creating SPML was a good direction, as the application is not dependent on external solutions.

Conclusion: 

The implementation of the Email Editor allowed for the optimization of various applications offered by Spotler Group, significantly reducing the costs of maintaining the teams responsible for the product operation and creating a wide range of new possibilities. The universal application of the new solution also contributed to simplifying deployment procedures for end clients, who, having access to diversified solutions from Spotler Group, could quickly and easily adapt to new functionalities. 

Case Study

Improvement of Legal Research: 

ArdentCode’s DevOps Transformation for Wolters Kluwer’s VitalLaw

Introduction:   

ArdentCode partnered with Wolters Kluwer to upgrade their flagship legal research platform – VitalLaw (former Cheetah™). It was a challenge to introduce DevOps practices to a large-scale, multi-year project. ArdentCode aimed to increase frequency of production deployments and lower the time needed for change implementation. 

Focus: 

Objective:  

Enhance the development process for VitalLaw, while maintaining the highest standards of security. 

Needs: 

  1. Increase frequency of production deployments and lower the time needed for changes implementation 
  2. Introduce DevOps practices to VitalLaw – large scale, multi-year project 

Approach: 

  1. Continuous Integration: Through DevOps practices, ArdentCode team was able to change production deployment from two months to bi-weekly production releases. This change also gave a possibility for daily deployments. 
  2. International blended team creation: ArdentCode used DevOps tooling and practices across teams in the USA, Europe, and India, facilitating collaboration and efficiency. 
  3. Process improvement: The adoption of the Scaled Agile Framework (SAFe) enabled smoother development processes and enhanced agility. It was conducted in accordance with the client’s internal processes. Needed improvements were also enhanced.
  4. Testing and verification: There was a need to test the application in a different way – it was a basic need of the project.  The goal was to reduce testing time. We changed the scope of testing to automatically test only the areas touched in the code.  As a result, instead of testing in a few working days, we were able to deliver some changes in a few hours, with testing taking much less time once the changes were made. The number of e2e tests was reduced to each release, integrating with external applications to support testing.  

Key changes: 

Results: 

  1. Accelerated deployment: Deployment frequency increased from 2 months to 2 weeks, with the ability to deploy changes on a daily basis. 
  2. Changes in shortened time: Teams were able to deliver required changes more quickly. 
  3. Agility: Every code change (Pull Request, Merge Request) is a potential release candidate. 
  4. Rollback on demand: Rollback to previous version on demand  
  5. Improved stability: Less number of regression bugs. Higher confidence in the release quality. 
  6. Comprehensive tooling: DevOps tooling and practices were successfully integrated across all collaborating teams, enhancing collaboration and efficiency. 
  7. Security and elevated performance: ArdentCode ensured rigorous security and performance verification, maintaining the highest standards for VitalLaw. 

Conclusion: The adoption of comprehensive DevOps practices by ArdentCode resulted in a significant change, thanks to the reduction of deployment timelines from months to weeks, and the introduction of daily deployment capabilities. The operational shift not only accelerated change delivery but also fostered a culture of agility, where every code change became a potential release candidate, enhancing adaptability and responsiveness within the organization. Moreover, the emphasis on rollback capabilities and the observed decrease in regression bugs underscored a commitment to stability and quality assurance, reflecting a pragmatic approach to software development that prioritizes efficiency and reliability.