Fuga Update: Development of a new region

Fuga Update: Development of a new region

In this new update you learn more about our road towards launching a complete new region at Fuga Cloud. Not in a reading mood? No worries. Relax and enjoy our podcast below.

The road to a new Cloud region. It’s a fun, but bumpy ride.

One of the most asked features for Fuga Cloud is an extra region. That’s why we are working hard to develop a new region. And it needs to be even better than the first region we launched back in 2015. We are currently in private Beta and the first tests are being done by actual users. For this region, we went back to the drawing board to see how we can optimize our development process and implement as many new features as we can, without delaying the launch of our second region. This region will be made available later this year and will be located in the Netherlands.

Challenges

We have the ambition to launch several regions in the coming years and we need a sustainable process for developing and maintaining these new regions, without compromising the usability and performance. Unfortunately, we aren’t a company with unlimited financial resources or employees. To make the best use of our resources and time we need to spend as much time as we can in development and as little as possible in managing and maintaining our regions. But how do you achieve that without compromising the quality and stability of your IaaS Cloud platform?

Scrum

Scrum and CI/CD

We implemented the Scrum framework in order to respond to the changing demands of our customers. Our Scrum teams work in a sprint cycle of two weeks to create increments (improvements) for our customers. To be even more efficient we created a development process for Continuous Integration using different tools and techniques such as Gitlab CI, Kubernetes, and Docker. This also helps us to use automated deployment within our new region. Working with Continuous Integration and Continuous Deployment (CI/CD), changes and improvements to the platform can be made very quickly. For example, our test users pointed out that there was something not working properly on our Private Beta platform. We made the necessary improvements and we got it from test to production within 10 minutes. Without the users even noticing it. Except, of course, that the problem was now fixed.

In the future, I will go more in-depth about our CI/CD strategy. CI/CD

Our lastest sprint cycle

In the past two weeks, we focussed on improving our registration process and implementing Single Sign-On (SSO) for our second region. I can tell you it’s looking pretty awesome. We made some minor changes to our website mostly in color and usability. We added some new tutorials, so check out our latest tutorials in our improved Academy. Furthermore, we’ve updated our privacy policy so that it’s GDPR ready.

Next

Looking forward, we still see many challenges we need to address and mountains we need to climb. But that will not stop us and every problem we fix will lead to a better, faster and more stable Fuga Cloud. We can already see the light at the end of the development tunnel and we look forward to facing the next challenges wearing a smile.

Updates

We’ll keep you posted on further development and the challenges we conquer for this new region and other news from Fuga Cloud.

Was this article helpful?


Next article:

How we use SCSS/CSS at Fuga Cloud

Last summer, we at Fuga Cloud started rethinking the way we approach writing our CSS. Before this point, we were still using vanilla CSS. This was starting to become more of a problem with every feature we rolled out. So when I started working here, my first assignment was to implement SCSS following the ITCSS methodology. This enabled us to do two things: SCSS enabled us to write SCSS in a component-like way ITCSS forced us to write our CSS in a logical order We chose Gulp to compile our SCSS and to automate some other stuff such as minification and sourcemaps etc.