3 ms·
This perfectly describes how I feel in my current position... and why I signed an offer letter this morning to go somewhere else. We've hit hard times and no on
by EpicEng 7y ago
This perfectly describes how I feel in my current position... and why I signed an offer letter this morning to go somewhere else. We've hit hard times and no one seems to know exactly what we need to build to bring in new revenue.
So instead of figuring that out as quickly as possible and building something of value... we're building a 'platform'. No one knows exactly what the platform needs to do, but management seems pretty sure that it needs to use gRPC for APis, table storage instead of SQL, an 'onion' architecture, a multi-stage data ingestion pipeline with more visio lines than I can count, docker, CQRS, a service bus for eventing, a micro-service architecture, no direct communication between services, and a SPA front end.
While it does seem enticing to get paid (well) to play around with new tech, it strikes me as a massive waste of resources and a huge risk. I just want to build something that solves a real problem before we run out of money.
- DelightOne 7y agoMy condolences! > no direct communication between services How does indirect communication work?
- williamdclt 7y agoI suppose they mean asynchronous communication through a message broker/queue?
- EpicEng 7y agoYep, exactly.
- oulu2006 7y agoIs no direct communication between microservices necessarily a bad thing? I've made a few similar design decisions in our tech stack, we have no "direct communication" between microservices, discounting the shared database. Microservices communicate through the use of RabbitMQ. We build our system around the premise of eventual consistency, thus reducing the need of blocking computations. So-far this has served us rather well.
- DelightOne 7y agoAll has pros and cons. Here it is (async) central simple central communication vs central point of failure I guess.