We Collaborate, Deliver & Explore

Our Architectonic Principles

Everything we build follows a set of guiding principles:

• Design for change
  The only thing that is constant is change, as the expression goes. This is certainly true for digital solutions as well, and it is something we take into consideration at the very outset of a new project. Our aim, therefore, is to build software that is open to changes, while maintaining its high quality.
• Design for run-time
  Our code only provides value when it is running in production. We make every effort to ensure that our solutions are reliable, and that they can be deployed and monitored with ease.
• Keep it simple
  Build the simplest solution possible, based on what is needed here and now. Each design element and line of code must be able to be understood, tested and maintained for a long period of time. Systems with intuitive and user-friendly designs are less vulnerable to changes, and encourage users to work with existing services instead of looking to new and/or isolated systems to help them in their work.
• Only build business value
  Our customers must always be at the very center of our attention, and we need to make sure that our work always benefits them; processes that increase business value and our productivity, and make us a trusted and valuable partner. This is something that should be be an integral part of all our work – long- and short-term, internal as well as external.
• Scalability as Default
  Client increase and service ecosystems are growing at a pace that is hard to predict. Therefore, consider an ever-growing traffic model, both from the number of clients and the impact each client puts on the system. We want to try to avoid building solutions where we know that we will "hit a wall", but instead cater to services that can be scaled next to an infinite number of times.
• Security as Default
  Security is always a central aspect of the solutions we build, as our customers expect that of us. The costs of security, and the risk of breaches, will only increase the longer one waits in implementing it.
• Service isolation
  Build well-defined services with minimal dependency on other services. If each service is largely independent of other services for its lifecycle and runtime, it can be improved and worked on without impacting other services. Isolated services with a clear purpose are easier to understand both in terms of code and runtime.