---
# System prepended metadata

title: "Bakery news (18/12/2020) \U0001F370"

---

# Bakery news (18/12/2020) 🍰

Hello [peeps](https://www.hotjar.com/blog/gender-inclusive-language-workplace/), I've been thinking about making this "newsletter" for ages. The rat race, as you all know, is a problem and nothing comes out of the oven. But using our mantra "make fast and grow later", I decided to start with this simple format and start today.

But what is that? Why should I care? Calm down, my young connoisseurs of cakes. As Jack (the cake maker) would say "let's go by parts":

Until now we have two places to talk about the things we are doing, biweekly on the tribe sync or the architecture forum. Both excellent places to speak, but the first one is focused on the product deliveries & users challenges and the second is about the future of our architecture.

On the other hand, I still feel we need a place to share knowledge and learnings about our day to day development work: a place to talk about our achievements & defeats, straightforward to read and understand.

This first version had the participation of Debora Martins, Felipe Piacsek, Ricardo Murad and Rodrigo Caldeira, to whom I am very grateful, we did this way to gift them at the end of the year, for the next I would like your participation.

It should work like this: whenever you find something new, fix something with an exciting form, discover a new tool or think you have a nice thing to share, go ahead, share with me. I will make a curation (sometimes sugarcoat it) and then share here with other members of the team.

**Obs 1**: for the next one, I will avoid the text wall on the presentation, going straight to the main topic. As this is the first of the series, I needed to introduce the subject.

**Obs 2**: initially, I wrote this text in Portuguese. After translating to English, I felt something was missing. If you don't realize my excitement and happiness with this project, here's a enforce: I'm very excited and joyful!

## Our darling 🍪

- The new Slack notification system on bank-cake
    - By cashin squad
    - We made this for support [this issue](https://sumupteam.atlassian.net/browse/BBCI-131);
    - Just for now is a [super simple solution](https://github.com/sumup-bank/bank-cake/pull/13);
    - If you need an example to use, check [this PR](https://github.com/sumup-bank/bank-cashin/pull/18);
    - Future:
        - Maybe a separated service, with delivery rules, something like we have on opsgenie.
        - Today we are using the module directly, but we have an idea to use Telemetry to handle events and send for other services;

## Fresh from the oven :cake: 

### Using a read only replica on the ecto to improve the queries performance:

- By backoffice squad
- With PJ release we needed to make sure that the new database modeling would not drastically affect response time, so we decided that before delivering PJ we should start using the replica for our queries. PRs:
    - https://github.com/sumup-bank/bank-accounts/pull/162
    - https://github.com/sumup-bank/bank-accounts/pull/163
    - https://github.com/sumup-bank/apps-state/pull/245

### [Oban](https://oban.dev) for background jobs, a Pix Out example:

- By pix-out squad
- Cashout transfers
    - Async nature of Pix transfers based on workers. After a new transfer request, a new job is created in Oban queue.
    - Each job is responsible to check and update locally the transaction status.
- List of Pix Participants
    - Bacen releases a daily updated list of Pix participants that must be used to choose the institution, instead of TED bank list.
    - This list is a CSV file available in Bacen website.
    - The worker reads this updated list on a daily basis.
- **obs:** We are using Oban at [bank-accounts](https://github.com/sumup-bank/bank-accounts) too, and we have business license, talk with Tiago Luiz to get more information.

## We are still experimenting 👨🏿‍🔬️

### Open Telemetry status

- by core-baking squad
- We had success in sending [traces](https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/trace/api.md) to Datadog (thanks to @Luiz Miranda that solved this issue) with [Open Telemetry](https://blog.newrelic.com/product-news/what-is-opentelemetry/) erlang libs. In Next steps the Ops team will deploy the [Open Telemetry Collector for Datadog Pods](https://github.com/open-telemetry/opentelemetry-collector-contrib) and we will be able to instrument our services just adding the dependencies to mix.exs.

>> **What's is Open Telemetry and why we using it?**

>> Open Telemetry is a specification with a set of tools created to standardize the process of collect and send metrics. Using that we have the advantage to avoid vendor lock-in with a multiplatform solution. Like other erlang/elixir projects, the maturity of the libs is a problem. Most of then are in first steps but we're planing to contribute to community.

## Piece of pie :pie: 

### Remote configuration via RPC on E2E testing

- We can run any commands remotely, not only configurations. Examples: [Cashout](https://github.com/sumup-bank/bank-e2e-tests/blob/master/test/bfc/cashout/ted_operations_test.exs#L61) and [CIP](https://github.com/sumup-bank/bank-e2e-tests/pull/46/files#diff-611891fb90ee318230960fac230d5d2c3cc009e455bb6a6b64c26c25565db103R112-R114)
- Although possible, it's still a rough experience. How can we improve it to become more dev-friendly?

## I'm full 🍾

Not enough, I hope, It's the end of the year, let's get our deserved rest and eat all good things this time of year. All the best, and see you again next year.