article thumbnail

Thoughts on organizing architecture

Xebia

The scope of a team often concerns a limited number of components, microservice or other functionalities. The character and way of working of the architect function has a huge impact on the engineering culture. As we move up to domain-oriented units, business lines and enterprises, we see an increase in the complexity.

article thumbnail

Thoughts on organizing architecture

Xebia

The scope of a team often concerns a limited number of components, microservice or other functionalities. The character and way of working of the architect function has a huge impact on the engineering culture. As we move up to domain-oriented units, business lines and enterprises, we see an increase in the complexity.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

6 Crucial Issues for Legacy.NET App Modernization

Datavail

For example, refreshing your.NET applications makes it much easier to adopt modern IT best practices such as cloud computing and microservices. Establishing an IT culture. Modernizing legacy applications is the perfect opportunity to reform your broader IT and engineering culture as well.

Azure 52
article thumbnail

A guide to personal retrospectives in engineering

CircleCI

I’m wondering how well the error enum translates to microservices. If you feel your retrospective shines a light on difficulties other engineers might have, share it more widely in your organization. Learning “in the open” creates a kind of safety in an engineering culture. cf “Railway Oriented Programming”, [link].

article thumbnail

The Netflix Cosmos Platform

Netflix Tech

Orchestrated Functions as a Microservice by Frank San Miguel on behalf of the Cosmos team Introduction Cosmos is a computing platform that combines the best aspects of microservices with asynchronous workflows and serverless functions. Our response was to create Cosmos, a platform for workflow-driven, media-centric microservices.

article thumbnail

2020: The Year Bee-hind Us

Honeycomb

Our existing deploy tooling and engineering culture made the transition to remote work go much more smoothly. Though our deploy velocity remained the same, the engineering org has been far from stagnant. It’s the same whether you’re running a monolith or hundreds of microservices, on a team of two or two hundred.

article thumbnail

2020: The Year Bee-hind Us

Honeycomb

Our existing deploy tooling and engineering culture made the transition to remote work go much more smoothly. Though our deploy velocity remained the same, the engineering org has been far from stagnant. It’s the same whether you’re running a monolith or hundreds of microservices, on a team of two or two hundred.