index.xml

<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>RedElastic</title>
    <link>http://redelastic.com/index.xml</link>
    <description>Recent content on RedElastic</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 12 Feb 2017 00:00:00 +0000</lastBuildDate>
    <atom:link href="http://redelastic.com/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Blockchain: Reality or Marketing Hype?</title>
      <link>http://redelastic.com/webinars/2017-01-02/</link>
      <pubDate>Sun, 12 Feb 2017 00:00:00 +0000</pubDate>
      
      <guid>http://redelastic.com/webinars/2017-01-02/</guid>
      <description>&lt;p&gt;Blockchain has made waves in the news over the past year. In this webinar, we&amp;rsquo;ll explore its relationship by diving into the practical implications of the technology, such as the practicality of a private blockchain in banking and early implementations such as BigchainDB.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Creating Evolutionary Architectures with Akka and DDD</title>
      <link>http://redelastic.com/webinars/2016-12-20/</link>
      <pubDate>Tue, 20 Dec 2016 00:00:00 +0000</pubDate>
      
      <guid>http://redelastic.com/webinars/2016-12-20/</guid>
      <description>&lt;p&gt;Architectures should be flexible and adaptable to ever-changing market conditions and business drivers. Unfortunately, most software architectures are inflexible and brittle. In this webinar we&amp;rsquo;ll show you practical solutions for implementing radical agility in your systems through sound integration decisions using Akka, a distributed systems toolkit for the JVM.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Play Concurrency: Under the Hood</title>
      <link>http://redelastic.com/blog/play-concurrency</link>
      <pubDate>Mon, 19 Dec 2016 00:00:00 +0000</pubDate>
      
      <guid>http://redelastic.com/blog/play-concurrency</guid>
      <description>

&lt;p&gt;Play is an MVC framework for the JVM that breaks away from the Servlet standard, which allocates a thread-per-request. Rather, Play embraces a fully reactive programming model through the use of &lt;em&gt;futures&lt;/em&gt; for asynchronous programming and &lt;em&gt;work stealing&lt;/em&gt; for maximizing available threads. Tight integration between Play and Akka also opens up avenues for distribution of work and state across clusters, even clusters that span data centers.&lt;/p&gt;

&lt;p&gt;It is by far the most powerful and flexible MVC framework in the industry.&lt;/p&gt;

&lt;p&gt;Not only does Play has some extreme advantages over Servlet-based MVC frameworks like Spring, it also fully supports two key languages on the JVM: Java and Scala.&lt;/p&gt;

&lt;h2 id=&#34;futures-actors-and-work-stealing&#34;&gt;Futures, actors, and work stealing&lt;/h2&gt;

&lt;p&gt;A combination of &lt;em&gt;futures&lt;/em&gt;, &lt;em&gt;actors&lt;/em&gt;, and &lt;em&gt;work stealing&lt;/em&gt; makes Play one of the most flexible, performant, and resilient MVC frameworks in the industry.&lt;/p&gt;

&lt;p&gt;Play employs &lt;em&gt;futures&lt;/em&gt;, which can be considered a form of event-driven concurrency. This is nothing novel; many frameworks such as Node.js feature event-driven concurrency as well.&lt;/p&gt;

&lt;p&gt;The clever innovation in Play is the use of &lt;em&gt;work stealing&lt;/em&gt; for scaling up and &lt;em&gt;actors&lt;/em&gt; for scaling out. This combination allows Play to scale out and in across both axis.&lt;/p&gt;

&lt;p&gt;In order to understand what futures and work stealing bring to the table, we need to start from the bottom and work our way up. All example Play code is written in Scala, although Play also has an excellent API for Java.&lt;/p&gt;

&lt;h3 id=&#34;work-stealing&#34;&gt;Work stealing&lt;/h3&gt;

&lt;p&gt;Under the covers of Play, work stealing is implemented with the &lt;a href=&#34;http://docs.oracle.com/javase/tutorial/essential/concurrency/forkjoin.html&#34;&gt;ForkJoin Framework&lt;/a&gt; (JSR-166). ForkJoin was first added to Java 7 and refined in Java 8, making it more efficient for Java developers to write concurrent/parallel code and avoid the complexities of locks, monitors, and synchronization.&lt;/p&gt;

