Spring is one of the most popular JVM-targeted frameworks. One of the reasons why it has become so popular is writing tests.
Even before Spring Boot era, it was easy to run an embedded Spring application in tests. With Spring Boot, it became trivial.
JUnit and Spock are two most popular frameworks for writing tests. They both provide great support and integration with Spring,
but until recently it was not possible to leverage Spring’s @WebMvcTest in Spock. Why does it matter?
@WebMvcTest is a type of an integration test that only starts a specified slice of Spring Application and thus its
execution time is significantly lower compared to full end-to-end tests.
Things have changed with Spock 1.2. Let me show you, how to leverage this new feature.
At Allegro, feature velocity is a top priority. We believe that one of our critical competitive advantages
is the rate at which we introduce new features. In order to achieve a high feature velocity, one of the architectural
choices that Allegro made a while back was to move to microservice architecture. So when somebody uses Allegro, a
request comes in (and we just have a hypothetical example here) to service D — and we can imagine a service D being a
proxy or an API layer — and whatever that service is, it is not going to have all the information it needs to serve a
response. So the service D is going to reach out to service C and service F, and F in turn will reach out to A, and it
will in turn reach out to B and E, and you see that this very quickly gets complicated. Allegro has somewhere around
500 microservices, so you can imagine how complicated the communication map looks.
This is a post for those seeking to accomplish business goals and ensure stability of the solutions developed
while maintaining focus on people. The model of three basic psychological needs that I’m presenting here may be
useful for leaders, agile coaches, and scrum masters. I also encourage developers to do some self-reflection.
This is the knowledge I’ve gained at the World Conference of Transactional Analysis in Berlin.
Transactional Analysis (TA) is a theory of interpersonal relationships developed by Eric Berne which has a
practical application in various fields, including organizations.
Application release process, or in fact software development process, as a release is the final stage of application
development, is not an easy thing. Books and IT websites discuss many approaches and each has its supporters and
opponents. On the one hand, you have product owners, project managers and customers who want a ready-to-use application
as soon as possible. On the other hand, we developers and testers, would like to release an application of the highest
quality, which may affect the delivery time. Balancing these needs is a hard nut to crack. Usually, both
sides need to make some compromises to establish a common way of working. For developers and testers, it involves
answering several questions concerning software development methods, skills, use of manual or automated testing, and
storage of test cases and test logs. In this article I describe best practices and tips for starting a new project.
I think that by following them, you will make the software development process as effective as possible and adjusted
to conditions of your project.
Apache Mesos is an open-source project to manage computer clusters. In this
article we present one of its components called Executor and more specifically
the Custom Executor. We also tell you why you should consider writing your own
executor by giving examples of features that you can benefit from by taking
more control over how tasks are executed. Our executor implementation is
available at github.com/allegro/mesos-executor
Some of our engineers run their own tech blogs.
We encourage them to move here, but for various reasons,
they prefer to publish on private blogs. We respect their decisions.
What we can do is to gather all the blog posts published by allegro.tech
engineers around the web in the one place.
In this post I present a story of a bug that hit us recently. Everything was
caused by unexpected (although documented) behavior of Go built-in function
append. This bug has lived silently
for nearly a year in
allegro/marathon-consul. Ensure
you run the latest version.
At Allegro, we build and maintain some of the most distributed and scalable applications in Central
Europe. This poses many challenges, starting with architecture and design, through the choice of
technologies, code quality and performance tuning, and ending with deployment and devops. In this blog,
our engineers share their experiences and write about some of the interesting things taking place at the
company.
