Changes for page 220 - Patch Parade
Last modified by Carlijn Kokkeler on 2024/05/22 13:30
From version 219.1
edited by Carlijn Kokkeler
on 2024/04/08 14:57
on 2024/04/08 14:57
Change comment:
There is no comment for this version
To version 189.1
edited by Carlijn Kokkeler
on 2024/01/15 16:23
on 2024/01/15 16:23
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -21 8-Sprightly Spring1 +212 - Failover Fiesta - Content
-
... ... @@ -1,13 +1,16 @@ 1 -In the last sprint cycle, we focused on r eleasing a majorversion of our [[current runtime>>doc:Main.eMagizAcademy.Fundamentals.fundamental-runtime-generation3||target="blank"]] baseimage for all our clients running on the [[currentruntime>>doc:Main.eMagizAcademy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture.Pleaserefer toour new [[runtimeimage>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V3.0.0/||target="blank"]]andSpring 6 [[migration path>>doc:Main.eMagiz Support.MigrationPaths.migration-path-spring-6-migration.WebHome||target="blank"]]formoreinformation.Apartfrom this, we haveimprovedevent streaminglogging,suchthat theselogsare not clutteredwithirrelevantinformation anymore.Moreover,we haveremovedthedeprecatedcloudption'Root' from theportal.1 +In the last sprint cycle, we focused on providing new cloud templates that improve auto-healibng. Moreover, components and deployment steps have been created to support a failover setup. Lastly, bug fixes regarding message mapping and topic data models have been done. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.21 8-Sprightly Spring||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.212 - Failover Fiesta||target="blank"]]. 4 4 5 5 =====New features===== 6 6 7 -* Architecture: Several components are affected by the migration to Spring 6. Please check out our [[Release blog>>Main.Release Information.Release Blogs.218 - Sprightly Spring||target="blank"]] for specifications. 8 -* Architecture: Moving the eMagiz runtime stack from Spring 5 to Spring 6 and from Java 8 to Java 17, includes moving to latest (major) versions of open source projects, libraries and technologies. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]] will be released. Although no new functionality is added in this new image version, several Spring libraries have been changed significantly. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V3.0.0/||target="blank"]]. 7 +* Deploy - Cloud Templates: New Cloud Templates are available for single and double environments to introduce improved auto-healing. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information. 8 +* Create - Flow Designer: New components have been created to support a failover setup. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]]. 9 +* Deploy - Deployment plan: Two new deployment step types are introduced to incorporate failover actions during deployment. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]]. 9 9 10 -=====Minor changes===== 11 -* Manage - Monitoring: Event streaming processors will produce significantly less logging, so the logs are not cluttered with irrelevant info logs. 12 -* Deploy - Cloud: Options and screens related to the deprecated cloud option 'Root' have been removed from the portal. 11 +====Bug fixes==== 13 13 13 +* Design - Message Mapping: The message merging tool has been fixed to allow merging a store item message model into your own message models. 14 +* Design - Topic Data Model: It is possible to generate a JSON Example of a topic whose schema has nested elements. 15 + 16 +