&lt;p&gt;Let’s explore parallelism as two distinct categories, divide-conquer and work stealing.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Divide-conquer&lt;/strong&gt; is the process of taking a long-running computation, splitting it up, and executing both sides of the computation in parallel before joining the results together.  If we apply the same approach recursively, we can continue to divide our work into smaller and smaller halves until the individual tasks become small enough to compute.&lt;/p&gt;

&lt;p&gt;For instance, if we’re summing a list of integers, we can decide that the largest list we want to work with has 1,000 elements. If the original list has 10,000 elements, we first split the list in half, and split those halves in half, and keep splitting until the maximum list size we work with has 1,000 elements. At that point we can execute the tasks in parallel and join the results together.&lt;/p&gt;

&lt;p&gt;Divide-conquer makes efficient use of multi-core processors because creating smaller tasks and handing them off to the runtime makes it easier for the runtime to &lt;em&gt;schedule&lt;/em&gt; the tasks according to the overall capacity of your system. For instance, if the CPU is mostly idle, the tasks can be spread across available cores and run in parallel, whereas if the CPU is already busy with other things the CPU can decide to interleave smaller tasks with other operations happening on the CPU so all programs make a reasonable amount of progress concurrently without hanging.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Work stealing&lt;/strong&gt; can be considered a subset of scheduling. ForkJoin implements a work-stealing technique when scheduling tasks that can be broadly described as follows:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;The fork/join framework is distinct because it uses a work-stealing algorithm. Worker threads that run out of things to do can steal tasks from other threads that are still busy.&lt;/p&gt;

&lt;p&gt;— &lt;a href=&#34;http://docs.oracle.com/javase/tutorial/essential/concurrency/forkjoin.html&#34;&gt;http://docs.oracle.com/javase/tutorial/essential/concurrency/forkjoin.html&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;ForkJoin is mostly abstracted away from Play developers, but it’s helpful to understand how it works when tuning Play for optimal performance.&lt;/p&gt;

&lt;p&gt;Parallelism building blocks in ForkJoin are:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;code&gt;ForkJoinPool&lt;/code&gt; — An instance of this class is used to run all of your fork-join tasks&lt;/li&gt;
&lt;li&gt;&lt;code&gt;RecursiveTask&amp;lt;V&amp;gt;&lt;/code&gt; — Run a subclass of this in a pool and have it return a result&lt;/li&gt;
&lt;li&gt;&lt;code&gt;RecursiveAction&lt;/code&gt; — Run a subclass of this in a pool but without returning a result&lt;/li&gt;
&lt;li&gt;&lt;code&gt;ForkJoinTask&amp;lt;V&amp;gt;&lt;/code&gt; — Superclass of &lt;code&gt;RecursiveTask&amp;lt;V&amp;gt;&lt;/code&gt; and &lt;code&gt;RecursiveAction&lt;/code&gt;; fork and join are methods defined in this class&lt;/li&gt;
&lt;/ul&gt;

&lt;h3 id=&#34;actions-and-futures&#34;&gt;Actions and Futures&lt;/h3&gt;

&lt;p&gt;The core of the developer experience in Play are &lt;em&gt;actions&lt;/em&gt;, which are tasks that are executed when an incoming request is routed to that action based on URI matching. An action can be defined as &lt;em&gt;synchronous&lt;/em&gt; or &lt;em&gt;asynchronous&lt;/em&gt;.&lt;/p&gt;

&lt;p&gt;Because Play is built on top of Scala, a hybrid object/functional programming language, actions themselves are simply anonymous functions that return an &lt;code&gt;HttpResponse&lt;/code&gt; (synchronous) or a &lt;code&gt;Future[HttpResponse]&lt;/code&gt; (asynchronous).&lt;/p&gt;

&lt;p&gt;The following action definition is synchronous:&lt;/p&gt;

