Software Engineer and jack-of-all-trades, mostly working with machine learning and AWS.
Interested in the trends in tech and working out how we can use them!
Interesting - so when you abstract out this common functionality do you find there can be much bloat in the packages that you’re creating? Lots of unused methods etc?
I’m thinking of how we could implement something like this, wrapping it up like some helper libraries we’ve created in the past but we’ve always ended up ballooning the scope of each lib
Current CTO exploring entrepreneurship on the side; coach; mentor; instructor.
Dedicated to promoting digital literacy and ideological diversity in tech.
This is for our backend projects, so package size typically isn't so much an issue.
Additionally, our use of dependency injection patterns makes our services fairly efficient.
From a use perspective, we typically only include functionality that is shared amongst all of our other Microservices. We've purposely designed our applications to promote interoperability.
Software Engineer and jack-of-all-trades, mostly working with machine learning and AWS.
Interested in the trends in tech and working out how we can use them!
Interesting - so when you abstract out this common functionality do you find there can be much bloat in the packages that you’re creating? Lots of unused methods etc?
I’m thinking of how we could implement something like this, wrapping it up like some helper libraries we’ve created in the past but we’ve always ended up ballooning the scope of each lib
This is for our backend projects, so package size typically isn't so much an issue.
Additionally, our use of dependency injection patterns makes our services fairly efficient.
From a use perspective, we typically only include functionality that is shared amongst all of our other Microservices. We've purposely designed our applications to promote interoperability.
Sounds really sustainable, this seems like it'll be a longer-term goal for us but could have some big payoffs,
Thanks for sharing!