Sergio Robles
Devops Team

Development, DevOps, LABS

Terragrunt : Terraform the easy way

March 12, 2019

March 12, 2019 by Sergio Robles

We are using Terraform to configure our Infrastructure as Code in AWS and we used it with Terragrunt from the first day.

What is Terragrunt? the official definition

“… is a thin wrap for Terraform that provides additional tools to maintain your Terraform DRY configurations, work with multiple Terraform modules, and manage the remote state.”  (read more)

We have found Terragrunt very useful, it allows us to configure the remote state, locking, additional arguments, etc. depending on the configuration of your terraform.tfvars file.

The best features of Terragrunt for us are:

Read more

Share on Share on FacebookGoogle+Tweet about this on TwitterShare on LinkedIn

Sergio Robles
Devops Team

DevOps, Events

DockerCon EU 18

March 12, 2019

March 12, 2019 by Sergio Robles

On December of 2018, the Ebury team attended DockerCon EU.

DockerCon Europe describes itself as “a 2.5 day technology conference, where customers and community come to learn, share and connect with each other. Attendees are a mix of developers, systems admins, architects, and IT decision makers —from beginner to intermediate, and advanced users—  who are all looking to level up their skills and go home inspired and ready to invest and implement their containerization strategies” and that is exactly what we wanted to get out of it.

Read more

Share on Share on FacebookGoogle+Tweet about this on TwitterShare on LinkedIn

Juan Manuel Pérez
Quality Assurance

Agile

Tech Culture: Teams, Tribes and Pirates

March 8, 2019

March 8, 2019 by Juan Manuel Pérez

Tech Culture: Teams, Tribes and Pirates

Welcome to this biology post, because in a high-level, I’m going to share part of our Agile DNA. We will cover 3 ways we interact with other Tech colleagues:

  • Teams
  • Tribes
  • Pirates

Teams

Our Scrum Master are going to explain this information in other post but Teams at Ebury are responsible of few microservices (API, Faster Payment, SEPA, Website …) or a larger application (Back Office System, Salesforce, Ebury Online…). These cross-functional groups from 4 to 8 people are aligned with the business roadmap and goals for the next few months.

Read more

Share on Share on FacebookGoogle+Tweet about this on TwitterShare on LinkedIn

Agile

Our Agile Process

February 14, 2019

February 14, 2019 by Fernando Lopez

At Ebury, all of our development teams use the Agile Scrum framework, so we thought it would be interesting to share a little bit about what goes on under the hood.

Scrum framework

Scrum is used by over 12 million people around the world for products big and small. It all starts with a Product Owner who represents customers and other stakeholders. The Product Owner drives the Product Backlog, a prioritized dynamic list of all the work that might be needed for the product.

Work is done by a self-organizing Development Team during the Sprint, a period of time between one and four weeks.

During Sprint Planning, based on the Sprint goal, the Sprint Backlog is populated. Once a day, the Development Team meets for 15 minutes for the Daily Scrum to inspect and adapt their progress toward the Sprint goal and to surface dependencies or impediments.

So, who makes sure that the Scrum Framework is understood and enacted? the Scrum Master. The Scrum Master is the servant leader of the Scrum Team and helps everyone understand Scrum theory, practices and rules. As the team works towards the Sprint goal, iterative delivery and feedback allow us to adapt our next steps. To improve transparency, the product increment can be released continuously during the Sprint.

At the end of the Sprint, the Scrum Team invites the stakeholders to the Sprint Review, where they collectively inspect the results. After the Sprint Review, the Scrum Team runs a Sprint Retrospective where they evaluate how they worked and build a plan for how to improve.

Scrum at a glance
Scrum at a glance

Read more

Share on Share on FacebookGoogle+Tweet about this on TwitterShare on LinkedIn

Data science, Design/UX

Visualizing User Experience Data with Google Data Studio (Part II)

January 21, 2019

January 21, 2019 by Carmel Hassan

In our previous article ‘Visualizing User Experience Data, we defined a framework to measure the User Experience of a product. In this article, we want to share how we can use Google Data Studio to visualise those metrics and facilitate the decision making during the design process.

Data Studio

Data Studio is a free tool offered by Google that allows you to create interactive dashboards and reports with data visualizations using multiple sources of data.

Data Studio user interface is pretty intuitive, however, there are two key concepts you need to manage to get started:

  1. Data sources let you connect data sets. This is the first thing you have to do before adding charts to reports.
  2. Reports let you visualise data. You have to select one or many data sources to feed data displays. Reports can be shared, interacted and exported.

Starting a new report is as simple as clicking on a button. If you don’t want to start from scratch, you can follow their tutorial that explains how to work with reports step-by-step.

datastudio user interface
Data Studio User Interface

Read more

