In the race with time-to-market pressures, developers are in a rush to put their product out there. But according to Theresa Lanowitz, founder of Voke, there's this "fix it later" mentality when we should really be fixing it now, or in her words, future-proofing our applications.
As mobility increases productivity in a fast-paced society, it's important to understand security threats that come along with it. How strong is your organization's mobile strategy? Do you know what tools should be used to help fend off attacks? Even if safeguards are in place, is it tome for your strategy to mature?
Traditionally, since the very beginning of the computing era, enterprise software development has faced one challenge when, naturally, it is supposed to be focused on solving real business problems, but at the same time developers have to spend significant time and efforts on the technical side of the solution, such as architecture and generic functionality implementation. The article explains how CUBA Platform solves this problem.
I’ve just written a book that is now publicly available! The name of the book is “Microservices for Java Developers” (O’Reilly) and is a hands-on, step-by-step guide for building microservices with some popular Java frameworks like Spring Boot, Dropwizard, and WildFly Swarm! We also explore some of the non-functional requirements like safe deployments, exposing metrics, service interaction, service discovery, load balancing et. al. and how technology like Netflix OSS, Docker, and especially Kubernetes can help simplify the deployment and management of your microservices. Many many thanks to all of the reviewers who took the time to give feedback and for Red Hat for sponsoring my time especially Burr Sutter and the talented folks at O’Reilly who helped coordinate the effort and make it come to fruition.
I’ll have printed copies at DevNation/Summit (including a signing session Tuesday, June 28th at 3:30 at the Moscone Ctr.) and you can get a digital copy at the Red Hat Developers website. Stay tuned (@christianposta) as I may be working on part II :)
The Java community has likely been the greatest factor in Java’s success and influence over the past 20+ years. This community has rallied and collaborated to improve the language and its capabilities through JSRs, libraries, APIs, frameworks, and more. Now Java EE has become “the dominant standard for companies building business-critical multi-tier enterprise applications.”
With that in mind, and with microservices architectures becoming ever more popular as monolithic applications hinder the advances of continuous delivery and integration, minimize performance, and lead to downtimes that are unacceptable for today’s technologies, there’s a new hurdle for the Java community to jump. Yesterday, the MicroProfile initiative was announced to inspire the community to overcome that hurdle together.
I think it's too obvious to say that a singleton is an anti-pattern as there are tons of articles about that (singleton being an anti-pattern). However, more often than not, the question is how to define global things without a singleton; and the answer to that is not obvious for many of us. There are several examples: a database connection pool, a repository, a configuration map, etc. They all naturally seem to be "global"; but what do we do with them?
I assume you already know what a singleton is and why it's an anti-pattern. If not, I recommend you read this StackOverflow thread: What is so bad about singletons?