Summerbatch

Point in time Restart

Summer batch Supports both transactional and non-transactional workload.

Transactional workloads benefits from Summer Batch embedded database controls, including point in time restart and let you focus exclusively on writing your business logic.

Cloud Independent .NetCore Batch Framework

Don’t become dependent on yet another technology and deploy your batch workloads on any cloud, container or bare metal systems.

Horizontal Scaling

Scale Horizontally node by multi-threading a workload in few clicks. No code required.

Integrate with your Mainframe

Integrate with EBCDIC files using pre-provided tasklets, and start exchanging with your Mainframe and Midrange system.

Coming Soon!

Summer Batch Introduces Vertical Dynamic Scaling Capabilities

Scale your batches on several nodes and leverage cloud and containers infrastructure elasticity.

Summerbatch comes now in two flavours

Summer Batch Core is an open-source framework developed by Blu Age and Accenture to enable efficient processing of millions of records in the .Net ecosystem. Easy to deploy and scale, start using Summer Batch and focus on your business logic.

Open-source batch framework for .NET and .NET Core

to cover typical bulk processing

At start, Summer Batch is a joint initiative of Blu Age and Accenture to bring the C# Community a lightweight, reliable, efficient batch framework based on proven concepts - distributed for free under an Apache 2 license. Its design has been driven by the concepts exposed in the JSR-352 specification which is a java colored but exposes universal batch concepts.
Its purpose is to help users to:

build new batch solutions to be run on Microsoft®-based environments;
provide modern architecture patterns that facilitates migrating batch to modern Microsoft®-based environments.

Blu Age has developed a companion product to modernize Cobol Batches to a Summer Batch target, part of the Legacy Procedural to Cloud family. Feel free to contact us to get more details.

Contact-us

Download

The current GA is the 1.2.6 - July 2021 Release.
The Summer Batch binaries can be checked out from Nuget.org nuget.org/packages/SummerBatch
The sources can be browsed and downloaded from github github.com/SummerBatch, as well as issues tracking.

The current GA is the 3.0.4 - July 2021 Release.
The Summer Batch Core binaries can be checked out from Nuget.org nuget.org/packages/SummerBatchCore
The sources can be browsed and downloaded from github github.com/SummerBatch/SummerBatchCore, as well as issues tracking.

Support offering

Need help architecting or developing your batch workload?
Blu Age has a long experience in Batch Processing ( Spring Batch / Summer Batch)?

Contact-us

Do you have Summer Batch workload in production?
Leverage Summer Batch support and benefit from our in depth expertise to resolve your business critical issues on time.

Support Terms of Service

	Self-support	Premium Support SummerBatch	Business Critical Support
Price	0$	$3,000 / month	$12,000/ month
Duration	unlimited	6 months to 5 years	6 months to 5 years
SummerBatch updates	Included	Included	Included
Online self-solve resources	Included	Included	Included
Mail support		Included	Included
Remote Support		Up to 10 hours of Webex remote support per month	Up to 40 Hours of Webex per month
Number of supported requests		5 / months	10 / months
Access to designated support engineers			Included
Root Cause Analysis (RCA)			Included
Feature Request Assistance			Included
Technical guidance with framework upgrades on your batches			Included

Support Terms of Service

Severity One means production server or other mission critical system(s) are down and no workaround is immediately available and (i) all or a substantial portion of Licensee’s mission critical data is at a significant risk of loss or corruption; (ii) Licensee has had a substantial loss of service; or (iii) Licensee’s business operations have been severely disrupted.

Severity Two means that major functionality is severely impaired such that (i) operations can continue in a restricted fashion, although long-term productivity might be adversely affected; (ii) a major milestone is at risk; ongoing and incremental installations are affected; or (iii) only a temporary workaround is available.

Severity Three means a partial, non-critical loss of functionality of the Software such that: (i) the operation of some component(s) is impaired but allows the user to continue using the Software; or (ii) initial installation milestones are at minimal risk.