Skip to content

Commit c95412c

Browse files
authored
Add new Deprecation FAQ page to Event API
* Add new Deprecation FAQ page to Event API * Few fixes - link to Migration playbook is still missing * Add links to Migration guide * Change text for some links
1 parent 686d951 commit c95412c

File tree

2 files changed

+56
-1
lines changed

2 files changed

+56
-1
lines changed

content/events-api/deprecation-faq.md

Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
# Deprecation FAQ
2+
3+
::: info
4+
The Event API will be retired on **December 31, 2026**.
5+
:::
6+
7+
## Why Event API will be retired?
8+
9+
Event API no longer meets evolving needs of our customers:
10+
11+
- Impossibility to scale over 4000 events per hour and 3 event subscribers.
12+
- Only two types of events are proposed. No possibility of choice.
13+
- Akeneo doesn’t guarantee a delivery or retry system of events.
14+
- Event API doesn’t support events related to Product Cloud.
15+
16+
This is why we built [Event Platform](../event-platform/overview.html) to succeed it.
17+
18+
## I have a critical integration with the Event API, what happens now?
19+
20+
There is no immediate impact.
21+
Until its retirement on December 31, 2026, Akeneo will continue supporting Event API.
22+
23+
We encourage you to start your migration to the new Event Platform as soon as possible to avoid any interruption in your integrations.
24+
25+
We provide you a dedicated [Migration Guide](./migrate-to-event-platform.html) to help you do so.
26+
27+
## Can I use both?
28+
29+
Yes, you can use both in parallel to ease your migration process.
30+
31+
However, please keep in mind that the Event API will be deprecated by the end of the given period, so you will eventually need to migrate all your existing integrations to our new platform.
32+
33+
## What are the benefits of the new Event Platform?
34+
35+
Event Platform comes with a lot of new benefits to cover previous lacks of Event API:
36+
37+
- Much more events (+30 events available today)
38+
- No restriction on number of events, quotas only
39+
- “At least once” delivery guarantee & retry system in place
40+
- Product deltas enable efficient updates
41+
42+
You can find more details [here](../event-platform/overview.html).
43+
44+
## What should I do to migrate to the new Event Platform?
45+
46+
You can follow our dedicated [Migration Guide](./migrate-to-event-platform.html) and the new [Event Platform](../event-platform/getting-started.html) documentation.
47+
48+
## I need help with this migration, what are my options?
49+
50+
For any help, you can always contact [Akeneo's Support](https://akeneo.atlassian.net/servicedesk/customer/portal/8).
51+
52+
## What should I do if the new Event Platform doesn’t cover my specific use case?
53+
54+
You can contact your CSM so we can find an appropriate answer to your needs.

tasks/build-doc.js

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -797,7 +797,8 @@ gulp.task('build-events-api', ['clean-dist','less'], function () {
797797
'security.md': 'Security',
798798
'limits-and-scalability.md': 'Limits and scalibility',
799799
'more-about-events.md': 'More about events',
800-
'migrate-to-event-platform.md': 'Migrate to Event Platform'
800+
'migrate-to-event-platform.md': 'Migrate to Event Platform',
801+
'deprecation-faq.md': 'Deprecation FAQ'
801802
};
802803

803804
var isOnePage = false;

0 commit comments

Comments
 (0)