2 ms·
> CQRS over simple databases, Hadoop while a single server suffices, or even people choosing JIRA over a simple trello board I've heard this from many engineer
by threeseed 5y ago
> CQRS over simple databases, Hadoop while a single server suffices, or even people choosing JIRA over a simple trello board
I've heard this from many engineers over the years.
But what I've often found is that they were never involved in the decision making process and so aren't aware of all of the business requirements. Once they are made aware usually they agree with the choice.
Common example being the business requirement to have high availability.
- cbushko 5y agoIt seems to me that the concepts of high availability, scalability and resilience are things that are just not taught or emphasized at most companies average at all. As Ops, this is a daily battle of education and prod readiness checklists. It is even the simplest things that are ignored such as: - what happens to your db query when you have 1 million records? - what happens when the cache goes away? - do you even use a cache? - why are you treating your cache as a DB? - can we run 2 copies of your service? - can your service scale up and down? - does your service have state? Kubernetes has been a boon for us in this department. Since pods can be moved/deleted at a moments notice we have had to make our software resilient and stateless. Yes, kubernetes is complex at first but it pays off hugely when you are no longer getting paged because 'server X hung and needs to be rebooted'.