Speed, autonomy and safety of the pros behind working within a microservices framework, according to Haiping Chen, a software architect and 15-year engineering veteran. “Microservices allow us to quickly respond to the needs of the different audiences our technology serves,” Chen said. “Each feature can be developed and deployed independently.”
Independence is one of the most essential reasons a company might find a microservices architecture beneficial, Chen said. Small and focused teams deploying microservices aren’t overly reliant on timelines or data systems from other areas of the business, and the architecture also means developers are given more individual ownership over their work.
At facilities maintenance platform SMS Assist, Chen said that a sense of autonomy — as well unit testing and a cloud-native infrastructure — allows developers to release products at an expedited rate.
“Before implementing microservices, we had a release cycle of two weeks,” Chen said. “Now we’re able to release new updates as soon as they’re ready.” So how can teams best utilize microservices to simplify their tech? The following engineering leaders and teams walked Built In through best practices for keeping what to do with a computer science degree architecture as it should be: small.
No comments:
Post a Comment