Share on Share on FacebookGoogle+Tweet about this on TwitterShare on LinkedIn

Development

The Fin and the Tech

January 17, 2019

January 17, 2019 by Victor Tuson Palau

We often talk about Ebury being a disruptive Fintech company. Today I wanted to go into more detail about what makes Ebury a Financial and Technology company.

FINtech

Ebury’s core business is foreign currency exchange (Forex), and we focus on the enterprise segment of the market. To better illustrate what we do, let’s take as an example a made-up European toy company, which we will call TOYSA.

Read more

Share on Share on FacebookGoogle+Tweet about this on TwitterShare on LinkedIn

Design/UX

Visualizing User Experience Data (Part I)

January 14, 2019

January 14, 2019 by Carmel Hassan

Ebury Online is a platform that allows users to do international payments quickly, securely and efficiently. Using data analytics it’s an important part of Ebury’s design process.

We, as product designers, need to have a great understanding of data in order to make informed decisions that will impact both on the business and the user experience (UX).

Services like Google Analytics or Hotjar facilitate the exploration and understanding of how websites are navigated. However, in 2017 and 2018, only 1 in 3 designer-related roles use any experience monitoring tool.

At Ebury, we think that data can certainly help us to find answers to questions like ‘who is our audience?’, ‘what do they do?’, ‘how do they perceive and experience the product?’ and ‘how good is that for the business?’.

As shown in the image below, data is collected directly from our Online platform using the huha.js library, sent through Segment and shared to different end-points, which will facilitate smart analytics.

UX Data Tools
Tool framework to collect UX metrics

Read more

Share on Share on FacebookGoogle+Tweet about this on TwitterShare on LinkedIn

Design/UX, Events

The best of Generate Conference – 2018

November 12, 2018

November 12, 2018 by Carmel Hassan

Last month, the Ebury team attended Generate, a conference dedicated to designers who are looking to improve the user experience (UX) of their websites. We’ll be talking through what we learned, how we’ll be applying our new knowledge to our UX, but most importantly, what you can take away to apply yourself.

The opening talk was presented by Sarah Parmenter who spoke about the importance of digital marketing strategies that can be easily applied by anyone. Parmenter shared key rules that can be applied today to help decide the best media tool to distribute your company’s message: First, think about your Product, then the client Experience, and then the Story. Only then, you can choose the right media outlet.

Our tip for you: If you decide to do a video, make sure you include subtitles, as 85% of all videos are played without sound.

Do you struggle to get your videos noticed? Try Hashtagify to find the best hashtags to get your content noticed.

The closing talk was presented by Sara Soueidan, a front-end UI developer who talked through how cascading style sheets (CSS) and scalable vector graphics (SVG) can be used for better usability and accessibility. One takeaway we gathered from this was to make sure that you integrate these inclusive design practices as part of your natural design and development process.

While CodePen’s senior software engineer Cassidy Williams impressed attendees by coding an image chosen at random found on Dribbble, designer and developer, Ricardo Cabello, demoed Three.js library to demonstrate how you can create WebVR interfaces with the library available on that platform.

UX consultant Trine Falbe talked through the importance of ethics when designing, highlighting the importance of how the data generated by users is looked after. In an age where data is the new oil, this is to consider for data-driven teams.  

Probably one of the most interesting talks of the day was presented by Andrew Godfrey, Senior Design Specialist at Invision, on Design Systems fails. Godfrey exposed some of the goals a successful design system has, such as:

  • Improved consistency
  • Efficient time on task
  • Efficiency reuse
  • Inclusive design (accessibility)
  • Reduction of defects
  • Improved UX
  • Strong design community

Godfrey also highlighted common failures that need to — and can easily — be avoided, such as:

  • Low adoption by internal staff
  • Low understanding by internal staff
  • Mismanaged content
  • Scale system difficulty
  • Lack of support
  • Missing the bigger picture (not just in UI components)
    • Lack of style guides
    • Unclear visual components
    • Unclear standards
    • Accessibility
    • Animation
    • Information architecture

Godfrey advocates considering Design Systems as a core project inside the business, which means adopting processes such as:

  • A plan, strategy, and process
  • A roadmap and priorities
  • Scaling up when validating
  • Incorporating ways of measuring and sharing success
  • Creating prototypes that can be validated
  • Assigning a ‘person of expertise’, that knows the system well
  • Effectively calculating design debt

 

For us at Ebury, Design Systems are one of the key tools to create and maintain a good user experience across all of our services. This is the key principle behind Ebury Chameleon and the reason why we’ll continue investing and improving our processes to ensure high-quality products and services.

Share on Share on FacebookGoogle+Tweet about this on TwitterShare on LinkedIn

Events

Jenkins World: Fighting the Jenkinstein

