Using a hands-on approach to three useful Java frameworks for building Microservices: Spring Boot, Dropwizard, and WildFly Swarm you can compare and contrast them through a handful of familiar patterns.
This report is for developers and architects interested in developing microservices and distributed applications. It does not explain the basics of distributed systems, but instead focuses on the reactive benefits to build efficient microservice systems.
As explained in this O’Reilly report, some enterprises are now looking to bridge that gap by building microservice-based architectures on top of Java EE.
This cheat sheet should help you get started with developing a (web) application on Red Hat Enterprise Linux (RHEL).
JRebel helps more than 35,000 Java developers instantly see the impact of their code changes, without restarting their applications or losing state. With JRebel, developers can:
Instantly load 95% of typical code changes, including complex Java EE updates
Write code 17% faster by eliminating application or server restarts
Increase predictability of releases by +8%
Avoid distractions and stay focused on writing quality code
Code is easy, State is hard. Learning how to deal with your monolithic relational databases in a microservices structure is key to keeping pace in a quickly changing workplace.
Often driven by technological needs and familiarity to developers and administrators, deciding on a database can be in influenced by past experiences and decisions. The goal of this document is to evaluate MariaDB and MySQL side by side to better inform the decision-making process. Whether to embark on a greenfield project with no database in place yet, or running MySQL in production and considering an upgrade to MariaDB.
ATO, also known as account compromise, is just what it sounds like: a bad actor getting access to a good user’s account. Once that access is achieved, the fraudster can use the account for all kinds of opportunistic and malicious ends. As part of the ATO, the fraudster may change the user’s password to lock them out, and change their email address so the good user doesn’t receive any additional communication about activity on their account.
Microservices architecture is a new architectural style for creating loosely coupled but autonomous services. Emerging trends in technology—such as DevOps, Platform-as-a-Service (PaaS), containers, and continuous integration and delivery (CI/CD) methods—let organizations create and manage these modular systems on an unprecedented scale that exceeds earlier approaches like service-oriented architecture (SOA). But organizations that refactor monolithic applications into microservices experience widely varying degrees of success. The key to using microservices effectively is a solid understanding of how and why organizations should use microservices to build applications.
In this post we’ll focus on the radical changes required to efficiently monitor your microservices in production. We’ll lay out five guiding principles for adapting your monitoring approach for this new software architecture.
K2 Community teases out the ideas, best practices and lessons learned from some of the most active and successful people using K2. We want to understand what they’ve experienced, learned and accomplished with K2, and share that information across the community. It is our intent to learn from one another and collectively participate in one another’s success.
This paper is the first in a series that we plan to release in 2018, and beyond. These papers will
be focused on how businesses are scaling process automation across their organizations, with particular attention paid to “citizen development” strategies and frameworks that are being employed in organizations today. In other words, how are organizations taking platforms like K2 and enabling the line of business, and non-technical, non-IT resources to build process applications to solve unique business challenges and drive automation company wide.
In this paper we introduce a FaunaDB, a transactional NoSQL database which delivers on the scale, ease of use, and productivity promise of the NoSQL movement while recovering the safety and correctness lost with the abandonment of ACID transactions.