Home

What challenges have you faced when implementing various point solutions and microservices at your organization?

Everyone talks about microservices or APIs—everything has to be in API, has to be consumed, even streams, etc. But they don't understand the ramifications of completely deconstructing a previously monolithic app into all these various systems that must integrate with each other. Even the definition of a micro service is iffy. People say microservice, but a function is not a microservice. It's a hard problem to solve. Everyone wants to modernize and the patterns they keep hearing, which a lot of these Unicom companies have been throwing out, are microservices—6 or 12 factor apps, with kubernetes everywhere.

Anonymous Author
Everyone talks about microservices or APIs—everything has to be in API, has to be consumed, even streams, etc. But they don't understand the ramifications of completely deconstructing a previously monolithic app into all these various systems that must integrate with each other. Even the definition of a micro service is iffy. People say microservice, but a function is not a microservice. It's a hard problem to solve. Everyone wants to modernize and the patterns they keep hearing, which a lot of these Unicom companies have been throwing out, are microservices—6 or 12 factor apps, with kubernetes everywhere.
1 upvotes
Anonymous Author
The issue with excess point-to-point solutions is a self-fulfilling prophecy, and I think it's borne out of the acceleration and velocity that the cloud and SaaS has allowed us to achieve. How do we keep up with how much data we're creating and the solutions that we’re wrapping around it? We're stuck in this groupthink where the only solution is to create point solutions that solve this piece of the puzzle and then that piece of the puzzle, thinking we can connect it all together. But those connections are not magnets. They're demagnetized in some places.
0 upvotes