Outbox Pattern

Implementing the Outbox Pattern by Sohan GanapathyOct. 25, 2019

Read more...

Java Microservices in Docker?..

- А ты точно маргинал?
- Да.
- А скажи что-нибудь на маргинальном!
- В чём смысл пихать Java Spring Boot микросервисы внутрь Docker контейнеров?
Read more...

Export Tabs URLs

https://github.com/alct/export-tabs-urls
https://addons.mozilla.org/en-US/firefox/addon/export-tabs-urls-and-titles/ Read more...

Anon

Read more...

GitHub Education

Github Comic - The Amazing Robopatchers

"GitHub Education helps students, teachers, and schools access the tools and events they need to shape the next generation of software development."

Read more...

RESTfu­l Java­ with ­JAX-­RS 2.0

[GitBook] RESTfu­l Java­ with ­JAX-­RS 2.0
[PDF] Read more...

Software Architecture Documentation

• Unified Modeling Language - Wikipedia
• 4+1 architectural view model - Wikipedia
• Architecture decision records (ADR) (aka Design Choices Document)
• The C4 model for visualising software architecture
• Dependency diagrams

Read more...

Интерактивная карта миграции в Латвии

Интерактивная карта миграции в Латвии от Центрального Статистического Управления: migracija.csb.gov.lv
Read more...

Где сейчас сверкает? Карты гроз

Карты, показывающие молнии на Планете с задержкой всего в несколько секунд (типа "почти в реальном времени"):
LightningMaps.org
Blitzortung.org

Read more...

What went wrong with the IT-industry? - James Coplien

Read more...

The other side of Elmar

(see also)

Read more...

Как правильно писать коммит-сообщения в Гит?

Наткнулся на такое обсуждение.

dmytrostriletskyi: Пулл реквесты должны иметь повелительное наклонение.

KvanTTT: Вот кстати меня всегда интересовал вопрос. Я обычно коммит-сообщения пишу в прошедшем времени, что было пофикшено: "Исправлен баг". Но также много встречал и в настоящем, в том числе и в этой статье: "Исправление бага". Как все же правильней?

vedenin1980: Я встречал в настоящем, в прошлом и будущем (если тикеты), более того бывает вместо глаголов просто существительные, бывает народ не парится и пишет по-разному. На самом деле, это как код стайл языка в одном языка записывают переменную как catInterface, в другом как cat_interface, в третьем СatInterface и т.д. Какой правильный? Все они правильные, это спор табов против пробелов, какие правила на проекте/команде/языке приняты — так и правильнее. ИМХО.

pesh1983: Вот тут отличный пост про это с доходчивым объяснением, зачем и почему chris.beams.io/posts/git-commit

Read more...

Elmar, I need more JIRAs today!

Read more...

Will, Would, Shall, Should

Read more...

"have" collocations

Read more...

BBC Learning English

BBC Learning English



Read more...

If you only have JRE... ;)

Read more...

WildFly Swarm in 15 minutes

"how to have executable Jars, use standard Java EE APIs and write Micro, Nano and even Pico services using WildFly Swarm"

Read more...

Java User Group Latvia - 42nd meeting on 25-April-2017

JUG LV Homepage
Free Registration for JUG LV #42, Konventa Seta, 9/11 Kalēju iela, LV-1050, Rīga. Kampenhauzens conference room, 1st floor.

Agenda

1. Look ma, no JavaScript – how you can build a modern web app 100% in Java by Sami Ekblad

Building great web apps is not an easy task. User expectations keep growing, and the technologies needed to fulfil them are increasingly complicated. Vaadin takes a very different approach to web development. For starters, there's no need to write HTML or JavaScript. No REST services. Instead, you build your app using ready-made UI components in Java and let Vaadin handle the rest. Come find out how fun and productive web development can be when you cut out all the nonsense.


2. Forget about Microservices, Micromodules is a new Silver Bullet by Dmitry Buzdin & Ilgvars Jecis
Read more...

Rod Johnson on portability of J2EE applications

Rod Johnson, the father of Spring, wrote in his famous book "Expert One-on-One J2EE Design and Development" (2002):

"Portability is a great bonus of the J2EE platform. <...> portability can be achieved in real applications, but it's not the point of J2EE. The requirement of the vast majority of projects is to build an application that solves a particular problem well on one target platform. An application that runs badly on one platform will never be ported to other platforms (the application might be ported to another operating system that runs on more powerful hardware to gain adequate performance, but that's not the kind of portability that professional developers aspire to).

J2EE orthodoxy holds that an application should be portable across J2EE application servers and must be able to work with different databases. The distinction between these two goals is important, and sometimes missed. Portability between application servers may deliver business value and is usually a realistic goal. Portability between databases is much more fraught, and often provides no business value.

Portability is usually taken to mean code portability: the ability to take the application and run it on another platform without any change. <...> this is an expensive misconception. Naïve emphasis on total code portability often leads to heavy costs in lost productivity and less satisfactory deliverables. Write Once Run Anywhere (WORA), while a reality where Java itself is concerned, is a dangerous slogan to apply to enterprise development, which depends on a range of resources.

<...>

The portability myth has led to wide acceptance that J2EE applications can't use the capabilities of today's relational databases, but should use them only as dumb storage. This does great harm in the real world."

Read more...