@LLYC_Global estamos tratando de contactar a su directora María José Castaño, realizamos una transferencia por error a su llave y buscamos su ayuda para que nos regrese el dinero. Ya la hemos contactado por otros medios pero solo hemos recibido el mensaje de "tarados"
@maria_mimia hola te estamos tratando de contactar por una transferencia que realizamos por error a tu llave. Por favor ayúdanos a recuperar el dinero.
@christianposta Because software is an entropic system all tech decisions over time will struggle. You make best available choice with context and constraints for what’s needed today and where you see the scale model working over the next horizon(3-5yrs).
Many people will say “producers should not know about consumers”, this is technically true… but can lead some issues around governance....
✅ Technically producers should not know about consumers
❌ But as humans we need to know and understand
When working with EDA common questions come up 👇
1. What events/messages is this service producing?
2. What events/messages can I consume from this service?
3. What is the format of these events/messages?
4. What schema version do I use?
5. Who is producing what?
6. Who is consuming what?
Here are three simple ways to start documenting your EDA and helping....
USING README FILES
Simple and cheap. If you want to document your schema, or what your service is publishing or subscribing too, maybe readme files can help? Anything is better than nothing... (maybe you think nothing is OK, but as you scale your app high chance you might need some form of discovery)
ASYNCAPI
@AsyncAPISpec is an open source specification for defining asynchronous APIS. The community has been growing over the past few years and many large organistions using it to help them define and write standards for producers and consumers. Community has a wide range of tools to help with integrating and documentation too.
EVENTCATALOG
@event_catalog is an open source static site generator for event-driven architectures. The interface gives your team a new visual way to navigate producers, consumers, domains and services.
To learn more with extra resources, find the link below
How refreshing is it when you start working on an OSS project that's a true community and not those single-vendor "owned" projects that masquerade as open.
DevOps is dead 💀, long live Platform Engineering!
1) Developers don't like dealing with infra
2) Companies need control of their infra as they grow
Platform Engineering (and Internal Developer Platforms) enable these two facts to coexist. Here's how:
(1/n)
@Astro_Isa Esos son los bonos, que ganaron en las herencias donde no había dinero. Dichos bonos solo se pueden gastar en la tienda, no es dinero del premio.