I participated in “Heroku Meetup #18 Connect!”.

Thank you CrowdWorks for providing the venue 🙏

to Heroku from AWS

(Waiting for slide publication)

I'll talk about the reasons for migrating from AWS to Heroku, what we did during migration, failures and lessons learned.

CrowdWorks Inc. Masaya Nasu

This was about the article:

• Migrating a Service Running on AWS to Heroku - CrowdWorks Engineer Blog

Here are my personal impressions:

✓ Migration from Heroku to AWS

I often hear about "migrating from Heroku to AWS" but rarely hear about "migrating from AWS to Heroku," so this was valuable.

✓ Ideally, late-night maintenance shouldn't be done

We tend to think "we have to do it for the service..." but it puts too much load on engineers, so I think it's healthier to consider improvement plans without late-night maintenance.

✓ Staging environments should have access restrictions

Even Heroku Staging can sometimes get indexed by Google search engines, so IP restrictions or Basic authentication should be implemented.

Heroku Connect Struggles and Hardships

(Waiting for slide publication)

Heroku Connect allows us to combine Heroku and Salesforce, products with completely different targets and strengths, to build composite systems. However, the database schema provided by Heroku Connect is heavily dependent on Salesforce's data structure, creating impedance mismatches with commonly used ORM assumptions and conventions. In the medical sharing economy service "Nadeshiko Nurse (https://nadeshikonurse.jp)," we resolve this mismatch using Heroku Postgres's updatable views. I'll specifically introduce a case where we achieved a standard web application development cycle without being conscious of the underlying Salesforce.

@Oakbow7

Since I’ve never used Salesforce, I listened like “I see, so such things happen” as current affairs.

"No Heroku Issues" - The Ultimate Praise for Heroku

There was a lot of company introduction time.

Event-Driven Architecture Using Apache Kafka on Heroku

(Waiting for slide publication)

Kafka is an open-source middleware developed by Apache Foundation for handling distributed messaging processing in pub-sub format. Heroku provides this Apache Kafka middleware in an easy-to-use state for developers, freed from operations, by having the knowledgeable Heroku team operate it. This time, I'll introduce event-driven architecture using Apache Kafka on Heroku.

@mitsuhiro

✓ Got a rough understanding of Apache Kafka

Apache Kafka was something I’d only heard the name of, so getting a rough understanding of Kafka was personally beneficial.

While listening to the presentation, I also read these articles:

• Getting Started with Apache Kafka | SOTA
• Apache Kafka ―From Introduction to Visualization Using Trifecta― - Qiita

Networking Event

(Will upload photos later 📷)

That’s all from the Gemba.