Nick Evans

Doing my best to build the right things right.

[Nick Evans @npcevans]

Practices for scaling architecture decisions: RFC's, working groups and guilds @patkua at #OReillySACon

[Nick Evans @npcevans]

We should build villages not skyscrapers - simple buildings that combine harmoniously @allenholub at #OReillySACon

[Nick Evans @npcevans]

Operationalizing machine learning models is an increasingly important challenge. How do we run these models on heterogeneous hardware while maintaining the ability to debug these models when they fail. @bsletten at #OReillySACon

[Nick Evans @npcevans]

Do you ever think about the carbon footprints of large scale machine learning models running in the cloud? @bsletten at #OReillySACon

[Nick Evans @npcevans]

Prioritize ruthlessly, reinvest in your existing systems, let's talk about messy evolution - so no rebuild after all? @z00b #OReillySACon

[Nick Evans @npcevans]

On the refactor - rewrite continuum, the sweet spot is probably on the refactor side @z00b at #OReillySACon

[Nick Evans @npcevans]

Embrace modularity but be cautious of granularity - @markrichardssa at #OReillySACon

[Nick Evans @npcevans]

Dimensions of service granularity: functionality, db transactions, data dependencies (schema ownership), workflow/choreography (inter-service communication) - except functionality, all dimensions prefer service consolidation.@markrichardssa at #OReillySACon

[Nick Evans @npcevans]

shared lib, shared service, code replication, service consolidation - 4 techniques for dealing with shared code in microservices @markrichardssa at #OReillySACon

[Nick Evans @npcevans]

DDD + Continuous delivery + cloud envs + biz agility = rise of microservices @markrichardssa #OReillySACon

[Nick Evans @npcevans]

@_ananyaneogi f1 returns the object whereas f2 returns undefined.

[Nick Evans @npcevans]

@Ruurtjan Yes agreed: "amount of effort they save other teams", that is indeed the crucial point.

[Nick Evans @npcevans]

@seldo @briankardell @Amorelandra I so agree with this: The representation of your object in memory depends what you intend to do with it, and context-sensitive representation is not a feature of OO design.

[Nick Evans @npcevans]

My takeaways from #OReillySACon

https://t.co/xI1isRCLSQ

[Nick Evans @npcevans]

@vladikk @Heimeshoff Indeed, so the UL is more like a discipline, but doesn't have a canonical physical embodiment.

[Nick Evans @npcevans]

When doing #DDD, always invest up front in establishing a clear ubiquitous language. Not doing this will result in confusion and wasted effort down the line.

@vladikk #OReillySACon

[Nick Evans @npcevans]

@vladikk @Heimeshoff Do you give the UL a physical form (in documentation) or is the refinement just making sure you have "good quality" talks with domain experts?

[Nick Evans @npcevans]

@SzymonPobiega @stilkov Haha, thanks, good point! I wasn't entirely sure, but I thought I guess sometimes you might want to advise in favour of a particular vendor.

[Nick Evans @npcevans]

Dogma + experience + pragmatism + flexibility + minimalism + trends/future needs + experiments/pocs + hands on + vendor advice = The Successful Architect

@stilkov #OReillySACon

[Nick Evans @npcevans]

@aboutlo @matteocollina You get the best hello world app you've ever seen! 😉

[Nick Evans @npcevans]

1+ million lines of code in node_modules for a hello world app with eslint, tap and create react app. No worries! NPM has solved the software reuse problem. @matteocollina #OReillySACon

[Nick Evans @npcevans]

By performing stream processing in @apachekafka you can do projections/aggregations/joins that you would otherwise do when querying the database. In this way different consumers can store data exactly as they need it.

@benstopford #OReillySACon