In it's purest form, the microservices architectural pattern tells us to "dream small" while designing services, which is all well and good, but how small is still useful?
Pragmatic microservice design helps draw some useful boundaries, and keeps our eyes on shipping product.
In this episode we talk to Director of Engineering Daniel Knight about breaking down business problems into known objectives in the business and technical domain, and taking the focus off trying to solve problems we don't yet understand.
In that way, product teams can focus on the WHAT while engineering teams can focus on the HOW. It's all about balance.
Hosted on Acast. See acast.com/privacy for more information.
