Much of the writing I’ve done in this space over the past few years has been geared towards microservices and scalable architectures based on innovations in cloud providers’ technologies. But sometimes the way that we talk about microservices architectures implies that they are the only good solution and monoliths are bad. Are they?
What we have to say, what you want us to hear.
That’s how our blog works. It’s interactive. Let’s learn together.
How long should a team spend analyzing something before doing something?
A team I work with recently used a "spike" to investigate how to implement a new system capability. The spike was open for two sprints, although I am not sure how much effort was expended over the course of those two sprints. The fact of this spike being open for two sprints made me curious about the trade-offs made… given the agile value of Working Software over Comprehensive Documentation, was the team leaning too far in the direction of comprehensive documentation? And if so, how would they know?
In thinking about this trade-off, I like the following thought experiment… what would each extreme look like?
One of the many benefits of working at ISE is the diversity of projects our team members are working on. Whether it be a project for work or just some tinkering at home, the people at ISE have experience with a wide variety of tools.
Meet Our Team Q&A series. My name is Daniela Williams, Project Manager at ISE, and I’ll be asking ISE team members questions to help give insight into what makes us tick.
It's Customer Service Week! Today I'm interviewing Brian Trieschmann, Client Support Representative for the ISE Fleet Services division of ISE. If you have a question about eFleetSuite on our A317 or the web application, he's here for you.