November 9, 2018

November 9, 2018 by Luis Piedra Márquez

Jenkins World is a two-day conference held specifically for IT executives, DevOps practitioners, Jenkins users and partners.

This year, I attended the conference in Nice, France.  Jenkins World has traditionally always been held in San Francisco, but this year it expanded across to Europe with the additional conference admitting more than 800 attendants. Due to the success of the first European conference, another has been scheduled for next year—taking place in Lisbon.

The event was sponsored and driven by CloudBees, the company behind Jenkins (in fact, the creator of Jenkins, Kohsuke Kawaguchi, is CTO of CloudBees. A few big names attended, such as Amazon, Google, Microsoft, Docker and VMWare. There was also a great presence of the Jenkins OSS community.

While Jenkins has been around for more than ten years, its roots can be traced back almost 15 years, so it was created in a completely different landscape compared with today’s technology and industry practices—for example, there were neither cloud nor Agile methodologies back then. In 2014, the then-called workflow plugin (later renamed to Pipeline) was introduced. It was a disruptive change, as there was no direct compatibility between old-style pipelines (that were, and still are available) and new pipelines. I remember being very critical at the time, since it was quite bugged and a somewhat incomplete function, (even in 2016 when Jenkins 2.0 was announced) so I wouldn’t have recommended migrating to Jenkins pipelines at that point. However, I was proven wrong and it evolved well. By mid-2017 it was production ready, so we started a successful migration at Ebury later that year.

Note that we are talking about three years of evolution to have a usable pipeline, which is a considerable amount of time. In fact, during this time other pipeline solutions, like CircleCI and Bitbucket Pipelines managed to be built from scratch and launched. However, this last year has been a year of wonder for Jenkins, with lots of amazing initiatives crystallizing for pipeline and beyond. All of this was presented at the Jenkins World conference in a quite well structured way:

Pipeline

With Declarative Pipeline Syntax and multibranch and organization jobs, Jenkins made a step forward in the last couple of years. Pipeline as Code continues being the backbone of the project, and that’s good news.

Configuration as Code

Although Pipeline as Code helped us a lot with job configuration, and the different cloud plugins also helps configuring slaves/nodes… when it comes to configure the Jenkins instances that instrument all that, it’s still really painful, and this tool comes to fill that gap.

We’ve been waiting for something like this for a long time, and thanks to Praqma and Ewelina Wilkosz, it’s finally here. It’s important to note that while this has not come from Cloudbees or Jenkins core, it has now been embraced as part of Jenkins core. It just looks awesome. We’re really excited to start configuring our instances this way.

 Jenkins Evergreen

This project is about Jenkins out-of-the-box experience. Think of it as a Linux distribution, a complete set of plugins thoroughly tested together for functionality and security, bundled with a Jenkins LTS version.
Of course, it will reduce flexibility in some scenarios, but quoting Michaël Pailloncy, we used to install the latest Jenkins versions instead of LTS when we were young… but we don’t do it anymore, and the same may apply for the huge collection of plugins we use day-to-day.

Cloud Native Jenkins

Along with configuration, another long lasting pain in Jenkins’ administrations has always been infrastructure for the master instance, particularly when it comes to storage. It also weighed the possibility of true high availability (HA) for Jenkins master. This is by far the less polished of the superpowers, exemplified by the fact that it is a Special Interest Group and not a Project.

Jenkins X

Continuous integration and deployment for Kubernetes in an “opinionated” way. This means it’s only for Kubernetes, and it enforces a certain way of working. Quite far from the extraordinary flexibility that has characterised Jenkins. As Koshuke explained, it acts like a train with a fixed destination (i.e Kubernetes) and fixed rails… but it’s a really comfortable and fast train.

Kubernetes has been a topic of discussion in almost every talk, as it’s now seen almost as a standard for microservices architectures.

Image: https://jenkins.io/

An other interesting topic at the conference was the “Jenkinstein”. Over the time, when Jenkins instances start to grow in usage in organisations, they sometimes tend to grow in uncontrollable ways, essentially becoming monsters that need more and more dedicated work maintaining them.

These ‘superpowers’ will help developers and Jenkins administrators to fight these “Jenkinsteins” monsters. At Ebury, we’ve taken advantage of everything included in Jenkins 2.0—over the last year we’ve managed to remove all the mess in jobs creation, linking and configuration. However, we still need some puppeting when it comes to the operations side, and we will for sure also take advantage of Configuration as Code and Jenkins Evergreen projects.

Enjoy Jenkins and automation, and remember two quotes I have learnt over the last two days:

  • If you automate a mess, you get an automated mess
  • “Never send a human to do a machine’s job”
Share on Share on FacebookGoogle+Tweet about this on TwitterShare on LinkedIn