3 ms·
When I hear things like that all I can think is that I have a wildly different idea of what a "service" is that it can be broken down to such a small chunk of f
by michaelbuckbee 6y ago
When I hear things like that all I can think is that I have a wildly different idea of what a "service" is that it can be broken down to such a small chunk of functionality.
Are there examples of the size of these individual services? What are they doing?
- spc476 6y agoAt work, we have: * two services that accept requests via telephony protocols (SS7, SIP, these are quite small) and forwards the request to: * the business logic component (large only because of the complexity of the business logic implemented). When there's some state changes, it sends a request to: * the replication module (say, midsized), which ensures that the state change is replicated at The Other Site to handle geographical redundancy (a requirement from our customer). * There's one other microservice that the business logic uses and that's to send some data to Apple so they can hand it off to iOS phones (all our stuff internally uses UDP (except for the SS7 stuff)---the addition of a TLS based service was too much to add to the business logic component and this is quite small as well). All of these modules are owned by the team I'm on, namely due to the esoteric nature of it (the telephony protocols, this is real time since it's part of the call path [1], etc.). Within our team, we can work on any component, but generally speaking, we tend to specialize on a few components (I work with the telephony interfaces and the Apple interface; my fellow office mate deals with the business logic). [1] As a cell phone call is being made.
- michaelbuckbee 6y agoThanks for replying, I'm so used to thinking of just CRUD apps or fairly small sized projects, this was really helpful.