<commit_before>---
kind: article
created_at: 29 May 2016
title: One Bad call for papers
excerpt: "How we used micro services and open API to cook our stuff better."
author: <NAME>
image: bb2.jpg

layout: '/blog_single.html'
---

_Title_: **Efficient Cooking with Micro Services**

_In short_: How we used micro services and open API to cook our stuff better

_Long description_:

At one point, we needed a better way to handle multiple, arrrr, sources.
Using just phones and paper sheets was simply not working, while our, errr,
business expanded. We desperately needed to make the big move. So, we figured
we should have one central place to organize all our inputs (you know, a
place where the magic should be happening, and it’s not a Bad). We decided
to use micro services architecture and API with mobile client.

Of course, we put a lot of effort to make the communication secure,
using available technologies; and yet to remain effective. On the other hand,
we had to provide simple interfaces that anyone from our...errr... business
associates could use without much trouble.

_We did it for us._\
_We liked it._\
_We were good at it._

All in all, we are the ones who kno...w! :)<commit_msg>treća sreća<commit_after>---
kind: article
created_at: 29 May 2016
title: One Bad call for papers
excerpt: "How we used micro services and open API to cook our stuff better."
author: <NAME>
image: bb2.jpg

layout: '/blog_single.html'
---

_Title_: **Efficient Cooking with Micro Services**

_In short_: How we used micro services and open API to cook our stuff better

_Long description_:

At one point, we needed a better way to handle multiple, arrrr, sources.
Using just phones and paper sheets was simply not working, while our, errr,
business expanded. We desperately needed to make the big move. So, we figured
we should have one central place to organize all our inputs (you know, a
place where the magic should be happening, and it’s not a Bad). We decided
to use micro services architecture and API with mobile client.

Of course, we put a lot of effort to make the communication secure,
using available technologies; and yet to remain effective. On the other hand,
we had to provide simple interfaces that anyone from our...errr... business
associates could use without much trouble.

_We did it for us._ \\
_We liked it._ \\
_We were good at it._

All in all, we are the ones who kno...w! :)
{'fraction_non_alphanumeric': 0.0632279534109817, 'fraction_numerical': 0.005823627287853577, 'mean_word_length': 4.010416666666667, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '302390', 'n_tokens_mistral': 668, 'n_tokens_neox': 640, 'n_words': 395}