/explore
|
You are here 
|
blog.acolyer.org | ||
| | | | |
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 |
|
| | | | | ||
| | | | |
www.milanjovanovic.tech
What are microservices, and why might they be the right architectural choice for your organization? Microservices offer independently deployable, domain-focused components that provide flexibility when applied correctly to solve the right organizational problems. |
|
| | | | | ||
| | | | |
martinfowler.com
The microservices architecture can be useful, but to know if it's suitable in your context you need to understand its costs and benefits. |
|
| | | | | ||
| | | | |
www.softdevtube.com
Computers are orders of magnitude faster than when most of us started programming and yet a lot of software runs much slower than it should. Nobody likes progress bars. Slow code provides for a horrible user experience, drains batteries faster, and increases our cloud bill. This session explores some of the reasons why software is |
|
| | | |||
