TGONext: Choose Architecture By Cons
This meetup we review previous discussions and switch to the next topic. Based on the high concurrency we talk about the last meetup, we simulate an architecture and evolution it.
This meetup we review previous discussions and switch to the next topic. Based on the high concurrency we talk about the last meetup, we simulate an architecture and evolution it.
About 1 year ago, I build a Ansible playbook for the customers of 5xRuby.
When the customers grow it is hard to use the fork feature to maintenance the customer’s playbook.
I have to update the main version and sync the changes to the fork version for each customer. Therefore I decided to split the common parts to a single role repository.
Yesterday is the first meetup of the TGONext project, we are learning from Taiwan’s high-level technical leaders. After the opening, our mentor Ant let our polling for the topic we want to discuss in this half-year project time.
We decide to pick up 4 topics to discuss and the first topic is “high concurrency.”
Include me, write test is many people’s nightmare. Many junior programmers feel it is hard to define which should be tested. So, I decided to share my experience after I tech my colleague today.