This Post Has 4 Comments

1. Good book for senior devs & dev leads
   The plot of the book is extremely promising. Indeed, it contains valuable information, and I personally appreciate author’s efforts he put into this artefact.I also appreciate that the majority of topics are explained with sample codebase available on Github.Nevertheless, I managed to collect a list of pitfalls/typos I would like author to review (if possible). Because, some of the items caused issues with regards to perception of the information/statements outlined throughout the book. That’s my own opinion solely.Chapter 1- Page 16-17 — in Dev Hub org the one should enable ‘Enable Unlocked Packages and Second-Generation Managed Packages’ setting prior to running sfdx force:package:create command – The path parameter should be ‘source/formulaforce’ instead of ‘force-app’ (code snippet typo)- Page 18-19 — invalid sfdx command ‘installationkeybypass’ should not have space sign- Hard-to-follow section dedicated to package creation, version creation and managing ancestries — the samples should be aligned with codebase provided (actually, everything got broken after missteps on pages 16-17)- Statement on page 26 (right at top) — seems to be misleading (based on the context section)- Page 29 — too little information about Environment Hub & TSO and its capabilities (I’m frustrated)- Page 34 — typo in SFX word- Page 42 — non-deterministic statement with regards to Connected App packagingOverall, a lot of packaging-related topics were covered, but those are too high-level.Chapter 2- Page 53 — misleading statement about non-deterministic encryption (encrypted value is NOT the same each time)- Page 69 — typo in ‘inherit sharing’Chapter 3- Page 90 — hands-on challenge — not clear what packaging org is?- Page 96-98 — The pictures in this chapter provide screenshots from the org (known as packaging org, probably a scratch org) where component names do not contain namespace prefix — at the very beginning it was asked to update ‘sfdx-project.json’ file by appending unique NS (composed separately and uniquely for each reader) — therefore there are differences between pictures in book and the real pseudo-implementation of steps provided in the book (app creation).- Page 102 — it was a real surprise to see that provided apps (Race Management and Race Analytics) are classic ones — not Lightning Apps- Page 110 — sfdx import command does not function and errors out with ‘The requested resource does not exist’ code (the issue is related to NS prepended to all components in the org when ‘sfdx-project.json’ file was updated according to instructions in the book)- Page 113 — typo in ‘Heroku Kafa’ (should be Kafka)Chapter 4- Page 127 — typo in ‘inherit sharing’- Page 131 — calling synchronous context as ‘interactive’ context is confusing, better to keep consistent naming (same as in SF docs) — IMHO- Page 148 — typo in ‘andap’Chapter 5- Page 165-166 — typo in snippets- Page 167 — ‘keyword’ instead of ‘keyboard’- The provided repo is NOT prepared for ongoing merges (chapter by chapter branch) — the file content within repo mismatches with content from the bookChapter 6- Page 206 — typoChapter 7- Page 261 — misleading statement at the bottom with code snippet typoChapter 8- Page 287-288 — failed to set up local postgreSQL server with snippets provided — had to to comment out [ssl: { rejectUnauthorized: false }] in 2 files to make it work- Page 295 — SOQL query is invalid since the development was conducted in namespaced scratch org — hence NS prefixes should be added to referenced custom fields- Page 314 — typo (at the bottom)Chapter 9- ‘Custom Report UI and Analytics API’ — expect more content with samples (especially using reports to drive an alternative approach for records selection in Apex)- ‘Managing performance and response times’ — expected more content on this crucial topic (would be interested in optimisation techniques that improve page load + getDescriptor calls issues by SF when page loads)Chapter 10- Page 377 — no sample data for Races Data object provided- Would be appreciated if there were more content with emphasis on salesforce mobile experienceChapter 11- Page 451 — invalid Apex REST api base endpoint (it should be prefixed with ‘services/apexrest’ )- Page 466 — misleading CMT screenshot — ‘Interface Type’ field should be disabled as it was marked as ‘Upgradeable’ (DeveloperControlled)Chapter 12- Page 504 — ProcessRaceDataJob batch does NOT update Driver Name field (along with Contestant lookup)Chapter 13- Page 536 — ‘RaceControllerTestMockitoDemo’ class is not present int sample code- Page 543 — it would be appreciated if there were more samples/explanations on how fflib matchers workChapter 14 — NoneChapter 15- It would be ideal if you could provide an examples of using common OAuth flows in conjunctions with custom Auth Providers (for example — use custom auth provider plugin for server-server Client Credential Flow)Chapter 16 — None

   Reply

