proophOS (@proophOS) header
proophOS (@proophOS) profile picture

Official #prooph components twitter account. https://nitter.gq/t.co/yZQ84yi9oC Maintained by Alexander and Sascha.

Joined July 2019
Photo by proophOS (@proophOS)
For support please join our #improoph chat: gitter.im/prooph/improoph
🎥 New video available 🎥 See how you can use Cody to connect #proophboard with EventCatalog and learn the basics. I'm using our @nodejs @typescript version of Cody available as open source package on @npmjs 👉 youtu.be/0FAgsPNqUV4
2
3
4
Started w/ ZF1. When ZF2 came out I looked at @symfony 1 w/ #ActiveRecord. I stayed w/ ZF and @doctrineproject ORM. Later I had to check out #rubyOnRails - again AR. Switched to symfony2 & ORM. Never tried @laravelphp because of AR. Today I mostly do #eventsourcing w/ @proophOS .
This Post is from an account that no longer exists. Learn more
3
2
Replying to @ArkadiuszKondas
events!
2
1
4
Yesterday we did a full day internal workshop on #proophboard. 6h Business Model Canvas, Capability and Wardley Mapping with @christofheinzel @_mschilling_ Take away: Way less exhausted compared to "traditional" remote set up. The video avatars seem to pay off. 💪
Working on a new #proophboard wiki page: How to implement your own Cody server: wiki.prooph-board.com/Cody-S… Pretty cool: you can open an API contract hosted on github with a direct link to editor.swagger.io/?url=https…
3
5
One of the reasons why we decided to become a sponsor of @EventSrcLive . This conference should have existed 10 years ago. It's finally time to provide a space for people to get in touch w/ #EventSourcing and learn what you can do with it. See you there? nitter.gq/mathiasverraes/status/…
Hey, it's @EventSrcLive next week! Now there's a conference I wish existed 10 years ago, back when the only way to learn about eventsourcing was to go and eat ribs with @yreynhout @tojans @ONE75 @JefClaes
2
4
5
"Classic implementation"? No, it is NOT.
15
30
5
119
ok, #prooph/event-sourcing is deprecated since a while now but this does not stop the community to make it compatible with #PHP 8. So here we go, new release available: github.com/prooph/event-sour…
4
6
#InspectIO ships with a fixed set of cards that you can use for modeling. This makes it easier to create consistent event maps across different teams and enables coding bot assistance. However, nothing stops you from defining your own legend and use it for exploration sessions.
6
5
Just finished the Ecotone tutorial. If you miss #prooph/service-bus, I highly recommend to check it out. It's service-bus on steroids thanks to #PHP 8 attributes. @DariuszGafka used the full potential of native PHP annotations. Impressive! docs.ecotone.tech/tutorial
1
9
10
#Cody key facts for a customized version tailored to a client's internal framework. Can't wait to see it in action and collect feedback from the teams.
3
7
Visual modeling + coding bot is a great opportunity for a #prooph event-sourcing revival. Thoughts? nitter.gq/prooph_software/status… Join discussion on Github: github.com/prooph/event-sour…
From #EventStorming to working code with assistance of a coding bot. Check out our new tutorials: github.com/event-engine/insp… Available for @nodejs and #PHP
2
2
Has anybody tried to implement something similar w/ #PHP & @proophOS ? axoniq.io/product-overview/a… #EventSourcing #GDPR #DSGVO #AxonFramework
1
2
2
Once you can switch metadata editor to a syntax other than JSON, this will open the door for #FPP integration in #InspectIO and the code generator. So you can design #prooph/micro services in #InspectIO #ExcitingFuture nitter.gq/prooph_software/status…
#InspectIO aims to combine problem and solution space in one tool. With the new Metadata support we get a huge step closer to that goal. Learn more: github.com/event-engine/insp… #RemoteEventStorming #DDDesign #LivingDocumentation
3
3