less than 1 minute read

We have been dreaming about this since we started with our first line of code - creating a blog and sharing our experiences and issues which we have encountered during our journey! So welcome to our blog and we hope you will find our posts useful or at least funny 😄

Even though making a blog is time-consuming and sometimes not the priority number one, we want to at least capture our most important stuff and hopefully make this some kind of “habit” to update our blog as much as time allows 🙏

if(ElixeumBlog.IsFinallyPublic)
{
  ElixeumBlog.SayHello(toWorld);
}

Stay tuned and thanks for reading! 💜

Tags:

Categories:

Updated:

You May Also Enjoy

UI 3.0

7 minute read

We recently made the strategic decision to completely transform and enhance the User Interface (UI) of our Portal, which can be accessed at https://portal.elixeum.cloud/. This significant change was prompted by the realization that our current UI lacked consistency and did not align with the sleek and modern designs commonly seen in leading web ...

Frontend unification (Pt. 1)

23 minute read

First part of shorter series of blogposts about major refactoring of our frontend technological stack to solution that seems very obvious now, but really didn’t three years ago. Going by memories and rather big pile of notes we wrote down while working on this fun endeavour… In some parts we shall go more in depth with technicalities, in some p...

Mixing it up: Using several different databases for our platform

10 minute read

…right now around 6 databases and we are not stopping there 😄 The Big Bang Let’s start from the beginning as every system - our platform needs some database to store its data, obviously, because I’m not sure if anyone would use and subscribe to a system where any data are stored in memory and lost on every service restart/deploy 😄 And when we...

Stateful responsibility

11 minute read

A short view back to the past - when work on the Elixeum portal began, every Vue component used to handle its own requests by itself, that usually meant that every list component had locally implemented API call to count, to list with paging options and at least to delete request for specific element of said list. And every detail component had ...