Messaging done in wrong way - can that be possible?

 What we shall expose to client (and it is really a case)?

My last blog entry (click) was about messaging and the way we can start refactoring our app by splitting activities internally, now let's have a look from other side when a decision need to be made to expose messaging wisely. 

Let's have a look at real life story that occured in one of the places where I was working.

A team was working on a monolith to split it up to smaller services (ach we want to say micro services). So they integrated messaging using one of the cloud providers (out of the box solution). 




As the team was successful in their job - a member from other product suggested to use the message bus to speed up integration process and all agreed and were happy.



The time goes on and a client got access to the bus just to speed up some things...




So what do you think happened there?

As the team was progressing with their job they realized that they can't:

- guys had to constantly maintain access to the bus and all configuration was on them (a pretty junk work believe me - as that not started as a public accessible solution)

- change messages shape and payload as the other teams were hestiating to do so...

- and the nicer part: one of the systems had to be deployed for a big and valuable customer that has only a government permission to use other cloud provider

As that started to look good in beginning turned out as a nightmare.

So what could we learn from this situation?

Single responsibility principle could give use a small hint, like don't mix stuff together. If we have a bus for internal services, then (if u need provide a bus to others) create a separate bus, a couple of $$ monthly will still be less than time spent to untangle this problem, moreover if you are obligated to use same bus - still - expose an api that will be putting those messages on YOUR bus, so you can handle all aspects internally and don't need to beg an external entity with 6 months notice for any communication schema changes.


Comments

Post a Comment

Popular posts from this blog

when a new guy joins a team...

Image
Not so long ago, I was browsing merged pull requests to check quality of the work that was done. I don't know why, but in 202X C# is rather a modern language and some language syntax shall be adjusted to newer standards. When I was starting my developer journey - I was told to always add a code that looks similar to the one that already is there, unless it is total crap and adding new stuff needs more effort today, to not to die tomorrow. But in this case, we have a project that is created in in 202X and there is a lot of good looking and working lines of code around, so anyone can follow it. First time, when I was a student and helped my colleague, I was in shock that the teacher recognized my help, I turned all red and asked him "how you were able to recognize that?". He said that most of us have a kind of style that identifies us as developers, so this is spacing, the way how we organize braces (even when autoformated), how we write and solve problems,  and finally var
Read more

FizzBuzz - my first interview task on whiteboard

Image
 I think we all know the FizzBuzz task, when we a function shall print fizz if the number is divided by 3, buzz if by 5 and fizzbuzz when by both. Yesterday I did a small research about how many different implementations we can have using C# and there were many. Ones looks very common with "if"   statement tree, some of them were using LINQ and looking hard to understand what is going on in a first instance. StackOverflow has this one question with a bunch of examples  Writing FizzBuzz , that I will use to check how those solutions work from a performance perspective, code complexity and human understanding. listing 1 fizzbuzz question As we can see, OP introduced a tuple to solve the problem, which in my opinion gives a lot of opportunists for extensions with a little code changes.  The metric looks good, but if we move the list declaration outside the function (so it is not recreated every time the function is called we shall be good) To do benchmark I will convert
Read more

are YOU a garbage collector?

Image
 If I will ask you: "Are you a garbage collector" - I bet I will hear: " NO ", so I ask you: show me your code.... It is unbelievable that so many developers are pushing changes with commented out code, because  there could be a chance to re-use that piece. In fact that time never comes to me and the lines stays there forever. Clean code means no rubbish commented code - we have git to remember that for us. Now, when you need to comment a few lines in a row... there are better solutions, but if someone is lazy and slumsy then we can see diffs on code review like that: Now this is a mystery for me, when I am able to see that this is going to the main branch as the guys who is called code reviewer is there only to click Approve -  I am truly believing that it is not you my reader. I need to admit that, when I was a kid, together with grandma we were collecting garbage as a way to get some $$ for a life and then every piece we found had a material value and were able t
Read more