We are Ready to Accept Your Contributions to EdU
Share your wisdom on event-driven systems with our ever-growing EdU community
EdU envisions building a vibrant community around asynchronous, event-driven, and reactive software architectures. We are always looking for great content to help architects, developers, and IT leaders build better systems than yesterday.
EdU attempts to centralize, curate, and distribute high-quality content on massively scalable and reliable event-driven systems among like-minded people.
If you have a background in this space, we are more than happy to share your experiences among our ever-growing EdU community.
Areas we are interested in
We would like your contributions in the following areas.
- Event-driven, highly scalable systems architecture
- Messaging systems (message queues and pub/sub-systems)
- Event-driven Microservices (DDD/CQRS/Event souring)
- Event-driven integrations (Use cases that trigger business logic in reaction to events. E.g., Serverless/FaaS)
- Stream processing
- Change Data Capture (CDC) and real-time data pipelines
- Reactive programming
Of course, you don’t have to limit yourself only to the above. But consider those as some starting points.
Types of content we are looking for
We are looking for articles and tutorials that fit into following criteria.
We accept articles that:
- Explains the concepts of a technology or a product. For example, How Event Sourcing works, How AWS SNS retry logic works, etc.
- Compare and contrast technology choices. For example, Why X is better than Y.
- Explains the best practices and lessons learned while working with technology.
We accept tutorials that:
- Provide a step-by-step guide to building a use case with a particular tool. E.g., How to build a real-time fraud-detection system with Apache Flink and Kafka.
There’s no strict restriction on the length of the material. However, as a rule of thumb, make sure to limit your piece to 2000 words.
Before you submit content
When you are submitting content, please make sure the following requirements are met.
- The content should be original.
- If the diagrams and images are not your own work, please mention the source or attribute them accordingly.
- Content should look OK grammatically.
- Content should be formatted properly for better readability. For a reference, check this style guide from Better Programming.
The submission process
- Drop an Email to email@example.com with a draft link to your story.
- Our team will add you as a writer.
- Follow these instructions on Medium to submit a story.
- We will review and maybe edit your story if needed. If it meets our criteria, as mentioned above, we will publish it.
- The EdU team will promote your story in relevant places, including social media, for better visibility and help more people discover your article. In the meantime, you can also promote the published content across your social channels. Be sure to tag us @EventUtopia so we can help you promote.
We will read each submitted article carefully and edit them if needed. Hence, it might take some time to get back to you. However, we value your time as well. If you don’t hear from us after 72 hours, please consider that your submission was not accepted.
The Event-driven Utopia publication on Medium brings you fresh content weekly. Follow @EventUtopia and @dunithd to stay up to date.