Arima

More content

We are
Arima /

Our
souls /

AUTHENTIC SOFTWARE DESIGN PEOPLE

Our character, the way we are, our talent, our culture and what we are.

All that is Arima’s soul.

1. BUSINESS
   DRIVEN DESIGN

   Understanding the business
   and the goals of our clients is always our major priority.

2. RESEARCH IS IN OUR BLOOD

   Exploring the knowledge, analysing other errors and solutions. This allows us a long term vision, essential in the world of technology.

3. MEASUREMENT IS THE KEY TO FIND THE BEST SOLUTION

   Because what can not be measured, can not be improved.

4. GOOD COMMUNICATION

   We are creative, pioneering and realistic people. And we love telling it as it is. With honesty, politeness and enthusiasm, the result is always better.

5. SIMPLICITY

   Less is more. Reducing complexity and facilitating the comprehension is the key. We apply good practices from the design.

Services and
products /

Business driven design: Understanding the big picture. Getting to know our clients’ business is the first step to finding a solution.

• Software Design

  We can help you to design your product or develop and improve existing architecture in order to guarantee the architectural principles and provide value to the business.

• Products

  For those aspects we consider are not solved by current state of the art products, ARIMA develops its own technology and products. One of the examples of this work is HDIV.

• Custom Software Development

  Based on the principles defined in our method of software design, ARIMA offers a custom software development service addressed to implement the design’s strategy.

Blog /

Investigar está en nuestro ADN. Explorar el conocimiento, analizar otros errores y otras soluciones. Esto nos permite tener visión a largo plazo, algo fundamental en el mundo de la tecnología.

• Testcontainers: containers for testing

  I’ve always been more of a fan of unit tests than integration tests, mainly for one reason: I don’t need anything external to be able to run them. I don’t need to have a database started, an external service to connect to or a Kafka running to be able to run the tests and therefore to be able to develop. That’s in the development environment, but if we’re talking about the integration environment, then I won’t even start. For example, in the case of databases we have the option of doing the tests with H2. But it is also true that depending on the type of project, it could be that something which works perfectly in H2 does not work in the database for which we are developing: As sure as we have often relied on “Let’s go … with h2, so as not to start the db …”

  Jessica Aguado

• My experience with the CKA exam

  Last Monday 22 March I took the exam for the CKA certificate from the Linux Foundation, and I’m here to tell you about my experience of how I prepared for it and what to expect in the exam. I highly recommend that you also read a post from my colleague Fernando from a few months ago about the CKAD exam, which goes into much more detail about the aspects of these exams and helps you to pass them. I got some essential tips from reading his post!

  Urko Lekuona

• Lessons learned about Contract Testing

  Over the course of several posts, we have seen how, as a result of the evolution of application architectures, new needs arise in the field of testing. We have focused on a specific one: as important as testing the functionalities in consumer and producer independently is, so also is ensuring that the interaction between them is correct. We have seen that we have Contract Testing within our reach, with different approaches and tools that allow us to address this specific need. Also using the producer driven approach and Spring Cloud Contract we have put into practice everything learned.

  Jessica Aguado