Copy
View this email in your browser

Dear Architect,

Welcome back to our weekly issue!

This week we have in our spotlight a post from Martin Fowler's blog regarding the benefits and pitfalls of a Platform team inside an organization.

Then a case study on how and why Coinbase moved their application to React Native from native applications.

I found particularly interesting a couple of articles on architecture decisions making, what should be the architect focus on and different techniques to take an objective decision.

Finally a case study on applying an event-driven architecture for a specific use case of Machine Learning.

Enjoy the read and see you next week!

In the SPOTLIGHT

Platform Strategies

Mind the platform execution gap

Developer productivity platforms are increasingly recognised as a way to manage the cognitive load of engineering teams and decrease time to market for new features.
However, there are baseline capabilities that organisations need to cultivate in order to successfully execute on a platform strategy.
The platform team needs to think of the platform as a software product, needing dialog with its users, attention to reliable operations, and a healthy team environment.

Case Study

Announcing Coinbase’s successful transition to React Native

The transition from native to React Native did not happen overnight, and in the interest of helping those contemplating such a decision, we want to tell the story of how we got here

Software Architecture

Less is More with Minimalist Architecture

So, in addition to every other tough job you have as an architect, you must figure out the right balance of architecture and anarchy for your organization.

Event-Driven Architecture

Event-Driven Architecture Can Clean Up Your Noisy Machine Learning Labels

In Riskified’s case, the labels are mutable. This means the labels can change over time. Additionally, the labels are derived from multiple fields. Why is this an issue? As a company grows, so does the number of labels and fields in use. As a result, there is no single person who knows them all, and this may cause data loss.
Software Architecture

How Technology Architects make decisions

In a fantastic paper published in 2014, “EA Anamnesis: An Approach for Decision Making Analysis in Enterprise Architecture”, Georgios Plataniotis, Sybren de Kinderen and Henderik Proper explain the importance of capturing decisions made about architecture.

Thanks for reading Dear Architects 🙏

If you have any suggestions to make this newsletter better, just drop us an email!

Have a great rest of the week 😉

Opinions are my own

HELP US TO IMPROVE THIS NEWSLETTER!
We just need a few minutes of your time to make Dear Architects even better
Sure! Let me share what I think about Dear Architects!
Twitter
Website
Copyright © 2021 deararchitects, All rights reserved.


Want to change how you receive these emails?
You can update your preferences or unsubscribe from this list.

Email Marketing Powered by Mailchimp