&lt;div class=&#34;highlight&#34; style=&#34;background: #ffffff&#34;&gt;&lt;pre style=&#34;line-height: 125%&#34;&gt;&lt;span&gt;&lt;/span&gt;&lt;span style=&#34;color: #000080; font-weight: bold&#34;&gt;def&lt;/span&gt; joinGame &lt;span style=&#34;color: #000080; font-weight: bold&#34;&gt;=&lt;/span&gt; Action { &lt;span style=&#34;color: #000080; font-weight: bold&#34;&gt;implicit&lt;/span&gt; request &lt;span style=&#34;color: #000080; font-weight: bold&#34;&gt;=&amp;gt;&lt;/span&gt;
    Ok(...)
}
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;The following is asynchronous:&lt;/p&gt;

&lt;div class=&#34;highlight&#34; style=&#34;background: #ffffff&#34;&gt;&lt;pre style=&#34;line-height: 125%&#34;&gt;&lt;span&gt;&lt;/span&gt;&lt;span style=&#34;color: #000080; font-weight: bold&#34;&gt;def&lt;/span&gt; joinGame &lt;span style=&#34;color: #000080; font-weight: bold&#34;&gt;=&lt;/span&gt; Action.async { &lt;span style=&#34;color: #000080; font-weight: bold&#34;&gt;implicit&lt;/span&gt; request &lt;span style=&#34;color: #000080; font-weight: bold&#34;&gt;=&amp;gt;&lt;/span&gt;
    Future(Ok(...))
}
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;When we build Play applications in Scala, under the hood we can consider a &lt;code&gt;Future[T]&lt;/code&gt; to be an abstraction on top of &lt;code&gt;ForkJoinTask&amp;lt;V&amp;gt;&lt;/code&gt;. Understanding this fact becomes important when creating and tuning new &lt;em&gt;execution contexts&lt;/em&gt;.&lt;/p&gt;

&lt;h3 id=&#34;execution-contexts-vs-thread-pools&#34;&gt;Execution contexts vs thread pools&lt;/h3&gt;

&lt;p&gt;In the above code, we can see that &lt;code&gt;Action.async&lt;/code&gt; roughly maps to a &lt;code&gt;RecursiveAction&lt;/code&gt; and is executed asynchronously on a &lt;code&gt;ForkJoinPool&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;We can also see that &lt;code&gt;Action&lt;/code&gt; — a synchronous action — doesn&amp;rsquo;t have a clear mapping to ForkJoin. Instead, &lt;code&gt;Action&lt;/code&gt; maps to a thread that is executed on a thread pool.&lt;/p&gt;

&lt;p&gt;Both ForkJoin and thread pools can be configured through Play as &lt;em&gt;execution contexts&lt;/em&gt;, the high-level abstraction term for concurrency in Play.&lt;/p&gt;

&lt;h2 id=&#34;conclusion&#34;&gt;Conclusion&lt;/h2&gt;

&lt;p&gt;The syntactic difference is subtle but the runtime difference is profound. If we do not declare our actions as async, Play does not leverage ForkJoin; it assigns a thread to the lifecycle of the request and performs all computation synchronously. In situations where you may be tempted to pin a request to a thread in this fashion, you’re almost always better moving that work to Akka where you have significantly more options for distributing the work across VMs, servers, clusters, and data centers.&lt;/p&gt;

&lt;p&gt;With all of the concurrency and distribution options at hand, Play is the perfect technology to use as a stateless API gateway or RESTful API layer in a broader enterprise architecture. It integrates very well with front-end technologies such as AngularJS and React along with back-end technologies like Akka.&lt;/p&gt;

&lt;p&gt;Many people consider Play a simple MVC framework for rendering HTML. Although it comes with support for rendering HTML out of the box, that&amp;rsquo;s a convenience; Play is perfectly suited to serving JSON and XML without HTML. Consider HTML rendering as a nice — but non-essential — facet of the Play experience.&lt;/p&gt;