2. Salesforce Deep Dive: Unpacking Andrew Fawcett’s Architectural Mastery
   Disclaimer: I was provided a complimentary copy of this book for the purpose of reviewing it.Currently immersed in Andy Fawcett’s fourth edition of ‘Salesforce Platform Enterprise Architecture’, I find myself captivated by the depth and practicality of the content. While many shy away from dense technical literature, this book stands as an essential exception, especially for Salesforce developers and architects. Fawcett’s extensive experience, as evidenced by his tenure as CTO of FinancialForce and his current role at Salesforce, pours into every page, offering invaluable insights into enterprise-scale application development using Salesforce.The book is masterfully structured, making complex concepts easy to understand. Starting from the Salesforce Developer Experience (SFDX) to advanced topics like leveraging Heroku and Salesforce Functions, each chapter is meticulously crafted, making the learning process both comprehensive and engaging. I particularly appreciate the hands-on examples and real-world application of coding patterns and best practices.Fawcett explains governor limits, continuous integration, and data storage in plain English. He covers definitions, benefits, drawbacks, and tips. The book’s thoroughness demands a careful read, and I am taking my time to fully absorb the wealth of knowledge it offers.In conclusion, it’s a must-have for anyone serious about mastering the platform, whether you are an architect, developer, or business analyst. Expect to gain a profound understanding of Salesforce, armed with architectural strategies that promise scalability, sustainability, and maintainability in your projects.

   Reply

3. A Must Read For Creating Salesforce Applications For Use In The ISV and App Exchange Ecosystem!
   “Salesforce Platform Enterprise Architecture” penned by Andrew Fawcett is a goldmine of wisdom for architects and developers navigating the Salesforce landscape. With his hands seasoned in Salesforce architecture, Fawcett lends his extensive proficiency and deep-seated understanding of the platform to craft a treasure trove of knowledge for those designing and crafting enterprise solutions on Salesforce.This impressive manual is smartly segmented into logical chapters, each one progressively diving into diverse facets of Salesforce architecture. Fawcett smartly starts off by illuminating key concepts and principles, creating a strong base for newcomers to Salesforce. Venturing forward, he explores a myriad of subjects, including data modeling, security, integration patterns, scalability, performance, and deployment tactics.The true power of this book is Fawcett’s knack for making complex concepts understandable. He deciphers the nuances of Salesforce architecture, presenting them in a manner digestible for a wide spectrum of readers. No matter if you’re a rookie or a seasoned Salesforce pro, you’ll appreciate his explanatory style and illustrative examples.Another shining quality of this book is its pragmatic approach. Fawcett doesn’t just stay in the realm of theory; he equips readers with real-life examples, top-notch practices, and architectural blueprints for tackling common hiccups in Salesforce projects. This emphasis on practical knowledge makes the book a faithful sidekick for those requiring actionable guidance to architect sturdy and scalable solutions.What’s more, Fawcett’s engaging, conversational writing style makes the book a captivating read. He strikes a harmonious balance between technicalities and wider architectural concepts, ensuring readers remain intrigued and grasp the overarching narrative while still immersing into necessary details.However, one slight hiccup in the book might be its assumption of some prior familiarity with Salesforce. While Fawcett does provide introductory rundowns, those absolutely new to Salesforce might find some sections a tad tough to follow. But don’t let this dissuade beginners – the depth and breadth of knowledge that this book offers are priceless assets for those eager to become proficient in Salesforce architecture.To wrap it up, “Salesforce Platform Enterprise Architecture” by Andrew Fawcett is a superb guide that sweeps across all crucial elements of Salesforce architecture. The book, with its lucid explanations, practical instances, and comprehensive scope, serves as a precious reference point for architects and developers striving to design and construct scalable and robust solutions on Salesforce. Regardless of your level of experience, this book will undeniably boost your comprehension and expertise in Salesforce architecture.

   Reply

4. Another review declared the book as developer handbook and gave it a bad score. BUT:This book shows one good way to structure your SF code. And the book – thanks god – everytime presents implementation examples. Which is incredible valuable. You can feel the experience of all authors through the clear and little explaining steps. And thats much better than thousand whiteboards, cool models and some sky scraping, high abstract “architecture talk”. And if you read and think about it, not focusing only on the code examples it gives a rock solid application design recommendation.It is exactly what I was looking for. The many sources in the internet regarding fflib aren’t that detailed and with that many facettes explained.If you understand the details you can abstract the picture.Really like and recommend it.Am waiting for a new edition in two years 😉

   Reply