Kubernetes as a cost optimization tool isn't something most people are familiar with yet, at Nucleus, we hear this all of the time. No one architecture is better than another, its all about what is right for the particular problem you're trying to solve.Ĥ. At the end of the day microservices (and monoliths) are an architecture design pattern that needs to be evaluated in the context of the problem and team you're trying to solve. That orchestration should be done in code instead of outsourcing it to another system and inserting 1-2 more hops on every call.ģ. This is inline with what we hear from customers. The other main reason the Prime Team moved away from their initial architecture was because AWS Step functions was slow and expensive. The Prime team consolidated their serverless functions and moved to ECS and saw MUCH better performance and costs.Ģ. ![]() Serverless sounds great on the surface but in reality gets very expensive very quickly, is quite slow, and, as a developer, you have very little control over how/where the functions run. Some thoughts (from an infrastructure company) below:ġ. ![]() The AWS Prime Video team moved away from Serverless & Microservices and reduced their costs and overhead by 90%.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |