A client wants to create a scalable set of microservices that communicate with each other, where multiple microservices have a public REST API.
Which architecture strategy allows this on Heroku?
Suggested Answer: C
Get Premium Salesforce Certified Heroku Architect (Plat-Arch-206) Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
- httDs://devcenterheroku.com/artJcles/event-driven-microservices-with-aDache-kafka
21 comments · newest first
TU
Tu
1 month ago
B is solid for a simpler setup. Redis is easy to manage.
LO
Louisa
2 months ago
I agree with A. Microservices need to be independent.
ON
Ona
2 months ago
D seems too limiting. Shared memory isn't scalable.
OT
Otis
2 months ago
C sounds interesting, but DNS might complicate things.
MA
Matthew
2 months ago
I feel like B could work too. Redis is fast for communication.
TE
Telma
2 months ago
I think option A is the best. Kafka is great for scalability.
SH
Sheron
2 months ago
B is solid too. Redis can handle high loads well.
MA
Marnie
3 months ago
I feel like A gives the most flexibility for growth.
ME
Melodie
3 months ago
D seems limiting. Shared memory isn't ideal for microservices.
GE
Gerald
3 months ago
C sounds interesting, but DNS Service Discovery can be complex.
FE
Felix
3 months ago
I’m leaning towards B. Redis is simple and effective for communication.
MI
Michell
3 months ago
I think option A is the best. Kafka is great for scalability.
MA
Man
4 months ago
Wait, can microservices really communicate effectively with DNS Service Discovery?
ST
Stanton
4 months ago
D) seems outdated, shared memory isn't ideal for microservices.
YO
Yoko
4 months ago
C) sounds interesting, but is it really practical?
NO
Novella
5 months ago
I think B) is more efficient for smaller projects.
TW
Twana
6 months ago
A) is the best choice for scalability.
CH
Cherry
6 months ago
I’m a bit confused about option D; shared memory doesn’t seem right for microservices since they should be independent, right?
DA
Davida
6 months ago
I think we had a practice question about Heroku and microservices, and I might lean towards option C because DNS Service Discovery seems like a good way to manage multiple services.
TA
Tammi
6 months ago
I'm not entirely sure, but I feel like option B could work too since Redis is a common choice for message passing.
JU
Julian
7 months ago
I remember we discussed microservices in class, and I think option A sounds familiar since Kafka is often used for communication between services.