&lt;p&gt;What makes Play such a solid technology in front of waves of traffic is the concurrency model. No containers to deploy to. Ultimate flexibility of the deployment model.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Principle of Least Power with Play and Akka</title>
      <link>http://redelastic.com/blog/principle-of-least-power</link>
      <pubDate>Mon, 12 Dec 2016 00:00:00 +0000</pubDate>
      
      <guid>http://redelastic.com/blog/principle-of-least-power</guid>
      <description>&lt;p&gt;Language zealotry is not new, it’s been going on since the beginning of personal computers. Apple shipped with BASIC, and from the very beginning BASIC was held in contempt by Unix programmers.&lt;/p&gt;

&lt;p&gt;While BASIC went on to become a highly popular programming language, Unix was eventually overshadowed by Linux and relegated to the history books. There&amp;rsquo;s a sweet spot between purity and popularity that all technologies must keep in mind.&lt;/p&gt;

&lt;p&gt;Unix programmers of the era didn’t fully appreciate the power of simplicity - that is, a programming language so simple that entire language could be held in the head of a developer. In the era of StackOverflow this may be considered a laughable value proposition, but there was a time when programmers needed to fully understand the tools they worked with; cut-and-paste code hasn&amp;rsquo;t always been a few clicks away.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Apple was founded in 1977, and advances came with almost unbelievable rapidity in the years that followed. The potential of microcomputers was clear, and attracted yet another generation of bright young hackers. Their language was BASIC, so primitive that PDP-10 partisans and Unix aficionados both considered it beneath contempt.&lt;/p&gt;

&lt;p&gt;— &lt;a href=&#34;http://www.catb.org/esr/writings/cathedral-bazaar/&#34;&gt;The Cathedral and the Bazaar&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;One of the biggest pressures in professional software development is the constant battle against the feeling of falling behind. Some technologists exploit this insecurity to push increasingly complex technologies to solve the challenges at hand, obfuscating the compexity behind claims of purity and correctness. The ugly truth is that a pure, correct, perfect codebase, which can only be worked on by a small fraction of the most elite developers in the world, holds almost no long-term business value. When it comes time to evolve that codebase, urgency counts. Therefore it&amp;rsquo;s critical to balance technical purity with the wider factors in the market, such as the ability to staff projects.&lt;/p&gt;

&lt;p&gt;An emerging line of thinking in the Scala community is to embrace the &lt;em&gt;principle of least power&lt;/em&gt;. While advanced languages and tools such as Scala can offer a competitive advantage, they are also riddled with potential landmines because of their vast flexibility. From being used as a &lt;em&gt;better Java&lt;/em&gt; to used in &lt;em&gt;purely functional polymorphic style&lt;/em&gt;, the range of complexity and styles in production Scala codebases is vast.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Given a choice of solutions, pick the least powerful solution capable of solving your problem.&lt;/p&gt;

&lt;p&gt;— Li Haoyi, &lt;a href=&#34;http://www.lihaoyi.com/post/StrategicScalaStylePrincipleofLeastPower.html&#34;&gt;Strategic Scala Style&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;One of the qualities that originally attracted me to the Lightbend platform was the balance between power and simplicity. The Play framework…&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Proprietary-Unix players proved so ponderous, so blind, and so inept at marketing that Microsoft was able to grab away a large part of their market with the shockingly inferior technology of its Windows operating system.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;TODO&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>The Cloud Revolution</title>
      <link>http://redelastic.com/blog/the-cloud-revolution</link>
      <pubDate>Tue, 06 Dec 2016 00:00:00 +0000</pubDate>
      
      <guid>http://redelastic.com/blog/the-cloud-revolution</guid>
      <description>

&lt;p&gt;Server-side development is rapidly moving into the world of declarative and functional programming. Even Java 8 now supports functional programming constructs such as lambda syntax and a functional-style collections API. Libraries such as &lt;a href=&#34;http://www.javaslang.io/&#34;&gt;Javaslang&lt;/a&gt; are bringing even more powerful functional programming to Java developers.&lt;/p&gt;

