Explore >> Select a destination
|
You are here 
|
aivarsk.com | ||
| | | | |
www.eferro.net
|
|
| | | | | These are the best podcast/talks I've seen/listen to recently: AgileByExample 2017: Donald Reinertsen - Making Money with Variabili... | |
| | | | |
dmitrykornilov.net
|
|
| | | | | You've decided that migrating a monolith application to a microservice is the best approach to meet new application needs. Microservices arecloud native, scalable, and can be created in different languages for different services. When you're ready to migrate, you can use different strategies. Among the most common is the strangler pattern, often used with the... | |
| | | | |
vladikk.com
|
|
| | | | | Microservices have taken our industry by storm. Teams around the world have ditched their clumsy monoliths in favor of chasing the dream of loosely coupled, manageable, and independently deployable microservices. Unfortunately, many of them ended up worse off than they were before - in the realm of distributed monoliths. Why? "If I had an hour to solve a problem I'd spend 55 minutes thinking about the problem and 5 minutes thinking about solutions" - Albert Einstein In my opinion, this quote is the key to solving most of the issues we have when designing microservices-based systems. We rush into solutions without ensuring we know what exactly a microservice is. In this post, I'd like to take a stab at answering this question. | |
| | | | |
www.ybrikman.com
|
|
| | | The home page of Yevgeniy (Jim) Brikman, co-founder of Gruntwork, author of "Hello, Startup" and "Terraform: Up & Running", and software engineer at LinkedIn, TripAdvisor, Cisco Systems, and Thomson Financial. | ||
