• Enterprise Groovy Gradle Plugin 1.0(static compilation by default with optional enforcment)

    Statically compile all the Groovy things!
    Just released Enterprise Groovy Gradle Plugin 1.0:

    One of the biggest complaints about Groovy is that it’s a dynamically compiled language, and that its optional static compilation feels bolted on. The Enterprise Groovy Plugin looks to fix this, by making static compilation the default, and gives you a configuration for optional enforcement. Groovy is a very powerful, and expressive language, and there may be times/places/companies, that want to take advantage of that power, but restrict it, because they have a large team, or have junior developers, etc. This is Where Enterprise Groovy comes in, giving you the tools to rein in some of the dynamic power, but whitelist it where it is needed.

    Posted By: tucker pelletier on Mar 11, 2019 6:31 AM
    Expires On: Apr 12, 2019 12:00 AM
  • Events
    • Learning a new programming language doesn’t have to be hard. Sure, there’s a lot of new stuff to wrap your head around: syntax, keywords and symbols, conventions, how to define variables and methods, arrays, and the list go on and on! But what if there were a technique and toolkit you could use to master a new language fast?

      In this session, Richard Kasperowski introduces mob programming and code koans. Mobbing is about getting all the best minds working on the same computer at the same time. Code koans are a series of micro-puzzles that teach you the new language in little chunks, using test-driven development. We’ll mob together on a set of code koans to learn a new language. Even better, we’ll decide on the language together! Current choices include C++, Java, JavaScript, Python, and Ruby.

      Who should attend? Anyone who wants to learn about mob programming and how to learn a new language.


      We would like to thank our event host Chewy.com for all the support for making this event possible in Downtown Boston. 



    • Resilient architecture is crucial for all cloud implementations. In this talk, we explore different design patterns to make a distributed application more resilient. 

      As part of this journey, for any process, we need to ask what if something goes wrong? Then, plan a course of action to the process auto heal without any human intervention and how to lower risks by performing canary deployments. Design starts with at first understanding of requirements and performing empathy map and value chain analysis. 

      Thinking application as stateless for all the API calls makes the system available most of the time requires creating a cache for common distributed data. Next, we examine how to deal with cascading failures, and timeouts scenarios.  Applications, as part of auto-healing, need to Detect, Prevent, Recover, Mitigate, Complement so that the service is resilient. 

      Key takeaways for the audience are as follows:

      • Resiliency is essential for any feature in cloud
      • Understanding the value chain is critical to identify failure points
      • Challenges come in identifying if there is a failure and design the system for auto healing
      • Focus should be first to prevent a failure to occur. 
      • Identifying key challenges in your company and tools and techniques to auto-heal and provide a sustainable solution