&lt;div class=&#34;highlight&#34; style=&#34;background: #ffffff&#34;&gt;&lt;pre style=&#34;line-height: 125%&#34;&gt;&lt;span&gt;&lt;/span&gt;&lt;span style=&#34;color: #008800; font-style: italic&#34;&gt;/* filtering by age and converting to people to names in Java 8 with Javaslang */&lt;/span&gt;
List&amp;lt;String&amp;gt; names = persons
    .&lt;span style=&#34;color: #FF0000&#34;&gt;filter&lt;/span&gt;(p -&amp;gt; p.&lt;span style=&#34;color: #FF0000&#34;&gt;age&lt;/span&gt; &amp;gt; &lt;span style=&#34;color: #0000FF&#34;&gt;12&lt;/span&gt;)
    .&lt;span style=&#34;color: #FF0000&#34;&gt;map&lt;/span&gt;(Person::getName);
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;This shift towards functional programming is not accidental.&lt;/p&gt;

&lt;h2 id=&#34;from-code-to-data&#34;&gt;From Code to Data&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;When you get to where the f*** I&amp;rsquo;m at, you gotta remind &amp;lsquo;em about where you been.&lt;/p&gt;

&lt;p&gt;— Lil Wayne&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;In 2006, Ruby on Rails gave PHP developers a reasonable alternative to web development. Ruby on Rails in particular inspired a whole legion of programmers to rethink standards like the JCP and build sane frameworks rather than work within the confines of slow-moving standards designed by committee.&lt;/p&gt;

&lt;p&gt;While this was happening, Amazon was quietly revolutionizing the data center.&lt;/p&gt;

&lt;p&gt;Aside from Ruby on Rails, most frameworks were initially slow to catch onto the revolution happening in the cloud. Services like &lt;a href=&#34;https://www.heroku.com/&#34;&gt;Heroku&lt;/a&gt; and &lt;a href=&#34;https://aws.amazon.com/&#34;&gt;AWS&lt;/a&gt; began to bring unlimited resources on-tap to developers. For awhile it even looked like the JVM would lose relevance with new companies like Twitter embracing Ruby on Rails rather than the ever-complex bloatware dictated by ivory tower standards committees.&lt;/p&gt;

&lt;p&gt;While on-tap resources brought tremendous flexibility to developers, they also introduced a host of situations that popular frameworks of the day were not equipped to deal with.&lt;/p&gt;

&lt;h2 id=&#34;the-cloud&#34;&gt;The Cloud&lt;/h2&gt;

&lt;p&gt;Let&amp;rsquo;s be clear; the cloud is just a fancy phrase that translates to &lt;em&gt;”other people’s computers”&lt;/em&gt;. When you entrust your applications to computers that you don’t own, expect the unexpected; the main issue affecting cloud architectures is that a machine in the cloud can disappear at any time and for any reason. This is the core reason why monolithic-style frameworks that hold state on the server ill-equipped as a cloud-based technology. As much as the big players like IBM and Oracle want to reposition their container-based technologies as cloud-ready, it will never happen. The reality is that a long-time ago, while Ruby on Rails was quietly embracing HTTP at the core of its offering, the Java world was attempting to graft the object model on top of HTTP and essentially hide the web from developers. Bad move.&lt;/p&gt;

&lt;p&gt;Fast forward to today, and now the glue between servers — &lt;em&gt;the network&lt;/em&gt; — has in many ways become more robust than servers themselves. This pushes resilience concerns off of servers and onto the glue that connects servers together. If we consider the network as the pipes, we also need a fabric that sits on top which adds context to those connections. Rather than containers, we have a fabric - what we refer to as a cluster - which needs to be managed across potentially hundreds of servers.&lt;/p&gt;

&lt;h2 id=&#34;resilience-in-the-cloud&#34;&gt;Resilience in the Cloud&lt;/h2&gt;

&lt;p&gt;If we don’t expect our servers to stay alive, the very least we require is that if they die they spin back up in a consistent state. This is trivial for stateless applications, but non-trivial for stateful applications.&lt;/p&gt;

&lt;h2 id=&#34;a-survival-guide-for-architects&#34;&gt;A Survival Guide for Architects&lt;/h2&gt;

