🟢 The Art & Science of CAP

[@pawem.9684]

Thanks!

[@wiseskeshom4673]

Nice presentation, great content as always. Thanks for sharing.

[@abhishektiwari2789]

Amazing explanation. Thank you for aspect oriented extensibility concepts

[@TribhuwanPant]

When I started CAP almost a year ago, I saw a lot of emphasis on DDD in documentation and I didn't know much about DDD. Since then, I spent significant time learning DDD. Today, I realize that, as a developer, the first step in Domain Modeling-i.e., finding domain experts in projects and deciding on 'ubiquitous language' with the help of domain experts-is the most challenging part of project requirements. Also, while going through the Capire documentation, I struggle to correlate many DDD concepts with their CAP counterpart. For example, it discusses value objects, but I am not sure how to utilise features of Value Objects in CAP such as immutability, structural equality, validations at VO level, etc. At one place, the documentation states that "the DDD concepts of Repositories, Aggregates, and Factories intentionally don't have first-class counterparts in CAP but can be realized using CAP's core concepts." If you could help us understand how these can be realized in CAP, it would be great.

[@sapdevs]

Great comment, thank you. Domain modelling is indeed a key part of any project, and a much underrated one at that. And yes, I agree that it can be challenging. We will certainly endeavour to help tease out the subtleties in CAP in this area over the course of this series. [dja]

[@patterjo9]

Interesting discussion, i really enjoyed the bit on what CAP isnt, highlighting when you develop in Java and ABAP you start thinkng in Java and ABAP. As much as DJ has disdain for Java and ORM its clear CAP is heavily influenced by these two technologies, in Java CAP there are some cool tools around monitoring and observability not in the NodeJS version, maybe thats the maturity that comes wth thinking in Java, likewise with ORMs and the frameworks like Rails which built upon the ORM abstractions and lead to sensible defaults, convention over configuration and Spring which took it further making annotations a central part of its programming model. I do like the format, through the comparison with other techniques we can see the strengths, best practices and opportunities to grow.

[@sapdevs]

Thank you John, always great to hear from you. "Disdain" is a strong word, but appropriate, to be honest :-) Seriously though, I strive for "strong opinions loosely held" so, dear folks who don't know me so well (as well as John does) - please take everything I say with a pinch of salt. I'm looking forward to the next installment with Daniel as much as you all are, too. [dja]

[@nicoschonteich1916]

Interesting how you explained that CAP as a framework grew out of cds, sort of being it's v2. Probably the reason the technical name (for the packages, e.g. npm) of CAP is "cds", and not "cap". Provocative question: If you could go back in time, would you have called the packages "@sap/cap" and "@sap/cap-dk" if you knew how they would mature in the future?

[@danielhutzel7967]

We rather would have called the whole thing CDS instead (note: the S in CDS always stood for Services. i.e. the runtime part)... weren't allowed to do so as there was concerns about CDS becoming too prominent ... ;)

[@sapdevs]

Hey Nico! That's a great question, I'll try to remember to relay that to Daniel in the next session (and/or you can remind me ;-)) And of course, this ties in with the two hard things in computer science: naming things, cache invalidation, and off-by-one errors ;-) BTW there's a further interesting debate as to the content of .cds files - technically that content is CDL (cap.cloud.sap/docs/cds/cdl) not CDS. But that's a discussion for another time. [dja]

[@xyz99206]

Can you please make video on how UI annotations work, how to idnentify which annotations to use where?

[@test1-g5k]

Hello, guys, thank you for your insights. Of course, I would appreciate it if you with your sessions.

[@20cmusic]

I've been working on cds amdp ui5 fiori stuff since 2018 and I think It's still terrible. Actually your developement model makes no sense. SAP has added more complexity every year. Everything you do can be done with simple rfc and nodejs web dev.

[@sapdevs]

I can't say I agree with you there, but you are of course welcome to your opinion. If simple RFC and Node.js Web development works for you, that's great. [dja]