consider using a BPMS for processes with the following characteristics: The process is distributed, i.e., spanning multiple applications The process involves complex rules If the process is complex overall If you have a need to monitor the process The process requires improvement If many instances of the process will be deployed If you have sufficient… Read More »
I was going through a bunch of old slide decks last week and came across this one particular slide that struck me. I think it gave me pause because I don’t normally use the slide, and I hadn’t seen it in a long time. I think the material is workwhile for anyone thinking about using… Read More »
An ESB brings flow-related concepts such as transformation and routing to a Service-Oriented Architecture. In an enterprise architecture making use of an ESB, an application will communicate via the bus, which acts as a message broker between applications. Such an approach has the primary advantage of reducing the number of point-to-point connections required to allow… Read More »
Many of us have had to ponder this question. Technology selection is notoriously difficult in the enterprise space since the criteria and complexity of the problem is often not fully understood until later in the development process. There is an interesting post from ThoughtWorker Erik Dörnenburg with the unfortunate title “Making the ESB pain Visible”.… Read More »
Increasing organizational agility by reducing time to market for new initiatives is one of the most common reasons that companies implement an ESB as the backbone of their IT infrastructure. An ESB architecture facilitates this by providing a simple, well defined, “pluggable” system that scales really well. Additionally, an ESB provides a way to leverage… Read More »
Answers to some of the most important questions surrounding the term “enterprise service bus” using concrete examples, so that the areas of application that can be deemed “correct” for ESBs can be clarified. Part of the Industrial SOA article series July 2013 Introduction Everyone seems to need to use an enterprise service bus (ESB) nowadays,… Read More »
Nathan Marz came up with the term Lambda Architecture (LA) for a generic, scalable and fault-tolerant data processing architecture, based on his experience working on distributed data processing systems at Backtype and Twitter. The LA aims to satisfy the needs for a robust system that is fault-tolerant, both against hardware failures and human mistakes, being… Read More »
Lambda Architecture: A state-of-the-art It’s been some time now since Nathan Marz wrote the first Lambda Architecture post. What has happened since then? How has the community reacted to such a concept? What are the architectural trends in the Big Data space, as well as the challenges and remaining problems? Big Data: Batch processing-only Despite… Read More »
This is guest post by John Piekos, VP Engineering atVoltDB. I understand this is a little PRish, but I think the ideas are solid. The focus of many developers and architects in the past few years has been on Big Data, specifically mining historical intelligence from the Data Lake (usually a Hadoop stack containing terabytes… Read More »
Introduction Relational database transactions are ACID and the strong consistency model simplifies application development. Because enabling Hibernate caching is one configurations away, it’s very appealing to turn to caching whenever the data access layer starts showing performance issues. Adding a caching layer can indeed improve application performance, but it has its price and you need to be aware of it.… Read More »