&lt;p&gt;TODO&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title></title>
      <link>http://redelastic.com/home/intro/</link>
      <pubDate>Thu, 17 Mar 2016 15:09:06 -0400</pubDate>
      
      <guid>http://redelastic.com/home/intro/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Blog</title>
      <link>http://redelastic.com/blog/</link>
      <pubDate>Thu, 17 Mar 2016 15:09:06 -0400</pubDate>
      
      <guid>http://redelastic.com/blog/</guid>
      <description>&lt;p&gt;Explore some of the topics that we&amp;rsquo;re passionate about at RedElastic.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title></title>
      <link>http://redelastic.com/home/footer/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>http://redelastic.com/home/footer/</guid>
      <description>&lt;p&gt;RedElastic is proudly located in downtown &lt;strong&gt;Toronto, Canada&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href=&#34;&#34;&gt;Schedule a chat&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;RedElastic Inc.&lt;/strong&gt;&lt;br&gt;
901 King Street West, Suite 400&lt;br&gt;
Toronto, Ontario, Canada&lt;br&gt;
M5V 3H5&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title></title>
      <link>http://redelastic.com/home/goals/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>http://redelastic.com/home/goals/</guid>
      <description>

&lt;h3 id=&#34;goals-of-your-leadership&#34;&gt;Goals of your Leadership&lt;/h3&gt;

&lt;p&gt;RedElastic is singularly focused on making the goals of your leadership a reality. We start every engagement with a number of sessions to fully map out the scope of your technical project along with long-term leadership goals. From these sessions can best advise on how to deliver solutions that fit your goals into the ever-evolving technical landscape.&lt;/p&gt;

&lt;h3 id=&#34;partnering-with-the-best&#34;&gt;Partnering with the best&lt;/h3&gt;

&lt;p&gt;Our extensive experience centers around partnerships, from vendors to other industry experts. Our engagements are focused on long-lasting relationships, which include helping your organization to form meaningful connections in the open source community.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>E-commerce</title>
      <link>http://redelastic.com/verticals/ecommerce/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>http://redelastic.com/verticals/ecommerce/</guid>
      <description>&lt;p&gt;What if you&amp;rsquo;re an online retailer that requires 99.9999% uptime while handling millions of page views per minute? Off-the-shelf solutions will only help you get you started, but won&amp;rsquo;t help you deal with spikes of traffic and the other realities of doing business online.&lt;/p&gt;

&lt;p&gt;The concepts of Reactive Application Development and Design (RADD) have proven themselves to drive incredible business value in e-commerce. Learn how to apply these concepts to your unique business needs.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Finance</title>
      <link>http://redelastic.com/verticals/finance/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>http://redelastic.com/verticals/finance/</guid>
      <description>&lt;p&gt;Financial services is a varied industry with many diverse needs. Balancing the availability and consistency of systems is crucial, all while maintaining an inviting and predictable user experience.&lt;/p&gt;

&lt;p&gt;We can help you leverage best-in-breed technologies in the field of stream processing, big data, and reactive programming, while also preparing your leadership for the future by advising on emerging technology topics such as blockchain.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Introduction to the Akka framework</title>
      <link>http://redelastic.com/trainings/2017-02-20/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>http://redelastic.com/trainings/2017-02-20/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Introduction to the Play framework</title>
      <link>http://redelastic.com/trainings/2017-01-12/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>http://redelastic.com/trainings/2017-01-12/</guid>
      <description></description>
    </item>
    
    <item>
      <title>Latest blog posts</title>
      <link>http://redelastic.com/home/blog/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>http://redelastic.com/home/blog/</guid>
      <description>&lt;p&gt;Donec id elit non mi porta gravida at eget metus. Nulla vitae elit libero, a pharetra augue. Vivamus sagittis lacus vel augue laoreet rutrum faucibus dolor auctor. Curabitur blandit tempus porttitor.&lt;/p&gt;
</description>
    </item>
    
    <item>
      <title>Public training</title>
      <link>http://redelastic.com/home/trainings/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>http://redelastic.com/home/trainings/</guid>
      <description>&lt;p&gt;Donec ullamcorper nulla non metus auctor fringilla. Donec sed odio dui. Praesent commodo cursus magna, vel scelerisque nisl consectetur et. Cras justo odio, dapibus ac facilisis in, egestas eget quam.&lt;/p&gt;
</description>
    </item>
    
  </channel>
</rss>