/explore
|
You are here 
|
highscalability.com | ||
| | | | |
blog.pragmaticengineer.com
|
|
| | | | | For the past few years, I've been building and operating a large distributed system: the payments system at Uber [https://eng.uber.com/payments-platform/]. I've learned a lot about distributed architecture concepts [https://blog.pragmaticengineer.com/distributed-architecture-concepts-i-have-learned-while-building-payments-systems/] during this time and seen first-hand how high-load and high-availability systems are challenging | |
| | | | |
abdulapopoola.com
|
|
| | | | | A team without proven observability and on-call strategies will invariably suffer from reactive disruptions; mitigating outages will be painful, like finding a needle in a haystack while blindfolded. | |
| | | | |
dylanpaulus.com
|
|
| | | | | A few months ago I had an opportunity to give a presentation to soon-to-be Computer Science (CS) graduates. We presented the software development process (), and how different teams at Schweitzer Engineering Laboratories adapt the development process to their needs. We ended the presentation with ti... | |
| | | | |
laihoconsulting.com
|
|
| | | Website and personal blog of Pekka Laiho, software engineer and financial enthusiast. | ||
